CloudAMQP incident

Monitoring Systems — False Alarms

Notice Resolved View vendor source →

CloudAMQP experienced a notice incident on May 30, 2026, lasting 13h 4m. The incident has been resolved; the full update timeline is below.

Started
May 30, 2026, 10:25 PM UTC
Resolved
May 31, 2026, 11:29 AM UTC
Duration
13h 4m
Detected by Pingoru
May 30, 2026, 10:25 PM UTC

Update timeline

  1. monitoring May 30, 2026, 10:25 PM UTC

    Between 17:30 and 20:00 UTC on 2026-05-30, our server monitoring system generated a large number of false "server_unreachable" alerts. Clusters were operational and healthy throughout this period — no customer data or message delivery was affected. The alerts were caused by a rolling restart of our monitoring service, during which individual monitoring workers went offline mid-cycle and lost state. This caused the workers to report connection timeouts for servers they could no longer reach — even though those servers were fully healthy. We apologize for any concern this may have caused.

  2. resolved May 31, 2026, 11:29 AM UTC

    This incident has been resolved.