AWS Outage: me-central

Critical Impact Identified Ongoing March 1, 2026

Incident Lifecycle

Identified Identified Identified Identified Identified Identified

Incident Timeline

Identified
AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.

AWS Status Page: https://health.aws.amazon.com/health/status
Mar 4, 2026 at 4:55 AM UTC
Identified
The outage is still ongoing on AWS side. The AWS Management Console is now operational, and AWS is recommending to retry operations where possible, although most of the underlying service are still offline.
Mar 3, 2026 at 10:21 AM UTC
Identified
ROSA clusters deployed in me-central-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.
Mar 2, 2026 at 5:52 PM UTC
Identified
Availability Zones in the ME-CENTRAL-1 Region (mec1-az2, mec1-az3) have been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.
Mar 2, 2026 at 1:37 PM UTC
Identified
An Availability Zone in the ME-CENTRAL-1 Region (mec1-az2) has been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.
Mar 1, 2026 at 2:26 PM UTC
Identified
ROSA clusters degraded in me-central

AWS Status Page: https://health.aws.amazon.com/health/status
Mar 1, 2026 at 2:02 PM UTC
Was your business affected by this Red Hat 3scale outage?
Set up instant alerts for Red Hat 3scale — be the first to know about outages via email, Slack, Teams, or Discord.