All Systems Operational

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.56 % 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
100.0 % 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
100.0 % 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.

Scheduled Maintenance

Scheduled Maintenance – EU Region Apr 21, 2026 08:00-11: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 14, 2026 - 15:44 PDT
Apr 16, 2026

No incidents reported today.

Apr 15, 2026
Activity Log ingest is delayed
Resolved - Activity Log is ingesting events again. We had no loss in data.
Apr 15, 12:25 PDT
Identified - Activity Log is experiencing a delay in processing events. We are working on remediating the issue.
Apr 15, 12:04 PDT
Apr 14, 2026
Activity Log delayed ingest in EU
Resolved - All activity log data is now live and up to date.
Apr 14, 15:37 PDT
Monitoring - A fix has been implemented and we are monitoring recovery.
Apr 14, 15:08 PDT
Identified - Activity Log events may be delayed, starting from around 19:55UTC. We're actively working on remediation.
Apr 14, 14:36 PDT
Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026
Activity log delay in production US
Resolved - All activity log data is now live and up to date.
Apr 10, 12:10 PDT
Update - SLO processing has fully recovered.
Apr 9, 17:05 PDT
Update - SLOs experienced a period of additional processing delays. A fix has been deployed and recovery is ongoing.
Apr 9, 16:43 PDT
Update - We have identified an issue with triggers and SLOs and have implemented a fix. Customers should no longer see degraded performance for triggers or SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes.
Apr 9, 14:03 PDT
Update - We have identified an issue with triggers and SLOs and are actively investigating. Customers may experience delays when creating or updating triggers and SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes.
Apr 9, 13:24 PDT
Identified - We have identified the cause and are working to resolve the issue.
Apr 9, 04:52 PDT
Ingest issues for some customers
Resolved - We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.
Apr 10, 10:24 PDT
Update - We are continuing to work on the systemic solution and monitor. We'll leave the incident open until we're able to confirm the issue won't recur.
Apr 10, 08:21 PDT
Update - The manual fix has been applied to all environments.
Apr 10, 07:32 PDT
Monitoring - We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.
Apr 10, 07:19 PDT
Update - We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.
Apr 10, 06:55 PDT
Update - We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.
Apr 10, 06:46 PDT
Identified - We have confirmed reports of some teams getting issues ingesting their data. We have identified a probable source behind this behavior and are currently trying to correct it.
Apr 10, 06:41 PDT
Apr 9, 2026
SLO processing delay in US
Resolved - We have detected and remediated an issue around our SLO processing pipeline. From 17:00 to 17:15 UTC, events were being delayed, and alerts may likewise have been a few minutes late. Processing has caught up and is currently within normal operational ranges.
Apr 9, 12:00 PDT
Partial Querying Outage
Resolved - We experienced a partial querying outage from approximately 8:58 - 9:18 UTC. This outage may have resulted in some Trigger and SLO alert failures for the duration of the outage. The cause of the outage has been identified and mitigated.
Apr 9, 03:12 PDT
Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage