Quay incident

AWS Outage: me-south

Critical Ongoing View vendor source →
Started
Mar 02, 2026, 07:22 AM UTC
Resolved
Ongoing
Duration
● 62d 17h
Detected by Pingoru
Mar 02, 2026, 07:22 AM UTC

Affected components

OpenShift Cluster Manager

Update timeline

  1. identified Mar 02, 2026, 07:22 AM UTC

    ROSA clusters degraded in me-south due to a localized power issue in mes1-az2. Customers are advised to schedule their workloads into another availability zone. AWS Status Page: https://health.aws.amazon.com/health/status

  2. identified Mar 02, 2026, 05:52 PM UTC

    ROSA clusters deployed in me-south-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation.

  3. identified Mar 04, 2026, 04:44 AM UTC

    The outage is still ongoing on the AWS side, and recovery efforts are ongoing. AWS is recommending customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region

Looking to track Quay downtime and outages?

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

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

5 free monitors · No credit card required