← Back to the carnage
HONEYCOMB
⚪ Honeycomb decided their query engine needed a 20-minute meditation break. Triggers and SLOs got ghosted in the process. Cause found, crisis averted, engineers returned to normal stress levels. (Auto-resolved: no updates in 24h)
// The official story
Partial Querying Outage
// Status page says
Apr 9 , 03:12 PDT Resolved - We experienced a partial querying outage from approximately 8:58 - 9:18 UTC. This outage may have resulted in some Trigger and SLO alert failures for the duration of the outage. The cause of the outage has been identified and mitigated.
🔗 Official status page (for the PR-approved version)
https://status.honeycomb.io/incidents/mhm6pgjzsr1dHoneycomb's Greatest Hits
🟢 HONEYCOMB
Aug 10, 2026
🟠 Honeycomb's US1 region decided historical data was yesterday's problem—literally. Queries digging into the past got the silent treatment while fresh data sailed through fine. They found the culprit and slapped a band-aid on it. (Auto-resolved: no updates in 24h)
🟢 HONEYCOMB
Jun 25, 2026
🟡 Honeycomb's EU data pipeline decided to ghost incoming telemetry. SLOs and triggers are also pretending they didn't see your metrics. Engineers are now playing detective with cold brew in hand. (Auto-resolved: no updates in 24h)
🟢 HONEYCOMB
Jun 24, 2026
🔴 Honeycomb's data intake went dark for 19 minutes while engineers frantically rolled back a deploy that apparently thought it could make observability invisible. Triggers, SLOs, and Service Maps are now limping back online, which is code for 'we have no idea what we missed.'. (Auto-resolved: no updates in 24h)
🟢 HONEYCOMB
Jun 24, 2026
🟡 Honeycomb decided to test what happens when observability can't observe itself—19 minutes of delayed ingest across US/EU while engineers frantically hit the rollback button. Service Maps also took an unscheduled nap. Crisis averted, embarrassment permanent. (Auto-resolved: no updates in 24h)