All Systems Operational

Uptime over the past 90 days. View historical uptime.
api.honeycomb.io - US1 Event Ingest ? Operational
90 days ago
100.0 % uptime
Today
ui.honeycomb.io - US1 Querying ? Operational
90 days ago
99.66 % uptime
Today
ui.honeycomb.io - US1 App Interface ? Operational
90 days ago
100.0 % uptime
Today
ui.honeycomb.io - US1 Trigger & SLO Alerting Operational
90 days ago
99.65 % uptime
Today
ui.honeycomb.io - US1 Activity Log Operational
90 days ago
100.0 % uptime
Today
api.eu1.honeycomb.io - EU1 Event Ingest ? Operational
90 days ago
99.97 % uptime
Today
ui.eu1.honeycomb.io - EU1 App Interface ? Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 Querying ? Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 Trigger & SLO Alerting Operational
90 days ago
100.0 % uptime
Today
ui.eu1.honeycomb.io - EU1 Activity Log Operational
90 days ago
100.0 % uptime
Today
www.honeycomb.io ? Operational
Sandbox ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Nov 1, 2025

No incidents reported today.

Oct 31, 2025

No incidents reported.

Oct 30, 2025

No incidents reported.

Oct 29, 2025

No incidents reported.

Oct 28, 2025

No incidents reported.

Oct 27, 2025

No incidents reported.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025

No incidents reported.

Oct 22, 2025

No incidents reported.

Oct 21, 2025
Delays in SLO, Service Maps processing
Resolved - This incident has been resolved. At no point did we lose any customer data that hit our load balancers. Querying has been stable for hours, and all features that were degraded are functional.
Oct 21, 08:41 PDT
Update - Honeycomb core functionality is operational. Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. This is our final update for the night unless the situation degrades. We will continue to monitor the situation.
Oct 20, 17:11 PDT
Update - Service maps are up and running and errors have resolved. Querying, triggers and SLOs are continuing to improve and customers may see delays as functionality continues to improve. We are continuing to monitor the situation.
Oct 20, 16:08 PDT
Update - AWS is starting to show signs of recovery. Querying remains partially impacted and may take longer to return results. We are continuing to monitor the situation.
Oct 20, 13:06 PDT
Update - We’re currently observing that querying is seeing signs of recovery. We are continuing to monitor the situation
Oct 20, 10:39 PDT
Update - The networking issues in us-east-1 is affecting our query engine - customers may see errors or delays when running queries as a result.
Oct 20, 08:30 PDT
Update - SLO processing has recovered. Service Maps continues to be degraded but historical data can be queried.
Oct 20, 08:14 PDT
Monitoring - Due to constrained EC2 instance capacity in the AWS us-east-1 region, we are choosing to allocate the capacity we have to incoming events and telemetry. As such, customers may see over 5 minute delays in our processing of
- SLOs
- Service Maps
We do not expect a degradation of our core ingest -> query flow, and we do not expect triggers to be impacted
Oct 20, 07:16 PDT
Oct 20, 2025
Investigating Querying Issues
Postmortem - Read details
Oct 22, 16:03 PDT
Resolved - All affected systems have fully recovered.
Oct 20, 03:04 PDT
Monitoring - We are beginning to see recovery across our systems. We will continue to monitor the situation in case of any regressions.
Oct 20, 02:49 PDT
Update - We are currently experiencing degraded performance. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes trace queries. SLO and Trigger alerts may be missed or delayed. Queries may return results, but those results may not be saved, meaning that loading queries that other people have run may fail. After the problem resolves, queries may need to be rerun.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.
Oct 20, 01:46 PDT
Update - We are currently experiencing degraded performance for queries. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs, Triggers, and Traces.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.
Oct 20, 01:14 PDT
Identified - We are currently experiencing degraded performance for queries that access older data stored in cold storage. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs and Triggers.

Queries over recent or “hot” data are not impacted.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.
Oct 20, 00:24 PDT
Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage