- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Honeycomb 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 1h 16m it lasted.
Anything that failed between 2026-04-09 17:43 UTC and 2026-04-09 19:00 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 1
- resolved
We have detected and remediated an issue around our SLO processing pipeline. From 17:00 to 17:15 UTC, events were being delayed, and alerts may likewise have been a few minutes late. Processing has caught up and is currently within normal operational ranges.
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-4909fc3863
Is Honeycomb still down?
No, this incident was resolved 2026-04-09 19:00 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
1h 16m, from 2026-04-09 17:43 UTC to 2026-04-09 19:00 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named 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.