Connectivity issues in Azure West Europe
Affected: Microsoft Azure
CloudAMQP Outage History
CloudAMQP is up right nowCloudAMQP had 46 outages in the last 2 years totaling 3232h 12m of downtime — averaging 1.9 incidents per month.
There were 46 CloudAMQP outages since February 20, 2025 totaling 3232h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
Degraded management connectivity to Azure UAE North
Timeline · 3 updates
- identified Oct 06, 2026, 02:37 PM UTC
We are seeing degraded network connectivity between some non-Azure networks and Azure UAE North (azure-arm::uaenorth), caused by a routing problem at an upstream transit provider. All servers in the region are up and processing messages, and monitoring, metrics and logs are working as normal. Customers whose clients connect from networks affected by this routing problem may also see connection timeouts. We have reported the problem to the provider and are routing our own management traffic around it.
- monitoring Oct 06, 2026, 03:44 PM UTC
Routing is back to normal.
- resolved Oct 06, 2026, 03:48 PM UTC
This incident has been resolved.
Issues on shared server 'Seal'
Affected: Shared servers
Timeline · 4 updates
- investigating Aug 26, 2026, 01:27 PM UTC
We are currently investigating this issue.
- identified Aug 26, 2026, 01:28 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 26, 2026, 01:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 26, 2026, 01:57 PM UTC
This incident has been resolved.
DigitalOcean control panel and API outage
Affected: DigitalOcean AMS2DigitalOcean AMS3DigitalOcean FRA1DigitalOcean LON1DigitalOcean NYC2DigitalOcean NYC3DigitalOcean SFO1DigitalOcean SGP1DigitalOcean TOR1
Timeline · 2 updates
- monitoring Aug 24, 2026, 11:52 PM UTC
DigitalOcean is currently experiencing issues with its API and control panel and you may run into errors and higher latency while the issue persists
- resolved Aug 25, 2026, 11:58 PM UTC
This incident has been resolved.
Servers Unreacheable - Azure West US
Affected: Dedicated serversMicrosoft Azure
Timeline · 3 updates
- investigating Jul 23, 2026, 03:33 PM UTC
We've received various alert notifying us about couple of servers deployed on Azure West US not being reachable. Apparently this seems to be related specific to this region impacting 25% of the servers.
- monitoring Jul 23, 2026, 07:50 PM UTC
Microsoft Azure confirmed they were having network issues on West US region. For now, most of the servers are operational. We'll keep monitoring for the following hours.
- resolved Jul 23, 2026, 09:48 PM UTC
This incident has been resolved.
False positive server down messages sent
Affected: Dedicated serversBackend
Timeline · 7 updates
Monitoring Systems — False Alarms
Timeline · 2 updates
- 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.
- resolved May 31, 2026, 11:29 AM UTC
This incident has been resolved.
System metrics not forwarded to legacy integration
Affected: Metrics
Timeline · 4 updates
Backend slow
Affected: Backend
Timeline · 4 updates
- investigating May 19, 2026, 01:21 PM UTC
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.
- identified May 19, 2026, 01:36 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 19, 2026, 01:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 19, 2026, 01:50 PM UTC
This incident has been resolved.
Connecting issues in Azure West Europe
Affected: Microsoft Azure
Timeline · 3 updates
- investigating May 03, 2026, 07:11 PM UTC
We are currently investigating this issue.
- identified May 03, 2026, 07:14 PM UTC
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."
- resolved May 04, 2026, 01:44 AM UTC
This incident has been resolved.
Backend slow/unresponsible
Affected: Backend
Timeline · 4 updates
- investigating Apr 28, 2026, 10:27 AM UTC
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.
- identified Apr 28, 2026, 10:49 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 28, 2026, 10:53 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 28, 2026, 11:05 AM UTC
We had an abnormal increase in traffic causing timeouts and slow responses for customer.cloudamqp.com, we increased capacity and are back to normal. This did not affect any running clusters, just provisioning and configuration updates.
Connection issues in Azure region westus
Affected: Microsoft Azure
Timeline · 2 updates
- investigating Apr 24, 2026, 09:36 AM UTC
We are getting indications of instances being down in Azure region westus. We are investigating the issue.
- resolved Apr 24, 2026, 11:12 AM UTC
This incident has been resolved.
Issues with Azure West US 3 region
Affected: Microsoft Azure
Timeline · 2 updates
- investigating Apr 23, 2026, 10:10 AM UTC
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.
- resolved Apr 23, 2026, 10:56 AM UTC
This incident has been resolved.
Metrics integration issues
Affected: Metrics
Timeline · 4 updates
Monitoring Systems Short Outage and "Connection issues" Alarms
Timeline · 1 update
- resolved Apr 15, 2026, 03:32 PM UTC
One of our backend components suffered a small outage due to an unexpected full services restart. Connectivity with the servers were broken and service triggered alarms for many clusters. We apologize for the inconvenience. All clusters were operational and healthy within the incident/alarms timespan.
Management Interface Unavailable - 502 Bad Gateway Response
Affected: Shared serversDedicated servers
Timeline · 4 updates
- identified Apr 02, 2026, 02:41 PM UTC
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.
- identified Apr 02, 2026, 02:52 PM UTC
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 Apr 02, 2026, 03:07 PM UTC
We are continuing to work on a fix for this issue.
- resolved Apr 02, 2026, 03:12 PM UTC
The Management UI SSO shortcut is back to service. Impacted Clusters: All customers with clusters created more than 6 months ago Cause: Some code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up. Impact: Only the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API. Logging into the Management UI via Credentials and all Authentications Backends was functioning normally.
Metrics delivery delay for 12% of the fleet
Affected: Metrics
Timeline · 2 updates
- identified Mar 25, 2026, 05:45 PM UTC
We're currently experiencing issues with metrics delivery, this affects 12% of the API based v1/v2 integrations. We've added additional capacity and expect have handled the backlog within 20 minutes.
- resolved Mar 25, 2026, 06:03 PM UTC
This incident has been resolved.
Queue metrics for legacy integrations delayed
Affected: Metrics
Timeline · 3 updates
- identified Mar 18, 2026, 09:25 PM UTC
We noticed an issue with our queue metrics being sent to metrics integrations. there is currently a delay in processing, but we have identified an issue and expect the delay to be fixed shortly.
- monitoring Mar 18, 2026, 10:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 19, 2026, 03:50 AM UTC
This incident has been resolved.
Coralogix log delivery performance issues
Timeline · 3 updates
- investigating Mar 03, 2026, 09:11 PM UTC
We're currently experiencing issues with Coralogix log delivery.
- monitoring Mar 04, 2026, 11:16 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 04, 2026, 02:14 PM UTC
This incident has been resolved.
Metrics delivery outage for v3 Prometheus based metrics.
Affected: Metrics
Timeline · 5 updates
- investigating Mar 03, 2026, 06:28 PM UTC
We're currently experiencing issues with metrics delivery, this affects v3 (Prometheus based) metrics.
- identified Mar 03, 2026, 06:47 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 03, 2026, 07:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 03, 2026, 08:51 PM UTC
This incident has been resolved.
- postmortem Mar 04, 2026, 02:14 PM UTC
### Summary On March 3, an internal monitoring metric stopped being reported for approximately 14 hours. No customer metrics delivery was affected, all integrations continued operating normally. The missing metric caused our dashboards to display false failure rates, which was incorrectly reported as a metrics delivery outage. ### Impact None. Metrics continued to be delivered to all customer endpoints throughout the incident. ### Resolution The monitoring metric was restored and we have updated our alerting queries to be resilient to missing data, preventing false positives in the future.
AWS region me-south-1 outage
Affected: Shared serversDedicated servers
Timeline · 3 updates
- monitoring Mar 02, 2026, 05:35 AM UTC
AWS has an ongoing issue with multiple services in region me-south-1. Shared server hummingbird-01 affected.
- monitoring Mar 02, 2026, 08:19 PM UTC
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.
- resolved May 05, 2026, 06:55 AM UTC
We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to [email protected] if you have any questions.
AWS region me-central-1 outage
Affected: Dedicated servers
Timeline · 6 updates
- monitoring Mar 01, 2026, 01:20 PM UTC
AWS has an ongoing issue with multiple services in region me-central-1.
- monitoring Mar 01, 2026, 01:22 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 01, 2026, 01:23 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 02, 2026, 01:46 AM UTC
We are continuing to monitor. The outage is in regards to the AZ mec1-az2
- monitoring Mar 02, 2026, 08:19 PM UTC
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.
- resolved May 05, 2026, 06:55 AM UTC
We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to [email protected] if you have any questions.
Issues with shared server "chameleon"
Timeline · 3 updates
- investigating Feb 17, 2026, 07:31 PM UTC
We are currently investigating this issue.
- monitoring Feb 17, 2026, 09:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 18, 2026, 03:30 PM UTC
This incident has been resolved.
The shared server 'porpoise' is overloaded. We are investigating this!
Timeline · 3 updates
- investigating Feb 03, 2026, 02:47 PM UTC
We are currently investigating this issue.
- monitoring Feb 03, 2026, 03:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 03, 2026, 03:28 PM UTC
This incident has been resolved.
Azure outage
Affected: Microsoft Azure
Timeline · 2 updates
- monitoring Feb 03, 2026, 02:53 AM UTC
A known Azure outage is leading to an error that prevents instances being created for now.
- resolved Feb 03, 2026, 08:17 AM UTC
This incident has been resolved by Azure, https://azure.status.microsoft/en-us/status