- Level
- confirmed
- Worst impact
- Degraded
- Components
- ui.honeycomb.io - US1 Querying
What to do
Check whether you use Honeycomb ui.honeycomb.io - US1 Querying. 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 7h 34m it lasted.
Anything that failed between 2026-08-10 13:01 UTC and 2026-08-10 20:35 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 2
- monitoring
From 11:36UTC to 12:43UTC, queries in US1 that read older data returned errors or timed out. Queries over recent data were un-affected, and no telemetry is being lost. The issue has been identified, and a fix is in place. We are currently monitoring the situation to confirm resolution.
provider
- resolved
The fix is in place and we've confirmed resolution. Queries and SLOs are processing normally.
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-de81c48b72
Is Honeycomb still down?
No, this incident was resolved 2026-08-10 20:35 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
7h 34m, from 2026-08-10 13:01 UTC to 2026-08-10 20:35 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named ui.honeycomb.io - US1 Querying.
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.