Issues with AWS services in the ME-CENTRAL-1 Region

Update timeline

1. investigating Mar 01, 2026, 02:23 PM UTC

   AWS is investigating issues with AWS services in the ME-CENTRAL-1 Region. Issue is related to connectivity and power affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Issue started at Mar 01 4:51 AM PST. For more details: https://health.aws.amazon.com/health/status

2. investigating Mar 01, 2026, 02:24 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 01, 2026, 03:05 PM UTC

   Update from AWS: A localized power outage is impacting one Availability Zone (mec1-az2) in the ME-CENTRAL-1 region. As a result, EC2 instances, databases, EBS volumes, and other resources in that zone are unavailable or experiencing connectivity issues. Some AWS services are also seeing increased errors and latency. For more details: https://health.aws.amazon.com/health/status

4. identified Mar 01, 2026, 08:25 PM UTC

   AWS continues to work on restoring services. For more details: https://health.aws.amazon.com/health/status

5. identified Mar 02, 2026, 05:06 PM UTC

   AWS continues to work on restoring services. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status

6. identified Mar 02, 2026, 05:11 PM UTC

   AWS started seeing increased API error rates in ME-SOUTH-1 Region from Mar 01 9:56 PM PST. Current issues are affecting both ME-SOUTH-1 and ME-CENTRAL-1. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status

7. identified Mar 24, 2026, 02:01 AM UTC

   We started noticing issue with services from AWS ME-SOUTH-1 for AZ0 at 13:07:27 UTC. AZ1 had been out of service from Mar 01. While we work with AWS on status, AWS has strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. For more details: https://health.aws.amazon.com/health/status