All Systems Operational
api.honeycomb.io - US1 Event Ingest
Operational
ui.honeycomb.io - US1 Querying
Operational
ui.honeycomb.io - US1 App Interface
Operational
ui.honeycomb.io - US1 Trigger & SLO Alerting
Operational
ui.honeycomb.io - US1 Activity Log
Operational
api.eu1.honeycomb.io - EU1 Event Ingest
Operational
ui.eu1.honeycomb.io - EU1 App Interface
Operational
ui.eu1.honeycomb.io - EU1 Querying
Operational
ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
Operational
ui.eu1.honeycomb.io - EU1 Activity Log
Operational
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.
Scheduled Maintenance
Scheduled Maintenance – EU Region May 4, 2026 10:00-13:00 PDT
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
Posted on Apr 27, 2026 - 13:58 PDT
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
Posted on Apr 27, 2026 - 13:58 PDT