- Level
- confirmed
- Worst impact
- Degraded
- Components
- ui.honeycomb.io - US1 Activity Log
- Regions
- us
What to do
Check whether you use Honeycomb ui.honeycomb.io - US1 Activity Log 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 2h 40m it lasted.
Anything that failed between 2026-06-29 22:07 UTC and 2026-06-30 00:47 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 2
- monitoring
Starting at 14:24 PT, there was an issue with the Activity Log causing events to stop being processed. You may notice a gap starting at that time. We are slowly backfilling these events and do not expect any data loss to occur. We expect the full data log to be restored around 17:30 PT.
provider
- resolved
Backfill of the Activity Log events has completed. All events during the affected period should be present.
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-4291fdd5b0
Is Honeycomb still down?
No, this incident was resolved 2026-06-30 00:47 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.
How long did it last?
2h 40m, from 2026-06-29 22:07 UTC to 2026-06-30 00:47 UTC, by the times Honeycomb posted.
What was affected?
Honeycomb named ui.honeycomb.io - US1 Activity Log 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.