
Honeycomb Status
Real-time updates of Honeycomb issues and outages
Honeycomb status is Operational
Honeycomb ui.honeycomb.io - US1 Querying
Honeycomb ui.honeycomb.io - US1 Trigger & SLO Alerting
Active Incidents
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.
Recently Resolved Incidents
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
Honeycomb Outage Survival Guide
Honeycomb Components
Honeycomb api.honeycomb.io - US1 Event Ingest
Honeycomb ui.honeycomb.io - US1 Querying
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
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.
Honeycomb ui.honeycomb.io - US1 App Interface
Honeycomb ui.honeycomb.io - US1 Trigger & SLO Alerting
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
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.