- Detected by Pingoru
- Aug 21, 2026, 03:21 PM UTC
- Resolved
- Aug 21, 2026, 03:59 PM UTC
- Duration
- 37m
Affected: ui.honeycomb.io - US1 App Interfaceui.eu1.honeycomb.io - EU1 App Interface
Timeline · 3 updates
-
identified Aug 21, 2026, 03:21 PM UTC
Canvas is not loading for customers in the US and EU regions and we have identified what we believe to be the cause and are rolling out a fix.
-
monitoring Aug 21, 2026, 03:25 PM UTC
We have deployed the fix and are seeing recovery of normal Canvas functionality.
-
resolved Aug 21, 2026, 03:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 01:01 PM UTC
- Resolved
- Aug 10, 2026, 08:35 PM UTC
- Duration
- 7h 33m
Affected: ui.honeycomb.io - US1 Querying
Timeline · 2 updates
-
monitoring Aug 10, 2026, 01:01 PM UTC
From 11:36UTC to 12:43UTC, queries in US1 that read older data returned errors or timed out. Queries over recent data were un-affected, and no telemetry is being lost. The issue has been identified, and a fix is in place. We are currently monitoring the situation to confirm resolution.
-
resolved Aug 10, 2026, 08:35 PM UTC
The fix is in place and we've confirmed resolution. Queries and SLOs are processing normally.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 02:30 PM UTC
- Resolved
- Jul 31, 2026, 02:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 01:13 PM UTC
- Resolved
- Jul 28, 2026, 06:30 PM UTC
- Duration
- 1d 5h
Affected: ui.eu1.honeycomb.io - EU1 Queryingui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
Timeline · 7 updates
-
investigating Jul 27, 2026, 01:13 PM UTC
We are seeing triggers intermittently failing in the EU region. We are actively investigating the cause.
-
investigating Jul 27, 2026, 01:52 PM UTC
We are continuing to see issues with triggers and are also noticing issues with querying. We are investigating for the cause of both.
-
monitoring Jul 27, 2026, 04:01 PM UTC
We have identified the source of the issue, applied a temporary fix, and are working on a permanent fix. We continue to monitor the situation.
-
monitoring Jul 27, 2026, 07:46 PM UTC
We are seeing a regression in performance with partial degradation of both triggers and querying. We are working to remediate.
-
monitoring Jul 27, 2026, 10:51 PM UTC
The partial degradation has been resolved for all customers except for those specifically contacted. We are working on mitigation measures so that we can fully restore trigger functionality for everyone.
-
monitoring Jul 28, 2026, 06:21 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 28, 2026, 06:30 PM UTC
The degradation in querying and triggers has been resolved and we're back to full functionality.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 06:10 PM UTC
- Resolved
- Jul 03, 2026, 12:31 AM UTC
- Duration
- 6h 20m
Affected: www.honeycomb.io
Timeline · 3 updates
-
investigating Jul 02, 2026, 06:10 PM UTC
We are currently investigating this issue.
-
monitoring Jul 02, 2026, 06:13 PM UTC
Clearing the CDN cache appears to have solved the issue.
-
resolved Jul 03, 2026, 12:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 10:07 PM UTC
- Resolved
- Jun 30, 2026, 12:47 AM UTC
- Duration
- 2h 39m
Affected: ui.honeycomb.io - US1 Activity Log
Timeline · 2 updates
-
monitoring Jun 29, 2026, 10:07 PM UTC
Starting at 14:24 PT, there was an issue with the Activity Log causing events to stop being processed. You may notice a gap starting at that time. We are slowly backfilling these events and do not expect any data loss to occur. We expect the full data log to be restored around 17:30 PT.
-
resolved Jun 30, 2026, 12:47 AM UTC
Backfill of the Activity Log events has completed. All events during the affected period should be present.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 06:10 PM UTC
- Resolved
- Jun 25, 2026, 08:41 PM UTC
- Duration
- 2h 31m
Affected: api.eu1.honeycomb.io - EU1 Event Ingestui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
Timeline · 3 updates
-
investigating Jun 25, 2026, 06:10 PM UTC
We are investigating an issue with delayed ingest in the EU region. SLOs and Trigger evaluations may also be delayed.
-
monitoring Jun 25, 2026, 06:31 PM UTC
We are monitoring the situation. Events may have been delayed between 17:53 and 18:04 UTC.
-
resolved Jun 25, 2026, 08:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 06:14 PM UTC
- Resolved
- Jun 24, 2026, 07:04 PM UTC
- Duration
- 50m
Affected: 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
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 04:39 PM UTC
- Resolved
- Jun 19, 2026, 05:21 PM UTC
- Duration
- 41m
Timeline · 3 updates
-
investigating Jun 19, 2026, 04:39 PM UTC
We are aware of an issue affecting Honeycomb MCP. Write tool functionality may be degraded. Read tools are unaffected.
-
monitoring Jun 19, 2026, 05:18 PM UTC
We are aware of an issue affecting Honeycomb MCP. Write tool functionality may be degraded. Read tools are unaffected.
-
resolved Jun 19, 2026, 05:21 PM UTC
MCP Write Tools have been restored. MCP users may need to reconnect to see all available tools.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 07:10 PM UTC
- Resolved
- Jun 18, 2026, 07:10 PM UTC
- Duration
- —
Affected: ui.honeycomb.io - US1 Enhanceui.eu1.honeycomb.io - EU1 Enhance
Timeline · 1 update
-
resolved Jun 18, 2026, 07:10 PM UTC
Beginning June 17th, enhance-related requests were failing to complete. We've since identified and deployed a fix, and enhance is now fully operational. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 02:01 PM UTC
- Resolved
- Jun 17, 2026, 09:14 PM UTC
- Duration
- 7h 13m
Affected: ui.eu1.honeycomb.io - EU1 Querying
Timeline · 3 updates
-
investigating Jun 17, 2026, 02:01 PM UTC
We are continuing to investigate intermittent slowness and query failures affecting our Production EU Region. We will provide an update as soon as we have more information.
-
monitoring Jun 17, 2026, 03:29 PM UTC
Querying in our Production EU Region is fully operational. We will continue to monitor for any abnormal behavior.
-
resolved Jun 17, 2026, 09:14 PM UTC
We have identified the root cause of the intermittent slowness and query failures affecting our Production EU Region. The issue was triggered by a large volume of dataset deletions that caused elevated database load, resulting in query instability. No data was lost during this incident. Service has been restored. A fix has been applied to help prevent recurrence.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 12:01 PM UTC
- Resolved
- Jun 17, 2026, 12:32 PM UTC
- Duration
- 31m
Affected: ui.eu1.honeycomb.io - EU1 Querying
Timeline · 2 updates
-
investigating Jun 17, 2026, 12:01 PM UTC
We are currently investigating the cause of slowness and query failures in our Production EU Region.
-
resolved Jun 17, 2026, 12:32 PM UTC
The issue is now resolved and querying is back to fully functional.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 03:30 PM UTC
- Resolved
- Jun 11, 2026, 03:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 11, 2026, 11:17 PM UTC
Requests to Honeycomb's Query Data and Management APIs in the production-eu1 environment encountered increased error rates between approximately 15:35 and 22:24 UTC. Event ingestion was not affected. The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 08:58 PM UTC
- Resolved
- Jun 10, 2026, 10:02 PM UTC
- Duration
- 1h 3m
Affected: api.eu1.honeycomb.io - EU1 Event Ingestui.eu1.honeycomb.io - EU1 Queryingui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
Timeline · 4 updates
-
investigating Jun 10, 2026, 08:58 PM UTC
We are investigating an issue with delayed ingest in the EU region. Received events are still being stored, but there may be a delay in event retrieval in queries. SLOs and Trigger evaluations may also be delayed.
-
investigating Jun 10, 2026, 09:28 PM UTC
Queries should no longer be delayed. SLOs and Trigger evaluations remain impacted.
-
identified Jun 10, 2026, 09:29 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jun 10, 2026, 10:02 PM UTC
All services are now healthy.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 04:37 PM UTC
- Resolved
- Jun 08, 2026, 05:41 PM UTC
- Duration
- 1h 3m
Affected: ui.honeycomb.io - US1 App Interfaceui.eu1.honeycomb.io - EU1 App Interface
Timeline · 2 updates
-
investigating Jun 08, 2026, 04:37 PM UTC
We are currently investigating this issue.
-
resolved Jun 08, 2026, 05:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:50 PM UTC
- Resolved
- Jun 03, 2026, 08:51 PM UTC
- Duration
- 55s
Affected: ui.honeycomb.io - US1 App Interfaceui.eu1.honeycomb.io - EU1 App Interface
Timeline · 2 updates
-
identified Jun 03, 2026, 08:50 PM UTC
Canvas agent cannot load honeycomb internal tools.
-
resolved Jun 03, 2026, 08:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 11:22 PM UTC
- Resolved
- May 22, 2026, 04:42 PM UTC
- Duration
- 17h 20m
Affected: ui.honeycomb.io - US1 Queryingui.eu1.honeycomb.io - EU1 Querying
Timeline · 3 updates
-
investigating May 21, 2026, 11:22 PM UTC
We have identified and are working to resolve an issue that is causing query results to return inconsistent results.
-
investigating May 22, 2026, 12:49 AM UTC
Impact from this issue has concluded. For a period of time (different between US and EU instances, noted below), queries spanning data older than the most recent 2 hours with certain GROUP / WHERE clauses returned inconsistent results. Data was never lost, and reruns of the same queries will show the previously missing data. US impact times: 21:50 UTC - 23:20 UTC EU impact times: 20:50 UTC - 23:20 UTC
-
resolved May 22, 2026, 04:42 PM UTC
This is an administrative update, marking the incident as Resolved. There has been no further impact since 23:20UTC on May 21 2026.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 08:00 AM UTC
- Resolved
- May 11, 2026, 04:37 PM UTC
- Duration
- 3d 8h
Affected: ui.honeycomb.io - US1 Activity Log
Timeline · 7 updates
-
identified May 08, 2026, 08:43 AM UTC
Activity log delay is rising, and is more than an hour behind due to a MySQL replica failover.
-
monitoring May 08, 2026, 10:13 AM UTC
Backfilling of the past 2h30m of data is now in progress and should complete shortly.
-
monitoring May 08, 2026, 10:21 AM UTC
We believe that the activity log should now be caught up.
-
monitoring May 08, 2026, 10:22 AM UTC
We are continuing to monitor for any further issues.
-
monitoring May 08, 2026, 10:40 AM UTC
All activity log streams are now caught up, except for the query runs table, which should have all data since the start of the incident backfilled by 1600 PDT.
-
monitoring May 08, 2026, 08:46 PM UTC
Activity Log recovered at 07:00 UTC-07:00 today (about 6.5h ago). All streams are caught up.
-
resolved May 11, 2026, 04:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 01:00 PM UTC
- Resolved
- May 01, 2026, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 01, 2026, 07:51 PM UTC
The database failover that caused query issues earlier in the EU (https://status.honeycomb.io/incidents/n855d8kzp32y) has also had knock-on effects on our Activity Log beta feature. Due to recovery issues on the data replication flow used for this mechanism, activity log events will be missing from 12:45 UTC until 19:45 UTC, representing a 5 hour gap in events. We have identified configuration parameters that will be adjusted to reduce the likelihood of such losses in the future.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 12:30 PM UTC
- Resolved
- May 01, 2026, 12:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 01, 2026, 01:22 PM UTC
At 12:50, our main database underwent an automated failover. This failover led to issues with some of our query engine connection pools, and caused queries to fail for roughly 10 minutes before self resolving.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 03:03 PM UTC
- Resolved
- Apr 30, 2026, 04:37 PM UTC
- Duration
- 1h 33m
Affected: ui.honeycomb.io - US1 Trigger & SLO Alertingui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting
Timeline · 3 updates
-
identified Apr 30, 2026, 03:03 PM UTC
We discovered that links in Slack triggers are not working and have identified the cause and are in process of implementing a fix
-
monitoring Apr 30, 2026, 03:07 PM UTC
The fix has been implemented and links on Slack triggers are functional again.
-
resolved Apr 30, 2026, 04:37 PM UTC
We are confident the issue is fully resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 04:56 PM UTC
- Resolved
- Apr 20, 2026, 05:02 PM UTC
- Duration
- 6m
Affected: ui.eu1.honeycomb.io - EU1 Activity Log
Timeline · 2 updates
-
identified Apr 20, 2026, 04:56 PM UTC
Activity Log events are interrupted, starting from around 15:51UTC. Customers may experience some data lost since the beginning of the incident.
-
resolved Apr 20, 2026, 05:02 PM UTC
Activity Log is back to operational, and most events should be recovered.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 07:04 PM UTC
- Resolved
- Apr 15, 2026, 07:25 PM UTC
- Duration
- 20m
Affected: ui.honeycomb.io - US1 Activity Logui.eu1.honeycomb.io - EU1 Activity Log
Timeline · 2 updates
-
identified Apr 15, 2026, 07:04 PM UTC
Activity Log is experiencing a delay in processing events. We are working on remediating the issue.
-
resolved Apr 15, 2026, 07:25 PM UTC
Activity Log is ingesting events again. We had no loss in data.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 09:36 PM UTC
- Resolved
- Apr 14, 2026, 10:37 PM UTC
- Duration
- 1h
Affected: ui.eu1.honeycomb.io - EU1 Activity Log
Timeline · 3 updates
-
identified Apr 14, 2026, 09:36 PM UTC
Activity Log events may be delayed, starting from around 19:55UTC. We're actively working on remediation.
-
monitoring Apr 14, 2026, 10:08 PM UTC
A fix has been implemented and we are monitoring recovery.
-
resolved Apr 14, 2026, 10:37 PM UTC
All activity log data is now live and up to date.
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 01:41 PM UTC
- Resolved
- Apr 10, 2026, 05:24 PM UTC
- Duration
- 3h 42m
Affected: api.honeycomb.io - US1 Event Ingest
Timeline · 7 updates
-
identified Apr 10, 2026, 01:41 PM UTC
We have confirmed reports of some teams getting issues ingesting their data. We have identified a probable source behind this behavior and are currently trying to correct it.
-
identified Apr 10, 2026, 01:46 PM UTC
We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.
-
identified Apr 10, 2026, 01:55 PM UTC
We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.
-
monitoring Apr 10, 2026, 02:19 PM UTC
We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.
-
monitoring Apr 10, 2026, 02:32 PM UTC
The manual fix has been applied to all environments.
-
monitoring Apr 10, 2026, 03:21 PM UTC
We are continuing to work on the systemic solution and monitor. We'll leave the incident open until we're able to confirm the issue won't recur.
-
resolved Apr 10, 2026, 05:24 PM UTC
We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.
Read the full incident report →
