CloudAMQP Outage History

CloudAMQP's monitoring system generated numerous false "server_unreachable" alerts between 17:30 and 20:00 UTC on May 30, 2026, caused by monitoring workers losing state during a rolling restart of the monitoring service. All clusters remained fully operational throughout the incident with no impact to customer data or message delivery. The false alerts were resolved and the incident was closed on May 31, 2026.

CloudAMQP instances in Azure West Europe experienced connectivity issues, connection failures, and unexpected restarts due to an underlying Microsoft Azure platform incident in the region. The issue affected a limited number of customers during a 4-minute window (14:09–14:13 UTC on May 23, 2026). Microsoft resolved the Azure Virtual Machines incident through automatic self-healing, restoring normal operations for all affected CloudAMQP instances.

CloudAMQP experienced an issue where system metrics were not being forwarded to legacy integrations, while Prometheus integrations remained unaffected. The incident lasted 1.6 hours and was resolved after implementing a fix and monitoring the results.

CloudAMQP experienced backend service issues that affected account and server creation processes for 30 minutes. Existing customer servers remained unaffected, but new server provisioning was delayed during the incident. The issue was identified and resolved with a backend fix that restored normal provisioning capabilities.

CloudAMQP experienced backend service slowdowns that affected account and server creation processes for 3.1 hours. Running customer servers remained unaffected, but new server provisioning was delayed during the incident. The issue was resolved after implementing a fix and monitoring performance recovery.

CloudAMQP experienced connection issues in the Azure West Europe region due to underlying infrastructure problems at Microsoft Azure, specifically affecting virtual machines and storage backend systems. The incident impacted servers' ability to establish reliable connections for approximately 6.6 hours. The issue was resolved after Azure addressed the unhealthy backend storage infrastructure that was causing the availability problems.

CloudAMQP experienced backend service issues caused by an abnormal increase in traffic, resulting in timeouts and slow responses that affected account creation, server provisioning, and configuration updates. Running customer servers remained unaffected throughout the incident. The issue was resolved after 39 minutes by increasing backend capacity to handle the elevated traffic load.

CloudAMQP experienced a major outage affecting instances in the Azure westus region, causing connection issues for users. The incident impacted Microsoft Azure components and prevented access to CloudAMQP services in that region. The issue was resolved after 1.7 hours of investigation and remediation.

CloudAMQP servers in the Azure West US 3 region experienced connection issues due to underlying problems with the Microsoft Azure infrastructure. The incident affected CloudAMQP services running on Microsoft Azure in that specific region. The connection issues were resolved after 48 minutes of disruption.

CloudAMQP experienced an 8.1-hour incident where legacy metrics integrations failed to receive metrics data, which also disrupted alarms based on broker metrics. Prometheus-based metrics integrations like Datadog v3 continued to function normally throughout the incident. The issue was resolved after implementing a fix and monitoring the results.