Alkira Status · History · Incident #28042

ACTIVE INCIDENT

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

Major · Started Mar 1, 2026 · 2:23 PM

  • Duration

    Ongoing

  • Severity

    Major

  • Detection lead

  • User reports

Summary

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

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


  • Started

    Mar 1, 2026 · 2:23 PM

  • Status

    Identified

  • Duration

    Ongoing

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Mar 1 · 2:23 PM Alkira

    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

  • Investigating

    Mar 1 · 2:24 PM Alkira

    We are continuing to investigate this issue.

  • Identified

    Mar 1 · 3:05 PM Alkira

    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

  • Identified

    Mar 1 · 8:25 PM Alkira

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

  • Identified

    Mar 2 · 5:06 PM Alkira

    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

  • Identified

    Mar 2 · 5:11 PM Alkira

    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

  • Identified

    Mar 24 · 2:01 AM Alkira

    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

Get alerted before the next Alkira outage.

Pulsetic catches degradations minutes before vendors acknowledge them.