activity log for US instance is delayed
Update - We are continuing to monitor for any further issues.
May 08, 2026 - 03:22 PDT
Update - We believe that the activity log should now be caught up.
May 08, 2026 - 03:21 PDT
Monitoring - Backfilling of the past 2h30m of data is now in progress and should complete shortly.
May 08, 2026 - 03:13 PDT
Identified - Activity log delay is rising, and is more than an hour behind due to a MySQL replica failover. Estimated recovery by 04:00 PDT.
May 08, 2026 - 01:00 PDT
Uptime over the past 90 days. View historical uptime.
api.honeycomb.io - US1 Event Ingest Operational
90 days ago
99.98 % uptime
Today
ui.honeycomb.io - US1 Querying Operational
90 days ago
100.0 % uptime
Today
ui.honeycomb.io - US1 App Interface Operational
90 days ago
99.99 % uptime
Today
ui.honeycomb.io - US1 Trigger & SLO Alerting Operational
90 days ago
99.98 % uptime
Today
ui.honeycomb.io - US1 Activity Log Operational
90 days ago
99.54 % uptime
Today
api.eu1.honeycomb.io - EU1 Event Ingest Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 App Interface Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 Querying Operational
90 days ago
99.99 % uptime
Today
ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 Activity Log Operational
90 days ago
99.76 % uptime
Today
www.honeycomb.io Operational
Sandbox Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

May 8, 2026

Unresolved incident: activity log for US instance is delayed.

May 7, 2026
Scheduled Maintenance - US Region
Completed - Scheduled maintenance is complete. All services are healthy and stable. Ingest, querying SLO processing, anomaly detection, Service Maps, and Activity Log are all confirmed operating normally. Backfill and SLO repair are complete. Thank you for your patience.
May 7, 15:44 PDT
Update - We are now in our final verification stage. Query results should begin returning fresh data now.
May 7, 15:27 PDT
Verifying - All consumer services have been successfully cut over. SLO backfill is currently running. Anomaly detection, Service Maps, and Activity Log processing are all on the new cluster and catching up. All data will be fully present within approximately 2 hours of the maintenance window closing.
May 7, 15:13 PDT
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
May 7, 13:53 PDT
In progress - We have begun scheduled maintenance on our Kafka infrastructure in Production US. During this window, event ingestion and query results may experience delays.
May 7, 13:10 PDT
Scheduled - We will be performing scheduled maintenance on our Kafka infrastructure in the US region. This maintenance will only impact the US cluster.

During this window, you may experience the following:

Ingest will remain uninterrupted - events will continue to be accepted, although their processing will be delayed. You may notice a gap in your data during the migration window; this data will be backfilled after the migration completes. Expect all data to be present within approximately 3 hours of the maintenance window closing.

Query results will reflect a delay in fresh data during the cutover window, in line with the ingestion delays.

Triggers and alerts: Triggers watching for missing events (e.g. heartbeats) will fire during this window. Triggers watching for values above a threshold are not expected to fire. Other alerting sources will process delayed events late, up to approximately 3 hours.

SLO burn alerts will also fire late during this window.

Activity Log and Service Maps will experience delays in processing events.

We appreciate your patience and will provide updates as the maintenance progresses
Apr 28, 11:49 PDT
May 6, 2026

No incidents reported.

May 5, 2026

No incidents reported.

May 4, 2026
Scheduled Maintenance – EU Region
Completed - Scheduled maintenance is complete. All services are healthy and stable. Ingest, Querying, SLO processing, Anomaly Detection, Service Maps, Triggers and Activity Log are all confirmed operating normally. Backfill and SLA repair are complete. Thank you for your patience.
May 4, 13:00 PDT
Verifying - We are in our final verification phase. Query results, SLO calculations, anomaly detection, and Service Maps are all confirmed processing as expected.
May 4, 12:08 PDT
Update - Query results should begin returning fresh data shortly. SLO processing and Service Maps migration are still in progress.
May 4, 11:14 PDT
Update - We have begun scheduled maintenance on our Kafka infrastructure in Production EU.
May 4, 10:28 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 4, 10:00 PDT
Scheduled - We will be performing scheduled maintenance on our Kafka infrastructure in the EU region. This maintenance will only impact the EU cluster.

During this window, you may experience the following:
* Ingest will remain uninterrupted - events will continue to be accepted, although their processing will be delayed. You may notice a gap in your data during the migration window; this data will be backfilled after the migration completes. Expect all data to be present within approximately 3 hours of the maintenance window closing.
* Query results will reflect a delay in fresh data during the cutover window, in line with the ingestion delays.
* Triggers and alerts: Triggers watching for missing events (e.g. heartbeats) will fire during this window. Triggers watching for values above a threshold are not expected to fire. Other alerting sources will process delayed events late, up to approximately 3 hours.
* SLO burn alerts will also fire late during this window.
* Activity Log and Service Maps will experience delays in processing events.

We appreciate your patience and will provide updates as the maintenance progresses
Apr 27, 13:58 PDT
May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026
Gap in Activity Log data in the EU region.
Resolved - The database failover that caused query issues earlier in the EU (https://status.honeycomb.io/incidents/n855d8kzp32y) has also had knock-on effects on our Activity Log beta feature. Due to recovery issues on the data replication flow used for this mechanism, activity log events will be missing from 12:45 UTC until 19:45 UTC, representing a 5 hour gap in events.

We have identified configuration parameters that will be adjusted to reduce the likelihood of such losses in the future.
May 1, 06:00 PDT
Query interuption due to database failover in the EU region
Resolved - At 12:50, our main database underwent an automated failover. This failover led to issues with some of our query engine connection pools, and caused queries to fail for roughly 10 minutes before self resolving.
May 1, 05:30 PDT
Apr 30, 2026
Links in Slack triggers not working
Resolved - We are confident the issue is fully resolved.
Apr 30, 09:37 PDT
Monitoring - The fix has been implemented and links on Slack triggers are functional again.
Apr 30, 08:07 PDT
Identified - We discovered that links in Slack triggers are not working and have identified the cause and are in process of implementing a fix
Apr 30, 08:03 PDT
Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage