Honeycomb Outage History
Uptime record, past incidents, and downtime history for Honeycomb.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| July 2026 | 77.8% | 9 | 2 |
| June 2026 | 70% | 30 | 9 |
| May 2026 | 74.2% | 31 | 8 |
| April 2026 | 81% | 21 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
honeycomb.io marketing website not working
Started: Jul 2, 6:10 PM
monitoring
Clearing the CDN cache appears to have solved the issue.
Jul 2, 6:13 PM
investigating
We are currently investigating this issue.
Jul 2, 6:10 PM
June 2026
Activity Log delayed in US
Started: Jun 29, 10:07 PM
monitoring
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.
Jun 29, 10:07 PM
Ingest outage in EU
Started: Jun 25, 6:10 PM
monitoring
We are monitoring the situation. Events may have been delayed between 17:53 and 18:04 UTC.
Jun 25, 6:31 PM
investigating
We are investigating an issue with delayed ingest in the EU region. SLOs and Trigger evaluations may also be delayed.
Jun 25, 6:10 PM
Ingest Outage in US and EU
Started: Jun 24, 6:14 PM
monitoring
Triggers, SLOs and Service Maps are recovered. We are continuing to monitoring the Ingest Service
Jun 24, 6:31 PM
monitoring
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.
Jun 24, 6:22 PM
investigating
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.
Jun 24, 6:14 PM
MCP tool access degraded
Started: Jun 19, 4:39 PM
monitoring
We are aware of an issue affecting Honeycomb MCP. Write tool functionality may be degraded. Read tools are unaffected.
Jun 19, 5:18 PM
investigating
We are aware of an issue affecting Honeycomb MCP. Write tool functionality may be degraded. Read tools are unaffected.
Jun 19, 4:39 PM
Querying Issues
Started: Jun 17, 2:01 PM
monitoring
Querying in our Production EU Region is fully operational. We will continue to monitor for any abnormal behavior.
Jun 17, 3:29 PM
investigating
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.
Jun 17, 2:01 PM
Querying Issues in EU
Started: Jun 17, 12:01 PM
investigating
We are currently investigating the cause of slowness and query failures in our Production EU Region.
Jun 17, 12:01 PM
Delayed ingest in EU
Started: Jun 10, 8:58 PM
identified
The issue has been identified and a fix is being implemented.
Jun 10, 9:29 PM
investigating
Queries should no longer be delayed. SLOs and Trigger evaluations remain impacted.
Jun 10, 9:28 PM
investigating
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.
Jun 10, 8:58 PM
Canvas UI issues
Started: Jun 8, 4:37 PM
investigating
We are currently investigating this issue.
Jun 8, 4:37 PM
Canvas tools unavailable
Started: Jun 3, 8:50 PM
identified
Canvas agent cannot load honeycomb internal tools.
Jun 3, 8:50 PM
May 2026
Investigating querying issues
Started: May 21, 11:22 PM
investigating
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
May 22, 12:49 AM
investigating
We have identified and are working to resolve an issue that is causing query results to return inconsistent results.
May 21, 11:22 PM
activity log for US instance is delayed
Started: May 8, 8:00 AM
monitoring
Activity Log recovered at 07:00 UTC-07:00 today (about 6.5h ago). All streams are caught up.
May 8, 8:46 PM
monitoring
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.
May 8, 10:40 AM
monitoring
We are continuing to monitor for any further issues.
May 8, 10:22 AM
monitoring
We believe that the activity log should now be caught up.
May 8, 10:21 AM
monitoring
Backfilling of the past 2h30m of data is now in progress and should complete shortly.
May 8, 10:13 AM
identified
Activity log delay is rising, and is more than an hour behind due to a MySQL replica failover. Estimated recovery by 04:00 PDT.
May 8, 8:43 AM
April 2026
Links in Slack triggers not working
Started: Apr 30, 3:03 PM
monitoring
The fix has been implemented and links on Slack triggers are functional again.
Apr 30, 3:07 PM
identified
We discovered that links in Slack triggers are not working and have identified the cause and are in process of implementing a fix
Apr 30, 3:03 PM
Activity Log events interrupted for EU
Started: Apr 20, 4:56 PM
identified
Activity Log events are interrupted, starting from around 15:51UTC. Customers may experience some data lost since the beginning of the incident.
Apr 20, 4:56 PM
Activity Log ingest is delayed
Started: Apr 15, 7:04 PM
identified
Activity Log is experiencing a delay in processing events. We are working on remediating the issue.
Apr 15, 7:04 PM
Activity Log delayed ingest in EU
Started: Apr 14, 9:36 PM
monitoring
A fix has been implemented and we are monitoring recovery.
Apr 14, 10:08 PM
identified
Activity Log events may be delayed, starting from around 19:55UTC. We're actively working on remediation.
Apr 14, 9:36 PM
Ingest issues for some customers
Started: Apr 10, 1:41 PM
monitoring
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.
Apr 10, 3:21 PM
monitoring
The manual fix has been applied to all environments.
Apr 10, 2:32 PM
monitoring
We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.
Apr 10, 2:19 PM
identified
We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.
Apr 10, 1:55 PM
identified
We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.
Apr 10, 1:46 PM
identified
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.
Apr 10, 1:41 PM
Activity log delay in production US
Started: Apr 9, 11:52 AM
identified
SLO processing has fully recovered.
Apr 10, 12:05 AM
identified
SLOs experienced a period of additional processing delays. A fix has been deployed and recovery is ongoing.
Apr 9, 11:43 PM
identified
We have identified an issue with triggers and SLOs and have implemented a fix. Customers should no longer see degraded performance for triggers or SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes.
Apr 9, 9:03 PM
identified
We have identified an issue with triggers and SLOs and are actively investigating. Customers may experience delays when creating or updating triggers and SLOs. A fix for the activity log delay has been implemented and is in the process of recovering. Customers may continue to see activity log unavailability while this completes.
Apr 9, 8:24 PM
identified
We have identified the cause and are working to resolve the issue.
Apr 9, 11:52 AM
March 2026
Honeycomb UI displaying an error
Started: Mar 18, 6:07 PM
identified
We have identified the issue and are working on a fix.
Mar 18, 6:10 PM
investigating
We are currently investigating this issue.
Mar 18, 6:07 PM
Elevated Querying Errors
Started: Mar 12, 11:55 AM
identified
We have rolled back a code change to our query engine, but our triggers service has not recovered. We are investigating.
Mar 12, 1:17 PM
identified
We are investigating elevated error rates affecting queries in our US1 region. Our team is actively working on a resolution. We will provide updates as we learn more.
Mar 12, 11:55 AM