- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu
What to do
Check whether you use Honeycomb in eu. 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 2025-08-13 17:10 UTC and 2025-08-13 09: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
For a period of approximately 1h30, from 9:34 UTC to 11:08 UTC, our ingestion of events in the EU region was delayed. All events were eventually processed, but for that duration, triggers, SLOs, and regular queries could have seen missing data for a brief period of time. As we re-balanced traffic loads and scaled the system, ingestion caught up and data has since then been fully available. We are still actively working on improving the scaling margins and behaviors of the EU instance of Honeycomb to better sustain load variations we are observing at this time.
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-8307d335e4
Is Honeycomb still down?
No, this incident was resolved 2025-08-13 09:30 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
0m, from 2025-08-13 17:10 UTC to 2025-08-13 09:30 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named in eu.
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.