- Level
- confirmed
- Worst impact
- Degraded
- Components
- ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting
- Down Index
- 22of 100
What to do
Check whether you use Honeycomb ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting. 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 1h 43m it lasted.
Anything that failed between 2026-03-12 11:55 UTC and 2026-03-12 13:39 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 investigating elevated error rates affecting queries in our US1 region. Our team is actively working on a resolution. We will provide updates as we learn more.
provider
- identified
We have rolled back a code change to our query engine, but our triggers service has not recovered. We are investigating.
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-14168b5987
Is Honeycomb still down?
No, this incident was resolved 2026-03-12 13:39 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
1h 43m, from 2026-03-12 11:55 UTC to 2026-03-12 13:39 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named ui.honeycomb.io - US1 Querying, ui.honeycomb.io - US1 Trigger & SLO Alerting.
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.