Honeycomb.io Outage History

Honeycomb.io is up right now

There were 15 Honeycomb.io outages since February 10, 2026 totaling 41h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.honeycomb.io

Notice May 1, 2026

Gap in Activity Log data in the EU region.

Detected by Pingoru
May 01, 2026, 07:51 PM UTC
Resolved
May 01, 2026, 01:00 PM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Major May 1, 2026

Query interuption due to database failover in the EU region

Detected by Pingoru
May 01, 2026, 01:22 PM UTC
Resolved
May 01, 2026, 12:30 PM UTC
Duration
—
Timeline · 1 update
  1. 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 →

Notice April 30, 2026

Links in Slack triggers not working

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
  1. 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

  2. monitoring Apr 30, 2026, 03:07 PM UTC

    The fix has been implemented and links on Slack triggers are functional again.

  3. resolved Apr 30, 2026, 04:37 PM UTC

    We are confident the issue is fully resolved.

Read the full incident report →

Major April 20, 2026

Activity Log events interrupted for EU

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
  1. 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.

  2. 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 →

Minor April 15, 2026

Activity Log ingest is delayed

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
  1. identified Apr 15, 2026, 07:04 PM UTC

    Activity Log is experiencing a delay in processing events. We are working on remediating the issue.

  2. 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 →

Minor April 14, 2026

Activity Log delayed ingest in EU

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
  1. 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.

  2. monitoring Apr 14, 2026, 10:08 PM UTC

    A fix has been implemented and we are monitoring recovery.

  3. resolved Apr 14, 2026, 10:37 PM UTC

    All activity log data is now live and up to date.

Read the full incident report →

Major April 10, 2026

Ingest issues for some customers

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
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. monitoring Apr 10, 2026, 02:32 PM UTC

    The manual fix has been applied to all environments.

  6. 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.

  7. 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 →

Notice April 9, 2026

SLO processing delay in US

Detected by Pingoru
Apr 09, 2026, 05:43 PM UTC
Resolved
Apr 09, 2026, 07:00 PM UTC
Duration
1h 16m
Timeline · 1 update
  1. resolved Apr 09, 2026, 05:43 PM UTC

    We have detected and remediated an issue around our SLO processing pipeline. From 17:00 to 17:15 UTC, events were being delayed, and alerts may likewise have been a few minutes late. Processing has caught up and is currently within normal operational ranges.

Read the full incident report →

Minor April 9, 2026

Activity log delay in production US

Detected by Pingoru
Apr 09, 2026, 11:52 AM UTC
Resolved
Apr 10, 2026, 07:10 PM UTC
Duration
1d 7h
Affected: ui.honeycomb.io - US1 Trigger & SLO Alertingui.honeycomb.io - US1 Activity Log
Timeline · 6 updates
  1. identified Apr 09, 2026, 11:52 AM UTC

    We have identified the cause and are working to resolve the issue.

  2. identified Apr 09, 2026, 08:24 PM UTC

    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.

  3. identified Apr 09, 2026, 09:03 PM UTC

    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.

  4. identified Apr 09, 2026, 11:43 PM UTC

    SLOs experienced a period of additional processing delays. A fix has been deployed and recovery is ongoing.

  5. identified Apr 10, 2026, 12:05 AM UTC

    SLO processing has fully recovered.

  6. resolved Apr 10, 2026, 07:10 PM UTC

    All activity log data is now live and up to date.

Read the full incident report →

Major April 9, 2026

Partial Querying Outage

Detected by Pingoru
Apr 09, 2026, 10:12 AM UTC
Resolved
Apr 09, 2026, 10:12 AM UTC
Duration
—
Affected: ui.honeycomb.io - US1 Queryingui.honeycomb.io - US1 Trigger & SLO Alerting
Timeline · 1 update
  1. resolved Apr 09, 2026, 10:12 AM UTC

    We experienced a partial querying outage from approximately 8:58 - 9:18 UTC. This outage may have resulted in some Trigger and SLO alert failures for the duration of the outage. The cause of the outage has been identified and mitigated.

Read the full incident report →

Critical March 18, 2026

Honeycomb UI displaying an error

Detected by Pingoru
Mar 18, 2026, 06:07 PM UTC
Resolved
Mar 18, 2026, 06:18 PM UTC
Duration
11m
Affected: ui.honeycomb.io - US1 App Interface
Timeline · 3 updates
  1. investigating Mar 18, 2026, 06:07 PM UTC

    We are currently investigating this issue.

  2. identified Mar 18, 2026, 06:10 PM UTC

    We have identified the issue and are working on a fix.

  3. resolved Mar 18, 2026, 06:18 PM UTC

    The issue has been identified and we have shipped a fix.

Read the full incident report →

Minor March 12, 2026

Elevated Querying Errors

Detected by Pingoru
Mar 12, 2026, 11:55 AM UTC
Resolved
Mar 12, 2026, 01:39 PM UTC
Duration
1h 43m
Affected: ui.honeycomb.io - US1 Queryingui.honeycomb.io - US1 Trigger & SLO Alerting
Timeline · 3 updates
  1. identified Mar 12, 2026, 11:55 AM UTC

    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.

  2. identified Mar 12, 2026, 01:17 PM UTC

    We have rolled back a code change to our query engine, but our triggers service has not recovered. We are investigating.

  3. resolved Mar 12, 2026, 01:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 10, 2026

Degraded Ingest due to database connectivity issues

Detected by Pingoru
Mar 10, 2026, 01:50 PM UTC
Resolved
Mar 10, 2026, 02:14 PM UTC
Duration
24m
Affected: api.honeycomb.io - US1 Event Ingest
Timeline · 3 updates
  1. investigating Mar 10, 2026, 01:50 PM UTC

    We are currently seeing elevated errors in connecting to some of our databases, which results in low amounts of Ingest traffic being rejected. We are looking into correcting the situation.

  2. monitoring Mar 10, 2026, 01:56 PM UTC

    We have stabilized the cluster and are monitoring the state while investigating to understand what triggered the degradation. Overall, 0.04% traffic was rejected with an error due to this degradation during the 20 minute window we were impaired.

  3. resolved Mar 10, 2026, 02:14 PM UTC

    This incident is now resolved. We are also noting that some other parts of honeycomb (the query UI) may have seen spurious failures as well during the impacted period (13:22—13:44 UTC).

Read the full incident report →

Minor February 18, 2026

Partial query outage in EU1

Detected by Pingoru
Feb 18, 2026, 11:07 PM UTC
Resolved
Feb 18, 2026, 11:07 PM UTC
Duration
—
Affected: ui.eu1.honeycomb.io - EU1 Querying
Timeline · 1 update
  1. resolved Feb 18, 2026, 11:07 PM UTC

    Between 22:10 and 22:40 UTC on Feb18, 2026 Honeycomb experienced a partial query outage in our EU environment. The incident has been resolved, and we are continuing to investigate the contributing factors.

Read the full incident report →

Minor February 10, 2026

Query Errors

Detected by Pingoru
Feb 10, 2026, 08:18 PM UTC
Resolved
Feb 10, 2026, 08:30 PM UTC
Duration
11m
Affected: ui.honeycomb.io - US1 Queryingui.eu1.honeycomb.io - EU1 Querying
Timeline · 2 updates
  1. investigating Feb 10, 2026, 08:18 PM UTC

    We are aware of elevated errors in trigger evaluations and queries, and are working to resolve it

  2. resolved Feb 10, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Honeycomb.io downtime and outages?

Pingoru polls Honeycomb.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Honeycomb.io reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Honeycomb.io alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Honeycomb.io for free

5 free monitors · No credit card required