- Level
- confirmed
- Worst impact
- Partial outage
- Components
- ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting
- Regions
- us, us-east-1
- Down Index
- 41of 100
What to do
Check whether you use Honeycomb ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 1h it lasted.
Anything that failed between 2025-10-20 14:16 UTC and 2025-10-21 15:41 UTC may need a replay.Subscribe to Honeycomb's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=honeycomb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Honeycomb 8
- monitoring
Due to constrained EC2 instance capacity in the AWS us-east-1 region, we are choosing to allocate the capacity we have to incoming events and telemetry. As such, customers may see over 5 minute delays in our processing of - SLOs - Service Maps We do not expect a degradation of our core ingest -> query flow, and we do not expect triggers to be impacted
provider
- monitoring
SLO processing has recovered. Service Maps continues to be degraded but historical data can be queried.
provider
- monitoring
The networking issues in us-east-1 is affecting our query engine - customers may see errors or delays when running queries as a result.
provider
- monitoring
We’re currently observing that querying is seeing signs of recovery. We are continuing to monitor the situation
provider
- monitoring
AWS is starting to show signs of recovery. Querying remains partially impacted and may take longer to return results. We are continuing to monitor the situation.
provider
- monitoring
Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. We are continuing to monitor the situation.
provider
- monitoring
Honeycomb core functionality is operational. Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. This is our final update for the night unless the situation degrades. We will continue to monitor the situation.
provider
- resolved
This incident has been resolved. At no point did we lose any customer data that hit our load balancers. Querying has been stable for hours, and all features that were degraded are functional.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-3cce7f1929
Is Honeycomb still down?
No, this incident was resolved 2025-10-21 15:41 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
1d 1h, from 2025-10-20 14:16 UTC to 2025-10-21 15:41 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting in us, us-east-1.
What caused it?
Honeycomb hasn't published a root cause. If it does, it shows here.
Where does this come from?
Honeycomb's official status page, https://status.honeycomb.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.