CloudAMQP

Affected: Microsoft Azure

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-21 16:39 UTC

   We're investigating connectivity issues affecting some servers in Azure West Europe. We'll post an update as soon as we know more.

2. resolved 2026-10-21 17:13 UTC

   Connectivity to servers in southeast Asia has been restored.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers, Google Cloud Platform Google Compute Engine

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 07:21 UTC

   We're investigating connectivity issues affecting some servers in Google europe-west2. We'll post an update as soon as we know more.

2. investigating 2026-10-20 07:22 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-20 07:29 UTC

   Incident is limited to servers in europe-west2-b

4. monitoring 2026-10-20 09:00 UTC

   GCE is still reporting issues, but we are seeing some API calls succeed.

5. monitoring 2026-10-20 12:13 UTC

   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.

6. monitoring 2026-10-20 12:33 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-10-20 13:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-09 13:28 UTC

   We're investigating connectivity issues affecting some servers in Azure West Europe. We'll post an update as soon as we know more.

2. investigating 2026-10-09 14:39 UTC

   Azure is aware of this issue and are actively investigating. We'll post another update as soon as we know more.

3. identified 2026-10-09 15:08 UTC

   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...

4. monitoring 2026-10-09 17:07 UTC

   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.

5. resolved 2026-10-09 19:27 UTC

   All CloudAMQP instances are up and running in Azure West Europe.

6. postmortem 2026-10-12 14:51 UTC

   **Summary** CloudAMQP lost connectivity with a subset of clusters in Azure west Europe availability zone 2 on October 9th. Single node clusters in AZ2 were most impacted by the incident. ‌ **Impact** Customers were unable to access data or mange nodes impacted during the...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-10-06 14:37 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...

2. monitoring 2026-10-06 15:44 UTC

   Routing is back to normal.

3. resolved 2026-10-06 15:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 13:27 UTC

   We are currently investigating this issue.

2. identified 2026-08-26 13:28 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-26 13:41 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-26 13:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: DigitalOcean AMS2, DigitalOcean AMS3, DigitalOcean FRA1, DigitalOcean LON1, DigitalOcean NYC2, DigitalOcean NYC3, DigitalOcean SFO1, DigitalOcean SGP1, DigitalOcean TOR1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-24 23:52 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

2. resolved 2026-08-25 23:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers, Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network connectivity – Issues accessing resources in West US.

1. investigating 2026-07-23 15:33 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.

2. monitoring 2026-07-23 19:50 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.

3. resolved 2026-07-23 21:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers, Backend

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-25 14:10 UTC

   We are currently investigating this issue.

2. identified 2026-06-25 14:21 UTC

   The issue has been identified and a fix is being implemented.

3. investigating 2026-06-26 08:38 UTC

   We are currently investigating this issue.

4. identified 2026-06-26 09:17 UTC

   The issue has been identified and a fix is being implemented.

5. monitoring 2026-06-26 14:22 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-06-26 14:44 UTC

   This incident has been resolved.

7. postmortem 2026-06-29 11:22 UTC

   **Summary** Between June 25 and June 26, our monitoring system incorrectly reported some dedicated servers as unreachable and sent "server down" notifications for servers that were in fact operating normally. This was a monitoring-side issue only — no customer servers or...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-30 22:25 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...

2. resolved 2026-05-31 11:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-23 16:21 UTC

   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,...

2. resolved 2026-05-23 17:23 UTC

   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....

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-22 03:16 UTC

   Since around 8pm UTC last night, some metrics are not being forwarded to legacy integration. Prometheus integrations not affected. We are investingating.

2. monitoring 2026-05-22 04:08 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-22 04:50 UTC

   This incident has been resolved.

4. postmortem 2026-05-22 13:52 UTC

   # Legacy host metrics integrations degraded Incident window: 2026-05-21 18:37 UTC – 2026-05-22 04:05 UTC \(9h 28m\) Affected service: Legacy metric integrations \(CloudWatch, Datadog, Librato, New Relic, Splunk, Stackdriver\). Host metrics affected, not broker metrics, nor was...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 13:21 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.

2. identified 2026-05-19 13:36 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-19 13:41 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-19 13:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 10:23 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.

2. monitoring 2026-05-05 10:41 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-05-05 11:23 UTC

   Still seeing slow requests, doing another investigation.

4. monitoring 2026-05-05 11:34 UTC

   Looks like we're back at full performance now.

5. resolved 2026-05-05 13:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-03 19:11 UTC

   We are currently investigating this issue.

2. identified 2026-05-03 19:14 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...

3. resolved 2026-05-04 01:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Backend

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 10:27 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.

2. identified 2026-04-28 10:49 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-28 10:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-28 11:05 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.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-04-24 09:36 UTC

   We are getting indications of instances being down in Azure region westus. We are investigating the issue.

2. resolved 2026-04-24 10:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-04-23 10:10 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.

2. resolved 2026-04-23 10:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-23 03:30 UTC

   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.

2. monitoring 2026-04-23 05:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-23 06:00 UTC

   This incident has been resolved.

4. postmortem 2026-04-24 08:38 UTC

   Broker metrics and metrics integrations degradation Window: 2026-04-23 03:25 – 05:35 UTC \(2h 10m\) ## Impact Broker metrics \(connections, channels, queues, consumers, message rates, node and netsplit state\) were degraded, progressively dropping until recovery at 05:35 UTC....

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-15 14:00 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...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers, Dedicated servers

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-04-02 14:41 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.

2. identified 2026-04-02 14:52 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.

3. identified 2026-04-02 15:07 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2026-04-02 15:12 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...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-25 17:45 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.

2. resolved 2026-03-25 18:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-18 21:25 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.

2. monitoring 2026-03-18 22:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-19 03:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-03 21:11 UTC

   We're currently experiencing issues with Coralogix log delivery.

2. monitoring 2026-03-04 11:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-04 14:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-03 18:28 UTC

   We're currently experiencing issues with metrics delivery, this affects v3 (Prometheus based) metrics.

2. identified 2026-03-03 18:47 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-03-03 19:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-03-03 20:51 UTC

   This incident has been resolved.

5. postmortem 2026-03-04 14:14 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...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers, Dedicated servers

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

1. monitoring 2026-03-02 05:35 UTC

   AWS has an ongoing issue with multiple services in region me-south-1. Shared server hummingbird-01 affected.

2. monitoring 2026-03-02 20:19 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,...

3. resolved 2026-05-05 06:55 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 support@cloudamqp.com if you have any questions.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. monitoring 2026-03-01 13:20 UTC

   AWS has an ongoing issue with multiple services in region me-central-1.

2. monitoring 2026-03-01 13:22 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2026-03-01 13:23 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-03-02 01:46 UTC

   We are continuing to monitor. The outage is in regards to the AZ mec1-az2

5. monitoring 2026-03-02 20:19 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...

6. resolved 2026-05-05 06:55 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 support@cloudamqp.com if you have any questions.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-17 19:31 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-17 21:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-18 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 14:47 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-03 15:11 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-03 15:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. monitoring 2026-02-03 02:53 UTC

   A known Azure outage is leading to an error that prevents instances being created for now.

2. resolved 2026-02-03 08:17 UTC

   This incident has been resolved by Azure, https://azure.status.microsoft/en-us/status

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-14 15:54 UTC

   We are currently investigating this issue

2. identified 2026-01-14 15:55 UTC

   The issue has been identified and a fix is being implemented

3. monitoring 2026-01-14 15:56 UTC

   We are monitoring now.

4. resolved 2026-01-14 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Help Scout Email Processing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-11 12:16 UTC

   emails and replies are delayed due to Helscout connection issues https://status.helpscout.com/incidents/kmd031b5fm16,

2. resolved 2025-12-11 13:12 UTC

   This incident has been resolved by third party.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-12-10 10:13 UTC

   Servers in west Europe can experience connection issues due to Virtual Machines issues at the provider. We will monitor and update when we know more.

2. resolved 2025-12-10 13:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-19 15:07 UTC

   We're currently experiencing issues with alarms notification/webhooks function.

2. identified 2025-11-19 15:19 UTC

   The issue has been identified and a fix is being implemented

3. identified 2025-11-19 15:49 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2025-11-19 16:03 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-17 22:52 UTC

   Metrics are currently not showing for dedicated servers, this is related to an outage of one of our suppliers.

2. monitoring 2025-11-17 22:57 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-18 02:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers, Microsoft Azure

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Thermal event impacting multiple services in AZ01 – West Europe.

1. identified 2025-11-05 17:47 UTC

   Access to Azure west Europe Availability zone 2 has been interrupted. Monitoring Azure and their report on the issue.

2. identified 2025-11-05 18:50 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2025-11-05 19:21 UTC

   Update from Azure - Current Status: We detected this issue via our automated service monitoring, which identified a spike in hardware temperatures and service incidents affecting multiple clusters. We are actively investigating the cause and working with on-site technicians to...

4. resolved 2025-11-06 01:50 UTC

   We have observed that impacted clusters has restored services, and are working to ensure everything is back to normal.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-30 03:31 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2025-10-30 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-29 17:24 UTC

   We've identified an issue in creating new clusters, when those clusters are using "copy-config" to get definitions from another cluster. Regular cluster creation still works fine.

2. resolved 2025-10-29 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-24 02:21 UTC

   We are currently investigating. Creating shared accounts work, but not dedicated. Don't trigger upgrades or plan changes if it can be avoided.

2. resolved 2025-10-24 05:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Help Scout Email Processing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-20 17:14 UTC

   Our service provider for support system is partially down. We can still reach many parts of the system and critical incidents still trigger incident response. If you have issues getting to CloudAMQP support you can use our backup email address support-group@84codes.com

2. monitoring 2025-10-20 19:32 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-20 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-13 17:01 UTC

   We're investigating issues with delayed or missing metrics

2. monitoring 2025-10-13 17:51 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-13 20:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-13 16:44 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2025-10-13 16:56 UTC

   We've found the issues and accounts are now being processed as they should.

3. resolved 2025-10-13 17:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network Connectivity – Multiple services impacted in Switzerland North.

1. identified 2025-09-27 01:02 UTC

   Servers in Switzerland North can experience issues due to Storage issues at the provider. We will monitor and update when we know more.

2. resolved 2025-09-27 05:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Metrics

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-09-15 13:41 UTC

   Between 11:00 and 13:00 UTC we had an issue with our metrics delivery pipeline so some customers might have gotten an reduced amount of metrics, in some cases even none, while some might have seen a spike om metrics being delivered to their integration. The version that caused...

2. resolved 2025-09-15 17:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-07-23 07:30 UTC

   Around 07:30 UTC we deployed a fix that cleaned up leaking message files to a batch of impacted clusters, where around 100 clusters had some message files removed. Most clusters recovered within seconds where RabbitMQ self-healed, but some clusters experienced more severe...

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-24 09:26 UTC

   We are currently investigating this issue

2. identified 2025-06-24 09:42 UTC

   The issue has been identified.

3. resolved 2025-06-24 09:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Backend, Heroku

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-10 16:29 UTC

   We are currently experiencing issues with our backend services handling account and server creation, and metrics collection. This does not affect any running customer servers. This is due to ongoing Heroku service disruption (affecting Heroku's dyno connectivity, Dashboard, and...

2. investigating 2025-06-10 20:39 UTC

   https://status.heroku.com/incidents/2822

3. monitoring 2025-06-10 23:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-06-10 23:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-10 06:42 UTC

   Logs shipped to Datadog are currently delayed.

2. resolved 2025-06-10 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Dedicated servers, Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2025-06-09 15:20 UTC

   Servers in west Europe can experience connection issues due to Virtual Machines issues at the provider. We will monitor and update when we know more.

2. monitoring 2025-06-09 15:52 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-09 16:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Shared servers

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-08 22:01 UTC

   The shared server horse.lmq.cloudamqp.com is not able to start. We are investigating why it is unable to do so.

2. resolved 2025-04-09 01:28 UTC

   We identified the cause of the crash and found a solution to prevent further crashes. The cluster is now online.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Microsoft Azure

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-04-01 09:23 UTC

   Servers in North Europe can experience connection issues due to Virtual Machines issues at the provider. We will monitor and update when we know more.

2. resolved 2025-04-01 14:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.

Affected: Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-23 18:27 UTC

   We are currently investigating this issue.

2. identified 2025-02-23 20:46 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-02-23 20:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CloudAMQP's status page.