Outage report · Partial outage

Honeycomb outage on Dec 5, 2025

Querying and Ingest issues in EU

SeverityPartial outage

StartedDec 5, 2025, 20:49UTC

ResolvedDec 17, 2025, 15:47UTC

Duration11d 18h

What happened

Honeycomb reported a partial outage starting Dec 5, 2025, 20:49 UTC, affecting api.eu1.honeycomb.io - EU1 Event Ingest, ui.eu1.honeycomb.io - EU1 Querying, ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting, ui.eu1.honeycomb.io - EU1 Activity Log. It was marked resolved at Dec 17, 2025, 15:47 UTC.

The incident lasted 11d 18h from first report to resolution.
It was the longest significant outage Honeycomb reported in the 12 months up to it.
Honeycomb had reported 2 other partial or major outages in the 90 days before it.
7 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Honeycomb

This incident started on December 5th, and is one of the longest in Honeycomb history, having been actively worked on and closed only on December 17th. Due to its impact and duration, we wanted to offer a partial and preliminary report to explain, at a high level, what happened. On December 5th, at 20:23 UTC, our Kafka cluster suffered a critical loss of redundancy. Our Kafka cluster contains multiple topics, including all telemetry events submitted by Honeycomb users, the rematerialization of state changes into the activity log, and multiple metadata topics used by Kafka to manage its own workloads. This led multiple partitions leaderless and by 20:35 UTC, we were getting alerts that roughly a quarter of our usual event topic partitions were unable to accept writes. For most Honeycomb customers, this does not result in ingest outages, because traffic gets redirected to other partitions environments can be assigned to. However, we noted some teams for whom all their assigned partitio

Read Honeycomb's official incident report ↗