Alkira Status · History · Incident #28042
ACTIVE INCIDENTIssues with AWS services in the ME-CENTRAL-1 Region
Major · Started Mar 1, 2026 · 2:23 PM
Alkira Status · History · Incident #28042
ACTIVE INCIDENTMajor · Started Mar 1, 2026 · 2:23 PM
Duration
Ongoing
Severity
Major
Detection lead
—
User reports
—
Summary
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
Investigating
Mar 1 · 2:23 PM AlkiraAWS 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 AlkiraWe are continuing to investigate this issue.
Identified
Mar 1 · 3:05 PM AlkiraUpdate 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 AlkiraAWS continues to work on restoring services. For more details: https://health.aws.amazon.com/health/status
Identified
Mar 2 · 5:06 PM AlkiraAWS 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 AlkiraAWS 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 AlkiraWe 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
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.