CloudAMQP incident

AWS region me-central-1 outage

Notice Resolved View vendor source →

CloudAMQP experienced a notice incident on March 1, 2026 affecting Dedicated servers, lasting 64d 17h. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2026, 01:20 PM UTC
Resolved
May 05, 2026, 06:55 AM UTC
Duration
64d 17h
Detected by Pingoru
Mar 01, 2026, 01:20 PM UTC

Affected components

Dedicated servers

Update timeline

  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.