CloudAMQP Outage History
Uptime record, past incidents, and downtime history for CloudAMQP.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 58.3% | 12 | 5 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 0% | 4 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 46 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Backend slow
Started: May 5, 10:23 AM
monitoring
Looks like we're back at full performance now.
May 5, 11:34 AM
monitoring
Still seeing slow requests, doing another investigation.
May 5, 11:23 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 5, 10:41 AM
investigating
We are currently experiencing issues with our backend services handling account and server creation.
This does not affect any running customer servers but might delay provisioning new servers.
May 5, 10:23 AM
Connecting issues in Azure West Europe
Started: May 3, 7:11 PM
identified
Servers in Azure West Europe can experience connection issues due to underlying issues at provider.
Latest update from Azure
"Current Status: We continue to investigate an availability issue caused by a subset of unhealthy backend storage infrastructure supporting Azure Virtual Machines and Azure Direct Drive in West Europe."
May 3, 7:14 PM
investigating
We are currently investigating this issue.
May 3, 7:11 PM
April 2026
Backend slow/unresponsible
Started: Apr 28, 10:27 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 28, 10:53 AM
identified
The issue has been identified and a fix is being implemented.
Apr 28, 10:49 AM
investigating
We are currently experiencing issues with our backend services handling account and server creation.
This does not affect any running customer servers but might delay provisioning new servers.
Apr 28, 10:27 AM
Connection issues in Azure region westus
Started: Apr 24, 9:36 AM
investigating
We are getting indications of instances being down in Azure region westus. We are investigating the issue.
Apr 24, 9:36 AM
Issues with Azure West US 3 region
Started: Apr 23, 10:10 AM
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.
Apr 23, 10:10 AM
Metrics integration issues
Started: Apr 23, 3:30 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 23, 6:53 AM
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.
Apr 23, 4:33 AM
Management Interface Unavailable - 502 Bad Gateway Response
Started: Apr 2, 2:41 PM
identified
We are continuing to work on a fix for this issue.
Apr 2, 3:07 PM
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.
Apr 2, 2:52 PM
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.
Apr 2, 2:41 PM
March 2026
AWS region me-south-1 outage
Started: Mar 2, 5:35 AM
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.
Mar 2, 8:19 PM
monitoring
AWS has an ongoing issue with multiple services in region me-south-1.
Shared server hummingbird-01 affected.
Mar 2, 5:35 AM
AWS region me-central-1 outage
Started: Mar 1, 1:20 PM
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.
Mar 2, 8:19 PM
monitoring
We are continuing to monitor. The outage is in regards to the AZ mec1-az2
Mar 2, 1:46 AM
monitoring
We are continuing to monitor for any further issues.
Mar 1, 1:23 PM
monitoring
We are continuing to monitor for any further issues.
Mar 1, 1:22 PM
monitoring
AWS has an ongoing issue with multiple services in region me-central-1.
Mar 1, 1:20 PM