# Honeycomb change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [Honeycomb](https://rewindex.com/company/honeycomb.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 15 | 15 | 2026-07-02 18:10 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-07-02 18:10 UTC | Major incident | [Major incident: honeycomb.io marketing website not working](https://rewindex.com/change/iefa428a032ab34.md) | outage | Honeycomb’s marketing website, www.honeycomb.io, was not working in a major-impact incident starting 2026-07-02 18:10 UTC and resolved at 2026-07-03 00:31 UTC, lasting 6 h 20 min. Honeycomb reported that clearing the CDN cache appeared to solve the issue. | | 2026-06-24 18:14 UTC | Major incident | [Major incident: Ingest Outage in US and EU](https://rewindex.com/change/i03a59dc53339e9.md) | outage | Honeycomb reported a major US and EU ingest outage starting 2026-06-24 18:14 UTC, resolved at 19:04 UTC after 50 min. Impact was primarily US: some telemetry was lost, triggers may not have fired, and SLO evaluations and Service Maps were delayed. Honeycomb rolled back a recent deploy; the postmortem reports telemetry gaps up to half an hour. | | 2026-06-18 19:10 UTC | Major incident | [Major incident: Enhance Issues](https://rewindex.com/change/i6c821ff7aa49e4.md) | outage | Honeycomb reported a major incident affecting EU1 Enhance and US1 Enhance, with enhance-related requests failing to complete beginning June 17th. The incident record started and resolved at 2026-06-18 19:10 UTC (computed duration: 0 min); Honeycomb said it deployed a fix and Enhance was fully operational. | | 2026-05-01 13:22 UTC | Major incident | [Major incident: Query interuption due to database failover in the EU region](https://rewindex.com/change/i41ce64ab87bcd1.md) | outage | Honeycomb reported a major EU-region query outage after an automated database failover at 12:50 UTC affected query engine connection pools; queries failed for roughly 10 minutes before self-resolving. The listed start is 2026-05-01 13:22 UTC and resolution is 2026-05-01 12:30 UTC; computed duration is unknown. | | 2026-04-20 16:56 UTC | Major incident | [Major incident: Activity Log events interrupted for EU](https://rewindex.com/change/ic99a51f17cfe92.md) | outage | Honeycomb reported a major EU1 Activity Log interruption, with possible event data loss. The recorded incident started at 2026-04-20 16:56 UTC and resolved at 2026-04-20 17:02 UTC (6 min), though the vendor said interruptions began around 15:51 UTC. Activity Log returned to operational status, and most events should be recovered. | | 2026-04-10 13:41 UTC | Major incident | [Major incident: Ingest issues for some customers](https://rewindex.com/change/i62ee27a3652868.md) | outage | Honeycomb reported a major US1 Event Ingest outage affecting data ingestion for some teams on Classic environments, from 2026-04-10 13:41 UTC to 2026-04-10 17:24 UTC (3 h 42 min). Honeycomb applied a manual fix, then confirmed the fix covered all impacted and potentially impacted environments and related ingest errors should no longer occur. | | 2026-04-09 10:12 UTC | Major incident | [Major incident: Partial Querying Outage](https://rewindex.com/change/ibc31808268e50a.md) | outage | Honeycomb reported a major partial querying outage affecting US1 Querying, with possible Trigger and SLO alert failures, approximately 8:58 - 9:18 UTC. The incident records start and resolution at 2026-04-09 10:12 UTC (computed duration: 0 min); Honeycomb said the cause was identified and mitigated. | | 2026-03-18 18:07 UTC | Major incident | [Critical incident: Honeycomb UI displaying an error](https://rewindex.com/change/i8c5a968e48e30f.md) | outage | Honeycomb reported a critical incident affecting ui.honeycomb.io - US1 App Interface, with the UI displaying an error. It started at 2026-03-18 18:07 UTC and was resolved at 2026-03-18 18:18 UTC, lasting 11 min; Honeycomb said it identified the issue and shipped a fix. | | 2026-01-15 15:46 UTC | Major incident | [Major incident: Increased Latency and Errors for Events Ingest](https://rewindex.com/change/i7b655b975b7adb.md) | degradation | Honeycomb reported a major incident affecting some event ingest requests in the US, with increased latency and higher-than-normal error rates. It started and was resolved at 2026-01-15 15:46 UTC (recorded duration: 0 min); service stabilized and returned to normal, with monitoring continuing. | | 2025-12-05 20:49 UTC | Major incident | [Major incident: Querying and Ingest issues in EU](https://rewindex.com/change/icef24bd059a4db.md) | outage | Honeycomb reported a major EU incident affecting event ingest, querying, Activity Log, and Trigger & SLO alerting, starting 2025-12-05 20:49 UTC and lasting 11 days 18 h. Some environments saw elevated ingest errors and delayed notifications; Honeycomb reported a critical loss of Kafka redundancy and migrated to a new Kafka cluster, with all systems operational at resolution. | | 2025-10-20 14:16 UTC | Major incident | [Major incident: Delays in SLO, Service Maps processing](https://rewindex.com/change/if85d7ff01e9248.md) | degradation | Honeycomb reported a major US1 degradation starting 2025-10-20 14:16 UTC, with SLO and Service Maps processing delays exceeding 5 minutes and later querying and trigger delays. Constrained EC2 capacity in AWS us-east-1 was cited; resolution came at 2025-10-21 15:41 UTC after 25 h 24 min, with no customer data reaching its load balancers lost. | | 2025-10-20 07:24 UTC | Major incident | [Major incident: Investigating Querying Issues](https://rewindex.com/change/if5e29ab3075a34.md) | degradation | Honeycomb reported major degradation in US1 Querying and Trigger & SLO Alerting from 2025-10-20 07:24 UTC to 2025-10-20 10:04 UTC, lasting 2 h 40 min. Historical and trace queries could fail or slow down, alerts could be missed or delayed, and query results might not be saved. Honeycomb attributed the issue to AWS and confirmed full recovery. | | 2025-08-13 17:10 UTC | Major incident | [Major incident: Delayed ingestion of events in EU region](https://rewindex.com/change/idd4a4b2b8577a8.md) | degradation | Honeycomb reported major EU event-ingestion delays that could leave triggers, SLOs, and queries temporarily missing data. All events were processed after traffic rebalancing and scaling. The incident is resolved, but timestamps conflict: start 2025-08-13 17:10 UTC, resolution 2025-08-13 09:30 UTC; computed duration is unknown. | | 2025-08-12 15:17 UTC | Major incident | [Major incident: Ingestion delays in EU](https://rewindex.com/change/i48a5289857d829.md) | degradation | Honeycomb reported major EU ingestion delays affecting EU1 Querying and potentially Trigger & SLO Alerting, starting 2025-08-12 15:17 UTC and resolved at 2025-08-12 15:37 UTC (20 min). All traffic was accepted, but data could appear late in queries; load-balancing ingestion traffic restored normal performance. | | 2025-06-26 00:08 UTC | Major incident | [Major incident: Queries are failing with errors](https://rewindex.com/change/i58c9d5f240ae8b.md) | outage | Honeycomb reported a major incident affecting EU1 and US1 Querying, with errors rendering query results. It started at 2025-06-26 00:08 UTC and was resolved at 2025-06-26 01:00 UTC; the recorded duration was 51 min. Honeycomb reverted a build and reported querying restored at 00:20 UTC. | --- Canonical: https://rewindex.com/company/honeycomb/changes · Markdown: https://rewindex.com/company/honeycomb/changes.md · JSON: https://rewindex.com/api/v1/companies/honeycomb/changes · Generated 2026-10-18T03:21:52.737Z