Honeycomb.io incident

Ingest Outage in US and EU

Major Resolved View vendor source →

Honeycomb.io experienced a major incident on June 24, 2026 affecting api.honeycomb.io - US1 Event Ingest and ui.honeycomb.io - US1 Trigger & SLO Alerting and 1 more component, lasting 50m. The incident has been resolved; the full update timeline is below.

Started
Jun 24, 2026, 06:14 PM UTC
Resolved
Jun 24, 2026, 07:04 PM UTC
Duration
50m
Detected by Pingoru
Jun 24, 2026, 06:14 PM UTC

Affected components

api.honeycomb.io - US1 Event Ingestui.honeycomb.io - US1 Trigger & SLO Alertingapi.eu1.honeycomb.io - EU1 Event Ingestui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting

Update timeline

  1. investigating Jun 24, 2026, 06:14 PM UTC

    We are investigating an issue with delayed ingest in the US and EU region. Our engineers are rolling back a recent deploy. SLOs and Trigger evaluations may also be delayed.

  2. monitoring Jun 24, 2026, 06:22 PM UTC

    We have rolled back the deploy and ingest service has recovered. There has been an ingest outage from 17:55 - 18:14 UTC. We have also observed an delay for Service Maps.

  3. monitoring Jun 24, 2026, 06:31 PM UTC

    Triggers, SLOs and Service Maps are recovered. We are continuing to monitoring the Ingest Service

  4. resolved Jun 24, 2026, 07:04 PM UTC

    All services have been fully recovered. Impact window: 17:55–18:17 UTC Regions affected: Primary impact in US. The EU region was affected to a much lesser degree. During this period, the following effects may have occurred: Ingest: Some data was not ingested, resulting in complete or partial data loss for events sent during the window. Triggers: Triggers may have failed to fire within the impact window. SLOs: SLI values across the affected window are skewed by the missing data and may show artificial dips or accelerated budget burn. Service Maps: Maps covering the outage window are incomplete. Services and dependencies may be under-counted, as their traces were not ingested. We apologize for the disruption. Please reach out if you have any questions about how this may have affected your data.