Companies / observability
Honeycomb
224incidents since 2017-10-16
80major or critical
4in the last 90 days
0silently edited or deleted
Recent notable changes
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: honeycomb.io marketing website not working 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. | Major incident | |
| Major incident: Ingest Outage in US and EU 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. | Major incident | |
| Major incident: Enhance Issues 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. | Major incident | |
| Major incident: Query interuption due to database failover in the EU region 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. | Major incident | |
| Major incident: Activity Log events interrupted for EU 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. | Major incident | |
| Major incident: Ingest issues for some customers 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. | Major incident | |
| Major incident: Partial Querying 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. | Major incident | |
| Critical incident: Honeycomb UI displaying an error 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. | Major incident | |
| Major incident: Increased Latency and Errors for Events Ingest 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. | Major incident | |
| Major incident: Querying and Ingest issues in EU 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. | Major incident |
Full Honeycomb change timeline, with diffs →
Status incident history
Honeycomb status incidents per year
Data table
| Year | Incidents | Major/critical |
|---|---|---|
| 2017 | 2 | 0 |
| 2018 | 8 | 3 |
| 2019 | 13 | 7 |
| 2020 | 12 | 4 |
| 2021 | 23 | 7 |
| 2022 | 31 | 15 |
| 2023 | 41 | 14 |
| 2024 | 31 | 12 |
| 2025 | 27 | 9 |
| 2026 | 36 | 9 |
Incidents per month, last 36 months
criticalmajorminornonemaintenanceunknown
Data table
| Month | Impact | Incidents |
|---|---|---|
| 2023-10 | minor | 1 |
| 2023-11 | critical | 1 |
| 2023-11 | major | 4 |
| 2023-11 | none | 1 |
| 2024-01 | major | 1 |
| 2024-03 | major | 1 |
| 2024-03 | minor | 1 |
| 2024-04 | critical | 1 |
| 2024-04 | major | 1 |
| 2024-04 | minor | 2 |
| 2024-05 | critical | 1 |
| 2024-05 | minor | 1 |
| 2024-05 | none | 1 |
| 2024-06 | critical | 2 |
| 2024-06 | minor | 2 |
| 2024-07 | minor | 2 |
| 2024-07 | none | 1 |
| 2024-08 | critical | 1 |
| 2024-08 | major | 2 |
| 2024-09 | major | 1 |
| 2024-09 | minor | 3 |
| 2024-10 | major | 1 |
| 2024-10 | minor | 1 |
| 2024-11 | minor | 2 |
| 2024-11 | none | 2 |
| 2024-12 | none | 1 |
| 2025-01 | critical | 1 |
| 2025-01 | minor | 1 |
| 2025-01 | none | 2 |
| 2025-02 | none | 1 |
| 2025-03 | major | 1 |
| 2025-03 | minor | 1 |
| 2025-04 | major | 1 |
| 2025-04 | minor | 1 |
| 2025-04 | none | 1 |
| 2025-05 | minor | 1 |
| 2025-05 | none | 1 |
| 2025-06 | major | 1 |
| 2025-06 | minor | 1 |
| 2025-07 | minor | 2 |
| 2025-07 | none | 1 |
| 2025-08 | major | 2 |
| 2025-08 | minor | 2 |
| 2025-09 | minor | 1 |
| 2025-10 | major | 2 |
| 2025-10 | none | 1 |
| 2025-11 | minor | 1 |
| 2025-12 | major | 1 |
| 2026-01 | major | 1 |
| 2026-01 | minor | 2 |
| 2026-02 | minor | 2 |
| 2026-03 | critical | 1 |
| 2026-03 | minor | 2 |
| 2026-04 | major | 3 |
| 2026-04 | minor | 3 |
| 2026-04 | none | 2 |
| 2026-05 | major | 1 |
| 2026-05 | minor | 2 |
| 2026-05 | none | 1 |
| 2026-06 | major | 2 |
| 2026-06 | minor | 9 |
| 2026-07 | major | 1 |
| 2026-07 | minor | 2 |
| 2026-08 | minor | 2 |
Silent edits
No silent edits or deletions detected for Honeycomb yet. We compare every 10-minute snapshot of each incident.
The Weekly Rewind: one short weekly email on what changed at Honeycomb and the other vendors we track, including silent edits. Subscribe →
Pricing, trust and legal pages
Page snapshot history
Data table
| Date | Page | Change |
|---|---|---|
| 2026-10-17 | Trust / security | baseline |
| 2026-10-17 | Terms of service | baseline |
| 2026-10-17 | Privacy policy | baseline |
| 2026-10-17 | Pricing | baseline |
| Page | URL | Versions | Last changed | Last fetched OK | History |
|---|---|---|---|---|---|
| Privacy policy | honeycomb.io/privacy | 1 | 2026-10-17 | 2026-10-17 | none yet |
| Terms of service | honeycomb.io/terms | 1 | 2026-10-17 | 2026-10-17 | none yet |
| Pricing | honeycomb.io/pricing | 1 | 2026-10-17 | 2026-10-17 | none yet |
| Trust / security | trust.honeycomb.io | 1 | 2026-10-17 | 2026-10-17 | none yet |
No changes since the first snapshot. Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
Incident timeline
Latest 100 of 224 incidents. Full list: last 90 days · JSON · Markdown