outages.live
Live

Honeycomb

Honeycomb is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 41 min

Longest incident

7 h 34 min

Components

14
api.honeycomb.io - US1 Event Ingest Operational
90 days agoNo incidentsToday
ui.honeycomb.io - US1 Querying Operational
90 days ago2 days with an incidentToday
ui.honeycomb.io - US1 App Interface Operational
90 days ago2 days with an incidentToday
ui.honeycomb.io - US1 Trigger & SLO Alerting Operational
90 days ago2 days with an incidentToday
ui.honeycomb.io - US1 Activity Log Operational
90 days agoNo incidentsToday
ui.honeycomb.io - US1 Enhance Operational
90 days agoNo incidentsToday
api.eu1.honeycomb.io - EU1 Event Ingest Operational
90 days agoNo incidentsToday
ui.eu1.honeycomb.io - EU1 App Interface Operational
90 days ago1 day with an incidentToday
ui.eu1.honeycomb.io - EU1 Querying Operational
90 days agoNo incidentsToday
ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting Operational
90 days ago1 day with an incidentToday
ui.eu1.honeycomb.io - EU1 Activity Log Operational
90 days agoNo incidentsToday
ui.eu1.honeycomb.io - EU1 Enhance Operational
90 days agoNo incidentsToday
www.honeycomb.io Operational
90 days agoNo incidentsToday
Sandbox Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 22, 2026

Duration1 h 1 min16:06 to 17:07Email notifications for SLOs, Triggers, and Anomaly Detection not sendingPartial outage

Between 03:53 PM UTC to 4:08 PM UTC we saw email send failures elevate in which a small number of customers (10 enterprise, 8 self-serve, and 1 pro plan) were impacted. This came to 508 emails in total, or ~1% of our daily email send. We are working to ensure this failure mode is not able to happen again.

Oct 20, 2026

Duration2 h 21 min14:04 to 16:26Slowness in US regionPartial outage

On October 20, we experienced roughly three hours of degraded service in the US region. * From 13:30 to 14:40 UTC, querying, the Honeycomb UI, the management API, and triggers experienced elevated latency and error rates, with the highest impact between 13:55 and 14:10 UTC. During this time, customers may have experienced slow or failed queries and a sluggish UI, and some trigger alerts may have been late or missed. * From 13:26 to approximately 16:10 UTC, SLO processing was delayed, so SLO data may have appeared out of date and burn alerts may have been delayed or missed during that time. * From 13:57 to 14:09 UTC, about half of requests to the event ingest API received 5xx errors, with lesser impact between 13:48 and 13:55 UTC \(1% error rate\) and for approximately a minute at 14:15 UTC \(1.9% error rate\). Telemetry rejected during these periods was not ingested unless the sender successfully retried it. Customers may see gaps in their data for those periods, including in triggers

Aug 21, 2026

Duration38 min15:21 to 15:59Canvas not loadingDegraded

This incident has been resolved.

Aug 10, 2026

Duration7 h 34 min13:01 to 20:35US1 cold query outageDegraded

The fix is in place and we've confirmed resolution. Queries and SLOs are processing normally.

Follow Honeycomb

Your coding agent knows when Honeycomb is down, and tells you when a failure is theirs, not yours. You can also get Honeycomb incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "honeycomb" and tell me if Honeycomb has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=honeycomb
Slack
/feed subscribe https://outages.live/feed.xml?providers=honeycomb

Go from tracking outages to fixing production issues with Polylane.

Try Polylane