Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Honeycomb Outage History

Every past Honeycomb outage tracked by IsDown, with detection times, duration, and resolution details.

There were 171 Honeycomb outages since October 2017. The 27 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 30, 2026

April 2026: Links in Slack triggers not working

Detected Apr 30, 2026 11:03 AM EDT · Resolved Apr 30, 2026 12:40 PM EDT · Duration about 2 hours

Honeycomb experienced an issue where links in Slack triggers were not functioning properly. The problem affected users' ability to use clickable links within Slack notification triggers from the service. The issue was identified, fixed, and fully resolved within 1.6 hours.

Major April 20, 2026

April 2026: Activity Log events interrupted for EU

Detected Apr 20, 2026 12:56 PM EDT · Resolved Apr 20, 2026 1:19 PM EDT · Duration 23 minutes

Honeycomb's Activity Log service was interrupted for EU customers starting around 15:51 UTC, causing potential data loss during the outage period. The incident lasted 11 minutes before the service was restored to operational status. Most events were recovered once the service came back online.

Minor April 15, 2026

April 2026: Activity Log ingest is delayed

Detected Apr 15, 2026 3:04 PM EDT · Resolved Apr 15, 2026 3:27 PM EDT · Duration 23 minutes

Honeycomb's Activity Log experienced a 23-minute delay in processing events, preventing real-time ingestion of activity data. The service team identified and resolved the processing bottleneck, restoring normal event ingestion. No data was lost during the incident.

Minor April 14, 2026

April 2026: Activity Log delayed ingest in EU

Detected Apr 14, 2026 5:36 PM EDT · Resolved Apr 14, 2026 6:40 PM EDT · Duration about 1 hour

Honeycomb's Activity Log service in the EU region experienced delayed data ingestion starting around 19:55 UTC, affecting the timeliness of activity log events. The engineering team identified and implemented a fix within approximately 30 minutes of detection. The incident was fully resolved after 1.1 hours with all activity log data restored to live status.

Major April 10, 2026

April 2026: Ingest issues for some customers

Detected Apr 10, 2026 9:41 AM EDT · Resolved Apr 10, 2026 1:27 PM EDT · Duration about 4 hours

Honeycomb experienced a major incident where some teams on Classic environments were unable to ingest their data through the api.honeycomb.io Event Ingest service. The engineering team identified the root cause and applied a manual fix to each affected environment while developing a systemic solution. The incident was fully resolved after 3.8 hours once the fix was uniformly applied to all impacted environments.

Minor April 9, 2026

April 2026: Activity log delay in production US

Detected Apr 9, 2026 7:52 AM EDT · Resolved Apr 10, 2026 3:11 PM EDT · Duration 1 day

Honeycomb experienced a 31-hour service disruption affecting activity logs, triggers, and SLOs in the US production environment. Users encountered delays when creating or updating triggers and SLOs, along with activity log unavailability and additional SLO processing delays. The issues were progressively resolved with fixes deployed for triggers and SLOs first, followed by full recovery of all activity log data.

Major March 18, 2026

March 2026: Honeycomb UI displaying an error

Detected Mar 18, 2026 2:07 PM EDT · Resolved Mar 18, 2026 2:21 PM EDT · Duration 13 minutes

The Honeycomb UI experienced a major outage displaying errors to users for 13 minutes. The issue affected the main app interface at ui.honeycomb.io, preventing users from accessing the application normally. The problem was identified and resolved with a shipped fix.

Minor March 10, 2026

March 2026: Degraded Ingest due to database connectivity issues

Detected Mar 10, 2026 9:50 AM EDT · Resolved Mar 10, 2026 10:24 AM EDT · Duration 34 minutes

Honeycomb experienced database connectivity issues that caused 0.04% of event ingest traffic to be rejected over a 20-minute period, with some users also experiencing spurious failures in the query UI. The database cluster was stabilized and the incident was resolved after 26 minutes of total impact.

Minor February 10, 2026

February 2026: Query Errors

Detected Feb 10, 2026 3:18 PM EST · Resolved Feb 10, 2026 3:33 PM EST · Duration 15 minutes