Looking for an update now? Check the current status, or follow CloudAMQP for future changes.
91.6%of 83 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
90.3%
31
3
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
The issue has been identified and a fix is being implemented.
investigating
Starting at 09:17 UTC on 9 Nov 2026, Microsoft Azure reported that multiple network devices in the North Europe region experienced power loss. Some servers in the region are currently unreachable, and clusters may experience latency, packet drops or connection issues. Multi-node clusters with nodes in other availability zones may continue to serve traffic. Azure is actively working on recovering the affected devices. We are monitoring the situation and will post updates as we learn more.
Link to Azure Service Issue https://app.azure.com/h/2J8J-GK8/bf9a9f
We can see that servers are slowly coming back. Our team will monitor the situation. Please get in contact with CloudAMQP Support if there are any issues.
identified
Azure has identified an unhealthy supporting storage system that is currently unable to process requests normally. While this is correlated with the observed service impact, the underlying trigger remains under investigation. We are aware of this issue and are actively investigating the issue.
identified
Azure are aware of this issue and are actively investigating.
https://app.azure.com/h/7PZM-X10/bf9a9f
investigating
We're investigating connectivity issues affecting some servers in Azure Brazil South.
Dedicated serversGoogle Cloud Platform Google Compute Engine
monitoring
We are continuing to monitor for any further issues.
monitoring
GCE has confirmed that a power outage in europe-west2-b caused the disruption. The power issue has been mitigated, and full recovery of affected workloads is tentatively expected by 13:00 UTC today. We continue to monitor the recovery.
monitoring
GCE is still reporting issues, but we are seeing some API calls succeed.
investigating
Incident is limited to servers in europe-west2-b
investigating
We are continuing to investigate this issue.
investigating
We're investigating connectivity issues affecting some servers in Google europe-west2. We'll post an update as soon as we know more.
We have been able to establish communication with instances in Azure West Europe. Majority of the instances are back up and running. Azure still has some VMs to resolve.
identified
Azure has identified this issue. They have narrowed the issue to storage accessibility affecting the region. Their teams is actively performing recovery actions on the affected infrastructure while continuing to investigate the underlying cause. We are monitoring recovery progress and working to restore affected resources.
investigating
Azure is aware of this issue and are actively investigating. We'll post another update as soon as we know more.
investigating
We're investigating connectivity issues affecting some servers in Azure West Europe. We'll post an update as soon as we know more.
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Legacy Incident Archive
15 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
Issues with Azure West US 3 region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Servers in Azure West US 3 can experience connection issues due to underlying issues at provider. We monitor and will update when we know more.
Metrics integration issues
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
There appears to be an issue regarding sending metrics to all Legacy metrics integrations. Alarms based on broker metrics also got affected.
We are currently investigating the issue
Prometheus based metrics (Datadog v3 etc) not affected.
Management Interface Unavailable - 502 Bad Gateway Response
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
The Management UI and brokers are serving traffic normally. You can still use the Management UI by using the Broker URL and properly typing User and Password.
The impact is related to our backend service logs into Management UI via CloudAMQP SSO.
identified
Customers are experiencing Management UI being unavailable with 502 Bad Gateway.
Timeline:
- 14:16 UTC -> The issue was identified
- 14:30 UTC -> Recent code changes were reverted. No relationship with incident noted.
March 2026
AWS region me-south-1 outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are still experiencing issues with this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.
monitoring
AWS has an ongoing issue with multiple services in region me-south-1.
Shared server hummingbird-01 affected.
AWS region me-central-1 outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are still experiencing issues with all AZ's in this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.
monitoring
We are continuing to monitor. The outage is in regards to the AZ mec1-az2
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
AWS has an ongoing issue with multiple services in region me-central-1.
