CloudAMQP incident

AWS region me-central-1 outage

Major Ongoing View vendor source →
Started
Mar 01, 2026, 01:20 PM UTC
Resolved
Ongoing
Duration
● 63d 13h
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.

Looking to track CloudAMQP downtime and outages?

Pingoru polls CloudAMQP's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when CloudAMQP reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track CloudAMQP alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring CloudAMQP for free

5 free monitors · No credit card required