Honeycomb.io incident

Slowness in US region

Resolved after 2 hours 21 minutes, affecting ui.honeycomb.io - US1 Querying and ui.honeycomb.io - US1 App Interface and 1 more, on October 20, 2026.

postmortem Oct 21, 2026, 11:26 PM UTC

On October 20, Honeycomb experienced about 3 hours of degraded service in the US region. From 13:30 to 14:40 UTC, querying, the Honeycomb UI, the management API, and triggers experienced elevated latency and error rates, with the highest impact between 13:55 and 14:10 UTC. Some trigger alerts may have been late or missed during that time. SLO processing suffered delays between 13:26 and 14:10 UTC. From 13:57 to 14:09 UTC, about half of requests to the event ingest API received 5xx errors. Lesser impact occurred between 13:48 to 13:55 \(1% error rate\) and for approximately minute at 14:15 \(3% error rate\). We’ll publish a more in-depth report on Friday, October 23 which will cover detection, remediation, and outstanding action items.

Started
Oct 20, 2026, 02:04 PM UTC
Resolved
Oct 20, 2026, 04:26 PM UTC
Duration
2h 21m
Detected by Pingoru
Oct 20, 2026, 02:04 PM UTC

Affected components

ui.honeycomb.io - US1 Queryingui.honeycomb.io - US1 App Interfaceui.honeycomb.io - US1 Trigger & SLO Alerting

Update timeline

  1. investigating Oct 20, 2026, 02:04 PM UTC

    We are currently investigating the degradation of various services in our US region.

  2. investigating Oct 20, 2026, 03:18 PM UTC

    We've identified and isolated the impacted service and are seeing recovery in query execution. SLO processing remains degraded.

  3. resolved Oct 20, 2026, 04:26 PM UTC

    SLO processing has fully recovered. All services are now functional.

  4. postmortem Oct 21, 2026, 11:26 PM UTC

    On October 20, Honeycomb experienced about 3 hours of degraded service in the US region. From 13:30 to 14:40 UTC, querying, the Honeycomb UI, the management API, and triggers experienced elevated latency and error rates, with the highest impact between 13:55 and 14:10 UTC. Some trigger alerts may have been late or missed during that time. SLO processing suffered delays between 13:26 and 14:10 UTC. From 13:57 to 14:09 UTC, about half of requests to the event ingest API received 5xx errors. Lesser impact occurred between 13:48 to 13:55 \(1% error rate\) and for approximately minute at 14:15 \(3% error rate\). We’ll publish a more in-depth report on Friday, October 23 which will cover detection, remediation, and outstanding action items.

Your product runs on more than Honeycomb.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →