CloudAMQP incident
Missing broker and queue metrics for some legacy metrics integrations
Resolved after 23 hours 55 minutes, affecting Metrics, on October 30, 2026.
Between 19:42 UTC on 29 October and 05:04 UTC on 30 October, broker and queue level metrics were not delivered to legacy third-party metrics integrations (Datadog, CloudWatch, New Relic, Stackdriver, Splunk, Librato) for a subset of clusters. Server metrics were not affected. Prometheus-based (v3) metrics and integrations were not affected. The cause was a stalled process in our legacy metrics collection pipeline. It has been restarted and delivery has resumed. Metrics from the affected period cannot be backfilled. We are adding safeguards so this failure is detected and recovered from automatically.
Affected components
Update timeline
- resolved Oct 30, 2026, 05:08 AM UTC
Between 19:42 UTC on 29 October and 05:04 UTC on 30 October, broker and queue level metrics were not delivered to legacy third-party metrics integrations (Datadog, CloudWatch, New Relic, Stackdriver, Splunk, Librato) for a subset of clusters. Server metrics were not affected. Prometheus-based (v3) metrics and integrations were not affected. The cause was a stalled process in our legacy metrics collection pipeline. It has been restarted and delivery has resumed. Metrics from the affected period cannot be backfilled. We are adding safeguards so this failure is detected and recovered from automatically.
Your product runs on more than CloudAMQP
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services