Aug <var data-var='date'> 5</var>, <var data-var='time'>19:09</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'> 4</var>, <var data-var='time'>20:10</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'> 3</var>, <var data-var='time'>21:47</var> UTC Scheduled - We will run maintenance on a logging server. There might be a short cut-out of log streaming to external logging services.

Log server maintenance

Jul <var data-var='date'>23</var>, <var data-var='time'>21:48</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>19:50</var> UTC Monitoring - 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. Jul <var data-var='date'>23</var>, <var data-var='time'>15:33</var> UTC Investigating - 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.

Servers Unreacheable - Azure West US

Jun <var data-var='date'>26</var>, <var data-var='time'>14:44</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>26</var>, <var data-var='time'>14:22</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>26</var>, <var data-var='time'>09:17</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>26</var>, <var data-var='time'>08:38</var> UTC Investigating - We are currently investigating this issue. Jun <var data-var='date'>25</var>, <var data-var='time'>14:21</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>25</var>, <var data-var='time'>14:10</var> UTC Investigating - We are currently investigating this issue.

False positive server down messages sent

May <var data-var='date'>31</var>, <var data-var='time'>11:29</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>30</var>, <var data-var='time'>22:25</var> UTC Monitoring - 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.

Monitoring Systems  — False Alarms

May <var data-var='date'>23</var>, <var data-var='time'>17:23</var> UTC Resolved - Resolved — Microsoft has confirmed that the Azure West Europe Virtual Machines incident is resolved. The impact window was 14:09–14:13 UTC on 23 May 2026, during which a limited number of customers may have experienced connection failures or unexpected Virtual Machine restarts. The Azure environment self-healed and the service has been confirmed restored. Affected CloudAMQP instances should now be operating normally. May <var data-var='date'>23</var>, <var data-var='time'>16:21</var> UTC Investigating - We are investigating connectivity issues affecting some CloudAMQP instances in Azure West Europe. Affected instances may see connection failures or unexpected restarts. The root cause is an ongoing Microsoft Azure platform incident in the West Europe region (started 14:31 UTC, 23 May 2026). Microsoft is investigating.

Connectivity issues in Azure West Europe

May <var data-var='date'>22</var>, <var data-var='time'>04:50</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>22</var>, <var data-var='time'>04:08</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>22</var>, <var data-var='time'>03:16</var> UTC Investigating - Since around 8pm UTC last night, some metrics are not being forwarded to legacy integration. Prometheus integrations not affected. We are investingating.

System metrics not forwarded to legacy integration

May <var data-var='date'>19</var>, <var data-var='time'>13:50</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>13:41</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>19</var>, <var data-var='time'>13:36</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>19</var>, <var data-var='time'>13:21</var> UTC 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.

Backend slow

May <var data-var='date'> 5</var>, <var data-var='time'>13:23</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>11:34</var> UTC Update - Looks like we're back at full performance now. May <var data-var='date'> 5</var>, <var data-var='time'>11:23</var> UTC Update - Still seeing slow requests, doing another investigation. May <var data-var='date'> 5</var>, <var data-var='time'>10:41</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>10:23</var> UTC 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 <var data-var='date'> 5</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'> 5</var>, <var data-var='time'>08:17</var> UTC Update - We will reconnect our log shovel consumers, any log messages related to "logstream2" is totally normal. May <var data-var='date'> 5</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 5</var>, <var data-var='time'>07:52</var> UTC Scheduled - We'll be doing maintenance, should not cause any degradation if all goes as planned, we'll update here as we go along.

Backend maintenance

May <var data-var='date'> 5</var>, <var data-var='time'>06:55</var> UTC Resolved - 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 support@cloudamqp.com if you have any questions. Mar <var data-var='date'> 2</var>, <var data-var='time'>20:19</var> UTC Update - 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 <var data-var='date'> 2</var>, <var data-var='time'>05:35</var> UTC Monitoring - AWS has an ongoing issue with multiple services in region me-south-1. Shared server hummingbird-01 affected.

AWS region me-south-1 outage

May <var data-var='date'> 5</var>, <var data-var='time'>06:55</var> UTC Resolved - 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 support@cloudamqp.com if you have any questions. Mar <var data-var='date'> 2</var>, <var data-var='time'>20:19</var> UTC Update - 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 <var data-var='date'> 2</var>, <var data-var='time'>01:46</var> UTC Update - We are continuing to monitor. The outage is in regards to the AZ mec1-az2 Mar <var data-var='date'> 1</var>, <var data-var='time'>13:23</var> UTC Update - We are continuing to monitor for any further issues. Mar <var data-var='date'> 1</var>, <var data-var='time'>13:22</var> UTC Update - We are continuing to monitor for any further issues. Mar <var data-var='date'> 1</var>, <var data-var='time'>13:20</var> UTC Monitoring - AWS has an ongoing issue with multiple services in region me-central-1.

AWS region me-central-1 outage

May <var data-var='date'> 4</var>, <var data-var='time'>01:44</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 3</var>, <var data-var='time'>19:14</var> UTC 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 <var data-var='date'> 3</var>, <var data-var='time'>19:11</var> UTC Investigating - We are currently investigating this issue.

Connecting issues in Azure West Europe

Apr <var data-var='date'>28</var>, <var data-var='time'>11:05</var> UTC Resolved - 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. Apr <var data-var='date'>28</var>, <var data-var='time'>10:53</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>28</var>, <var data-var='time'>10:49</var> UTC Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>28</var>, <var data-var='time'>10:27</var> UTC 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.

Backend slow/unresponsible

Apr <var data-var='date'>24</var>, <var data-var='time'>10:05</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>24</var>, <var data-var='time'>09:36</var> UTC Investigating - We are getting indications of instances being down in Azure region westus. We are investigating the issue.

Connection issues in Azure region westus

Apr <var data-var='date'>23</var>, <var data-var='time'>10:56</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>10:10</var> UTC 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.

Issues with Azure West US 3 region

Apr <var data-var='date'>23</var>, <var data-var='time'>06:00</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>05:25</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>23</var>, <var data-var='time'>03:30</var> UTC 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.

Metrics integration issues

Apr <var data-var='date'>15</var>, <var data-var='time'>14:00</var> UTC Resolved - 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.

Monitoring Systems Short Outage and "Connection issues" Alarms

Apr <var data-var='date'> 6</var>, <var data-var='time'>23:00</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'> 6</var>, <var data-var='time'>21:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>29</var>, <var data-var='time'>23:15</var> UTC Scheduled - We will be undergoing maintenance on some shared servers at this time

Maintenance on shared servers

Apr <var data-var='date'> 2</var>, <var data-var='time'>15:12</var> UTC Resolved - 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. Apr <var data-var='date'> 2</var>, <var data-var='time'>15:07</var> UTC Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'> 2</var>, <var data-var='time'>14:52</var> UTC Update - 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 <var data-var='date'> 2</var>, <var data-var='time'>14:41</var> UTC 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.

Management Interface Unavailable - 502 Bad Gateway Response

Mar <var data-var='date'>25</var>, <var data-var='time'>18:03</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>25</var>, <var data-var='time'>17:45</var> UTC Identified - 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.

Metrics delivery delay for 12% of the fleet

Mar <var data-var='date'>24</var>, <var data-var='time'>10:22</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>24</var>, <var data-var='time'>10:14</var> UTC Verifying - Verification is currently underway for the maintenance items. Mar <var data-var='date'>24</var>, <var data-var='time'>09:44</var> UTC Update - Metrics pipeline maintenance done. Currently doing maintenance on logs system. Mar <var data-var='date'>24</var>, <var data-var='time'>09:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>24</var>, <var data-var='time'>09:17</var> UTC Scheduled - Pipelines for metrics and log integrations are undergoing maintenance, we do not expect any significant delays.

Metrics and log integration maintenance

Mar <var data-var='date'>19</var>, <var data-var='time'>03:50</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>18</var>, <var data-var='time'>22:16</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>18</var>, <var data-var='time'>21:25</var> UTC Identified - 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.

Queue metrics for legacy integrations delayed

Mar <var data-var='date'> 4</var>, <var data-var='time'>14:14</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 4</var>, <var data-var='time'>11:16</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 3</var>, <var data-var='time'>21:11</var> UTC Investigating - We're currently experiencing issues with Coralogix log delivery.

Coralogix log delivery performance issues

Mar <var data-var='date'> 3</var>, <var data-var='time'>20:51</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 3</var>, <var data-var='time'>19:30</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 3</var>, <var data-var='time'>18:47</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'> 3</var>, <var data-var='time'>18:28</var> UTC Investigating - We're currently experiencing issues with metrics delivery, this affects v3 (Prometheus based) metrics.

Metrics delivery outage for v3 Prometheus based metrics.

Feb <var data-var='date'>18</var>, <var data-var='time'>15:30</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>17</var>, <var data-var='time'>21:44</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>17</var>, <var data-var='time'>19:31</var> UTC Investigating - We are currently investigating this issue.

Is CloudAMPQ down?

CloudAMPQ status is UP

Lastest published events

Log server maintenance

Servers Unreacheable - Azure West US

False positive server down messages sent

CloudAMPQ Services, Components and Regions

Recent CloudAMPQ events

Log server maintenance

Servers Unreacheable - Azure West US

False positive server down messages sent

Monitoring Systems — False Alarms

Connectivity issues in Azure West Europe

System metrics not forwarded to legacy integration