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 |
|---|---|---|---|
| April 2026 | 80% | 10 | 2 |
| March 2026 | 90.3% | 31 | 3 |
| February 2026 | 100% | 22 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 63 Days)
Feb 7
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
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