- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
- Regions
- eu
What to do
Check whether you use Honeycomb api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting 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 2h 32m it lasted.
Anything that failed between 2026-06-25 18:10 UTC and 2026-06-25 20:41 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
- investigating
We are investigating an issue with delayed ingest in the EU region. SLOs and Trigger evaluations may also be delayed.
provider
- monitoring
We are monitoring the situation. Events may have been delayed between 17:53 and 18:04 UTC.
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-2d42d6f7a1
Is Honeycomb still down?
No, this incident was resolved 2026-06-25 20:41 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
2h 32m, from 2026-06-25 18:10 UTC to 2026-06-25 20:41 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting 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.