CloudAMQP Outage History

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.

CloudAMQP's Management Interface experienced a 502 Bad Gateway error for 31 minutes, affecting customers trying to access the Management UI through SSO via the CloudAMQP Console. The issue was caused by code changes that altered the communication schema between backend services and the SSO component, creating a proxy configuration conflict. The problem was resolved by fixing the SSO component, while AMQP clusters remained healthy and users could still access the Management UI using direct broker URLs with credentials.

CloudAMQP experienced a metrics delivery delay affecting 12% of API-based v1/v2 integrations for 18 minutes. The team added additional capacity to handle the backlog and successfully resolved the issue within the expected timeframe.

CloudAMQP experienced a 7-minute incident where queue metrics sent to legacy metrics integrations were delayed due to processing issues. The metrics component was affected, causing delays in metric data delivery to integrated systems. The issue was quickly identified and resolved within the brief timeframe.

CloudAMQP experienced performance issues with Coralogix log delivery that affected the service's logging functionality. The incident was classified as minor and lasted approximately 17.1 hours. A fix was implemented and monitored before the issue was fully resolved.