Outage in Honeycomb
Delay in SLO and errors in Trigger notifications
Resolved MinorIncident Report
An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.
Need to monitor Honeycomb outages?
One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.
Try IsDown risk-free
14-day free trial · No credit card required
Latest Updates ( sorted recent to last )
RESOLVED
3 months ago - at 07/21/2025 03:59PM
This incident has been resolved.
MONITORING
3 months ago - at 07/21/2025 03:25PM
An error in our production AWS configuration caused a brief interruption that affected Service Maps and caused an delay in delivering SLO notifications, and errors delivering Trigger notifications between 9:54AM UTC-5 and 10:05AM UTC-5. If any longer Triggers (1 day) would have activated within this window, they may not have sent a notification.
Latest Honeycomb outages
aws-service-degradation - about 20 hours ago
Delays in SLO, Service Maps processing - about 23 hours ago
Investigating Querying Issues - 1 day ago
Partially Degraded Honeycomb Intelligence Features - 13 days ago
ServiceMaps down due to issues with an upstream provider - 27 days ago
The Status Page Aggregator Built for IT Teams
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 4522 services available
Integrations with
