- Level
- confirmed
- Worst impact
- Degraded
- Components
- ui.honeycomb.io - US1 Querying
- Regions
- us
What to do
Check whether you use Honeycomb ui.honeycomb.io - US1 Querying in us. 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 2h 53m it lasted.
Anything that failed between 2025-07-21 18:01 UTC and 2025-07-21 20:53 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 3
- identified
We are seeing a querying slowdown in the US. We have identified the cause and are working to mitigate
provider
- monitoring
A fix has been implemented and customers should see query speed returning to normal
provider
- resolved
This incident has been resolved.
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-26326d7e16
Is Honeycomb still down?
No, this incident was resolved 2025-07-21 20:53 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
2h 53m, from 2025-07-21 18:01 UTC to 2025-07-21 20:53 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named ui.honeycomb.io - US1 Querying in us.
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.