Update - AWS is expecting to address the issue in another day as per their communication at Mar 02 6:22 AM PST
Mar 02, 2026 - 06:26 PST
Mar 02, 2026 - 06:26 PST
Update - Mar 02 2:53 AM PST We wanted to provide more information on Amazon S3 given that there are two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. Amazon S3 is a regional service and designed to withstand the total loss of a single Availability Zone while maintaining S3's durability and availability. When the mec1-az2 AZ was powered off at approximately 4:00 AM PST on Sunday, March 1, S3 continued to operate normally. As the second AZ became impaired, S3 error rates increased. With two Availability Zones significantly impacted, customers are seeing high failure rates for data ingest and egress. We strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. As soon as practically possible, we will begin the restoration of our two Availability Zones which will include a careful assessment of data health and any repair of storage if necessary.
In addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.
Mar 02 12:52 AM PST We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.
Mar 02, 2026 - 03:23 PST
In addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.
Mar 02 12:52 AM PST We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.
Mar 02, 2026 - 03:23 PST
Update - We are following with the current situation with ME-Central-1. The last few updates from AWS are as below -
https://health.aws.amazon.com/health/status?path=open-issues
Increased Error Rates
Mar 01 10:46 PM PST We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share.
Mar 01 9:59 PM PST We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.
Mar 01, 2026 - 23:45 PST
https://health.aws.amazon.com/health/status?path=open-issues
Increased Error Rates
Mar 01 10:46 PM PST We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share.
Mar 01 9:59 PM PST We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.
Mar 01, 2026 - 23:45 PST
Investigating - We are currently investigating this issue.
Mar 01, 2026 - 23:40 PST
Mar 01, 2026 - 23:40 PST
Cloud Portal
Operational
Cloud Portal Front End
Operational
Cloud Portal ZTP
Operational
Orchestrator As a Service
Partial Outage
Orchestrator As a Service(Northern Virginia)
Operational
Orchestrator As a Service(Frankfurt)
Operational
Orchestrator As a Service(Ohio)
Operational
Orchestrator As a Service(Mumbai)
Operational
Orchestrator As a Service(Sydney)
Operational
Orchestrator As a Service(UAE)
Partial Outage
Orchestrator Service Provider
Operational
Orchestrator Service Provider(Northern Virginia)
Operational
Orchestrator Service Provider(Frankfurt)
Operational
Orchestrator Service Provider(Ohio)
Operational
Orchestrator Service Provider(Mumbai)
Operational
Orchestrator Service Provider(Sydney)
Operational
Orchestrator Service Provider(UAE)
Operational
Orchestrator Global Enterprise
Operational
Orchestrator Global Enterprise(Northern Virginia)
Operational
Orchestrator Global Enterprise(Frankfurt)
Operational
Orchestrator Global Enterprise(Ohio)
Operational
Orchestrator Global Enterprise(Mumbai)
Operational
Orchestrator Global Enterprise(Sydney)
Operational
Orchestrator Global Enterprise(UAE)
Operational
IPSLA
Operational
SP IPSLA
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.