CloudAMQP Outage History

CloudAMQP is up right now

CloudAMQP had 36 outages in the last 2 years totaling 3174h 44m of downtime — averaging 1.5 incidents per month.

There were 36 CloudAMQP outages since June 9, 2025 totaling 3174h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloudamqp.com

Minor May 23, 2026

Connectivity issues in Azure West Europe

Detected by Pingoru
May 23, 2026, 04:21 PM UTC
Resolved
May 23, 2026, 05:23 PM UTC
Duration
1h 1m
Affected: Microsoft Azure
Timeline · 2 updates
  1. investigating May 23, 2026, 04:21 PM 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, 23 May 2026). Microsoft is investigating.

  2. resolved May 23, 2026, 05:23 PM 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. The Azure environment self-healed and the service has been confirmed restored. Affected CloudAMQP instances should now be operating normally.

Read the full incident report →

Minor May 19, 2026

Backend slow

Detected by Pingoru
May 19, 2026, 01:21 PM UTC
Resolved
May 19, 2026, 01:50 PM UTC
Duration
28m
Affected: Backend
Timeline · 4 updates
  1. 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.

  2. identified May 19, 2026, 01:36 PM UTC

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

  3. monitoring May 19, 2026, 01:41 PM UTC

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

  4. resolved May 19, 2026, 01:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 3, 2026

Connecting issues in Azure West Europe

Detected by Pingoru
May 03, 2026, 07:11 PM UTC
Resolved
May 04, 2026, 01:44 AM UTC
Duration
6h 33m
Affected: Microsoft Azure
Timeline · 3 updates
  1. investigating May 03, 2026, 07:11 PM UTC

    We are currently investigating this issue.

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

  3. resolved May 04, 2026, 01:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 28, 2026

Backend slow/unresponsible

Detected by Pingoru
Apr 28, 2026, 10:27 AM UTC
Resolved
Apr 28, 2026, 11:05 AM UTC
Duration
37m
Affected: Backend
Timeline · 4 updates
  1. 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.

  2. identified Apr 28, 2026, 10:49 AM UTC

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

  3. monitoring Apr 28, 2026, 10:53 AM UTC

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

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

Read the full incident report →

Major April 24, 2026

Connection issues in Azure region westus

Detected by Pingoru
Apr 24, 2026, 09:36 AM UTC
Resolved
Apr 24, 2026, 10:05 AM UTC
Duration
28m
Affected: Microsoft Azure
Timeline · 2 updates
  1. 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.

  2. resolved Apr 24, 2026, 11:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

Issues with Azure West US 3 region

Detected by Pingoru
Apr 23, 2026, 10:10 AM UTC
Resolved
Apr 23, 2026, 10:56 AM UTC
Duration
45m
Affected: Microsoft Azure
Timeline · 2 updates
  1. 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.

  2. resolved Apr 23, 2026, 10:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026

Monitoring Systems Short Outage and "Connection issues" Alarms

Detected by Pingoru
Apr 15, 2026, 03:32 PM UTC
Resolved
Apr 15, 2026, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor April 2, 2026

Management Interface Unavailable - 502 Bad Gateway Response

Detected by Pingoru
Apr 02, 2026, 02:41 PM UTC
Resolved
Apr 02, 2026, 03:12 PM UTC
Duration
31m
Affected: Shared serversDedicated servers
Timeline · 4 updates
  1. 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.

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

  3. identified Apr 02, 2026, 03:07 PM UTC

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

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

Read the full incident report →

Notice March 25, 2026

Metrics delivery delay for 12% of the fleet

Detected by Pingoru
Mar 25, 2026, 05:45 PM UTC
Resolved
Mar 25, 2026, 06:03 PM UTC
Duration
17m
Affected: Metrics
Timeline · 2 updates
  1. 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.

  2. resolved Mar 25, 2026, 06:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Queue metrics for legacy integrations delayed

Detected by Pingoru
Mar 18, 2026, 09:25 PM UTC
Resolved
Mar 19, 2026, 03:50 AM UTC
Duration
6h 24m
Affected: Metrics
Timeline · 3 updates
  1. 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.

  2. monitoring Mar 18, 2026, 10:16 PM UTC

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

  3. resolved Mar 19, 2026, 03:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026

Coralogix log delivery performance issues

Detected by Pingoru
Mar 03, 2026, 09:11 PM UTC
Resolved
Mar 04, 2026, 02:14 PM UTC
Duration
17h 3m
Timeline · 3 updates
  1. investigating Mar 03, 2026, 09:11 PM UTC

    We're currently experiencing issues with Coralogix log delivery.

  2. monitoring Mar 04, 2026, 11:16 AM UTC

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

  3. resolved Mar 04, 2026, 02:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026

Metrics delivery outage for v3 Prometheus based metrics.

Detected by Pingoru
Mar 03, 2026, 06:28 PM UTC
Resolved
Mar 03, 2026, 08:51 PM UTC
Duration
2h 23m
Affected: Metrics
Timeline · 5 updates
  1. investigating Mar 03, 2026, 06:28 PM UTC

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

  2. identified Mar 03, 2026, 06:47 PM UTC

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

  3. monitoring Mar 03, 2026, 07:30 PM UTC

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

  4. resolved Mar 03, 2026, 08:51 PM UTC

    This incident has been resolved.

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

Read the full incident report →

Notice March 2, 2026

AWS region me-south-1 outage

Detected by Pingoru
Mar 02, 2026, 05:35 AM UTC
Resolved
May 05, 2026, 06:55 AM UTC
Duration
64d 1h
Affected: Shared serversDedicated servers
Timeline · 3 updates
  1. 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.

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

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

Read the full incident report →

Notice March 1, 2026

AWS region me-central-1 outage

Detected by Pingoru
Mar 01, 2026, 01:20 PM UTC
Resolved
May 05, 2026, 06:55 AM UTC
Duration
64d 17h
Affected: Dedicated servers
Timeline · 6 updates
  1. monitoring Mar 01, 2026, 01:20 PM UTC

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

  2. monitoring Mar 01, 2026, 01:22 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Mar 01, 2026, 01:23 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Mar 02, 2026, 01:46 AM UTC

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

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

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

Read the full incident report →

Notice February 17, 2026

Issues with shared server "chameleon"

Detected by Pingoru
Feb 17, 2026, 07:31 PM UTC
Resolved
Feb 18, 2026, 03:30 PM UTC
Duration
19h 59m
Timeline · 3 updates
  1. investigating Feb 17, 2026, 07:31 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 17, 2026, 09:44 PM UTC

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

  3. resolved Feb 18, 2026, 03:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 3, 2026

Azure outage

Detected by Pingoru
Feb 03, 2026, 02:53 AM UTC
Resolved
Feb 03, 2026, 08:17 AM UTC
Duration
5h 23m
Affected: Microsoft Azure
Timeline · 2 updates
  1. monitoring Feb 03, 2026, 02:53 AM UTC

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

  2. resolved Feb 03, 2026, 08:17 AM UTC

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

Read the full incident report →

Notice January 14, 2026

Datadog metrics issue

Detected by Pingoru
Jan 14, 2026, 03:54 PM UTC
Resolved
Jan 14, 2026, 04:58 PM UTC
Duration
1h 4m
Affected: Metrics
Timeline · 4 updates
  1. investigating Jan 14, 2026, 03:54 PM UTC

    We are currently investigating this issue

  2. identified Jan 14, 2026, 03:55 PM UTC

    The issue has been identified and a fix is being implemented

  3. monitoring Jan 14, 2026, 03:56 PM UTC

    We are monitoring now.

  4. resolved Jan 14, 2026, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 11, 2025

Email Delays

Detected by Pingoru
Dec 11, 2025, 12:16 PM UTC
Resolved
Dec 11, 2025, 01:12 PM UTC
Duration
55m
Affected: Help Scout Email Processing
Timeline · 2 updates
  1. investigating Dec 11, 2025, 12:16 PM UTC

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

  2. resolved Dec 11, 2025, 01:12 PM UTC

    This incident has been resolved by third party.

Read the full incident report →

Notice December 10, 2025

Connectivity issues with Azure westeurope

Detected by Pingoru
Dec 10, 2025, 10:13 AM UTC
Resolved
Dec 10, 2025, 01:13 PM UTC
Duration
2h 59m
Affected: Microsoft Azure
Timeline · 2 updates
  1. investigating Dec 10, 2025, 10:13 AM 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 Dec 10, 2025, 01:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 19, 2025

Alarms/webhook notification issue

Detected by Pingoru
Nov 19, 2025, 03:07 PM UTC
Resolved
Nov 19, 2025, 04:03 PM UTC
Duration
55m
Timeline · 4 updates
  1. investigating Nov 19, 2025, 03:07 PM UTC

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

  2. identified Nov 19, 2025, 03:19 PM UTC

    The issue has been identified and a fix is being implemented

  3. identified Nov 19, 2025, 03:49 PM UTC

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

  4. resolved Nov 19, 2025, 04:03 PM UTC

    This incident has been resolved

Read the full incident report →

Notice November 17, 2025

Metrics not showing

Detected by Pingoru
Nov 17, 2025, 10:52 PM UTC
Resolved
Nov 18, 2025, 02:03 AM UTC
Duration
3h 11m
Affected: Metrics
Timeline · 3 updates
  1. identified Nov 17, 2025, 10:52 PM UTC

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

  2. monitoring Nov 17, 2025, 10:57 PM UTC

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

  3. resolved Nov 18, 2025, 02:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 5, 2025

Azure westeurope Availability Zone: 2

Detected by Pingoru
Nov 05, 2025, 05:47 PM UTC
Resolved
Nov 06, 2025, 01:50 AM UTC
Duration
8h 3m
Affected: Dedicated serversMicrosoft Azure
Timeline · 4 updates
  1. identified Nov 05, 2025, 05:47 PM UTC

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

  2. identified Nov 05, 2025, 06:50 PM UTC

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

  3. monitoring Nov 05, 2025, 07:21 PM 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 restore normal cooling and service operations. The next update will be provided within 60 minutes, or as events warrant. AZ 1 and 2are impacted.

  4. resolved Nov 06, 2025, 01:50 AM UTC

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

Read the full incident report →