# Honeycomb: Slowness in US region

- Provider: [Honeycomb](https://outages.cc/honeycomb.md)
- Type: Incident
- State: Resolved
- Worst impact: Partial outage
- Started: 2026-10-20 14:04 UTC
- Resolved: 2026-10-20 16:26 UTC (lasted 2 h 21 min)
- Components: ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 App Interface, ui.honeycomb.io - US1 Trigger & SLO Alerting
- Official update: https://stspg.io/3rp4g9hght3w

## Updates from Honeycomb

### postmortem, 2026-10-21 23:26 UTC

On October 20, we experienced roughly three 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. During this time, customers may have experienced slow or failed queries and a sluggish UI, and some trigger alerts may have been late or missed. * From 13:26 to approximately 16:10 UTC, SLO processing was delayed, so SLO data may have appeared out of date and burn alerts may have been delayed or missed during that time. * From 13:57 to 14:09 UTC, about half of requests to the event ingest API received 5xx errors, with lesser impact between 13:48 and 13:55 UTC \(1% error rate\) and for approximately a minute at 14:15 UTC \(1.9% error rate\). Telemetry rejected during these periods was not ingested unless the sender successfully retried it. Customers may see gaps in their data for those periods, including in triggers

### resolved, 2026-10-20 16:26 UTC

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

### investigating, 2026-10-20 15:18 UTC

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

### investigating, 2026-10-20 14:04 UTC

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