- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 22of 100
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 0m it lasted.
Anything that failed between 2026-10-20 17:07 UTC and 2026-10-20 13:30 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
From 13:57 to 14:09 UTC, event ingest in Honeycomb's US production environment was degraded by an concurrent incident . During this window, approximately 53% of incoming events received 5xx errors.
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-27a0ed4125
Is Honeycomb still down?
No, this incident was resolved 2026-10-20 13:30 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
0m, from 2026-10-20 17:07 UTC to 2026-10-20 13:30 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.