Honeycomb.io had 35 outages in the last 2 years totaling 16h 59m of downtime — averaging 1.4 incidents per month.
There were 35 Honeycomb.io outages since June 13, 2025 totaling 16h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
An outage with an upstream service provider is currently affecting Honeycomb's infrastructure. Functionality of the ServiceMaps feature is degraded at this time.
Service Maps functionality has been restored.
A PagerDuty outage prevented some Trigger and SLO notifications from reaching your workspaces. The issue has since been resolved, and notification systems are now operating normally. Impact Window: 21:54 PT – 23:27 PT
We're see a partial degradation of data liveness, which may impact triggers and SLOs in a small percentage of users
We have determined the cause and implemented a fix. Customers should be seeing normal operations again.
For a period of approximately 1h30, from 9:34 UTC to 11:08 UTC, our ingestion of events in the EU region was delayed. All events were eventually processed, but for that duration, triggers, SLOs, and regular queries could have seen missing data for a brief period of time. As we re-balanced traffic loads and scaled the system, ingestion caught up and data has since then been fully available. We are still actively working on improving the scaling margins and behaviors of the EU instance of Honeycomb to better sustain load variations we are observing at this time.
Data ingestion is currently being delayed in the EU region. All traffic is being accepted, but it may take some time to show up in queries, and may have an impact on trigger-based alerting as well.
We have load-balanced ingestion traffic to bring back performance under control, and are currently monitoring to make sure it stays that way.
Our load-balancing of ingestion traffic is doing its job and everything is back to normal.
We are seeing a querying slowdown in the US. We have identified the cause and are working to mitigate
A fix has been implemented and customers should see query speed returning to normal
This incident has been resolved.
An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.
This incident has been resolved.
Telemetry is being intermittently dropped in the EU and we are currently investigating the cause
A fix has been implemented and we are monitoring the results
This incident has been resolved.
A build needs to be reverted as we have ongoing failures when rendering query results.
We have identified the cause of the problem and have begun a revert.
Querying capabilities are now restored.
The incident is resolved.