AWS

Affected: AWS Amplify, AWS Amplify Admin, AWS App Mesh, AWS AppConfig, AWS AppSync, AWS Application Migration Service, AWS Backup, AWS Batch, AWS Certificate Manager, AWS Client VPN, AWS Cloud Map, AWS Cloud WAN, AWS Cloud9, AWS CloudFormation, AWS CloudHSM, AWS CloudShell, AWS CloudTrail, AWS CodeBuild, AWS CodeCommit, AWS CodeDeploy, AWS CodePipeline, AWS Compute Optimizer, AWS Config, AWS Console Mobile App, AWS Control Tower, AWS DataSync, AWS Database Migration Service, AWS Direct Connect, AWS Directory Service, AWS Elastic Beanstalk, AWS Elastic Disaster Recovery, AWS End User Messaging, AWS Fargate, AWS Fault Injection Service, AWS Firewall Manager, AWS Global Accelerator, AWS Glue, AWS Ground Station, AWS IAM Identity Center, AWS Identity and Access Management Roles Anywhere, AWS Internet Connectivity, AWS IoT Core, AWS IoT Device Defender, AWS IoT Device Management, AWS Key Management Service, AWS Lake Formation, AWS Lambda, AWS Launch Wizard, AWS License Manager, AWS Management Console, AWS NAT Gateway, AWS Network Firewall, AWS Outposts, AWS Private CA Connector for Active Directory, AWS Private CA Connector for SCEP, AWS Private Certificate Authority, AWS Resilience Hub, AWS Resource Access Manager, AWS Resource Explorer, AWS Resource Groups, AWS Resource Groups Tagging API, AWS Secrets Manager, AWS Security Hub, AWS Security Incident Response, AWS Security Token Service, AWS Serverless Application Repository, AWS Service Catalog, AWS Service Quotas, AWS Sign-In, AWS Site-to-Site VPN, AWS Step Functions, AWS Storage Gateway, AWS Systems Manager, AWS Systems Manager for SAP, AWS Transfer Family, AWS Transit Gateway, AWS VPCE PrivateLink, AWS WAF, AWS Well-Architected Tool, AWS X-Ray, Amazon API Gateway, Amazon Athena, Amazon Bedrock, Amazon CloudFront, Amazon CloudWatch, Amazon CloudWatch Application Insights, Amazon CloudWatch Internet Monitor, Amazon CloudWatch RUM, Amazon CloudWatch Synthetics, Amazon Cognito, Amazon Data Firehose, Amazon Data Lifecycle Manager, Amazon Detective, Amazon DynamoDB, Amazon EC2 Instance Connect, Amazon EMR Serverless, Amazon ElastiCache, Amazon Elastic Compute Cloud, Amazon Elastic Container Registry, Amazon Elastic Container Service, Amazon Elastic File System, Amazon Elastic Kubernetes Service, Amazon Elastic Load Balancing, Amazon Elastic MapReduce, Amazon EventBridge, Amazon EventBridge Scheduler, Amazon FSx, Amazon FreeRTOS, Amazon GameLift Streams, Amazon Glacier, Amazon GuardDuty, Amazon Inspector, Amazon Keyspaces, Amazon Kinesis Data Streams, Amazon Kinesis Video Streams, Amazon MQ, Amazon Macie, Amazon Managed Service for Apache Flink, Amazon Managed Streaming for Apache Kafka, Amazon Managed Workflows for Apache Airflow, Amazon Neptune, Amazon OpenSearch Service, Amazon Polly, Amazon Redshift, Amazon Relational Database Service, Amazon Route 53, Amazon Route 53 Private DNS, Amazon Route 53 Resolver, Amazon S3 Replication Time Control, Amazon SageMaker, Amazon Simple Email Service, Amazon Simple Notification Service, Amazon Simple Queue Service, Amazon Simple Storage Service, Amazon Simple Workflow Service, Amazon Transcribe, Amazon VPC IP Address Manager, Amazon VPC Lattice, Amazon Verified Permissions, Amazon Virtual Private Cloud, Auto Scaling, Control Catalog, EC2 Image Builder, EC2 Serial Console, Infrastructure Performance, Network Access Analyzer, Reachability Analyzer, Traffic Mirroring, VM Import/Export

Knock-on incidents at other vendors that started during this one and name AWS:

• CloudAMQP: AWS region me-south-1 outage
• Genesys Cloud: Elevated Error Rates - EMEA (UAE)
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regions
• SingleStore: AWS UAE multiple services disrupted
• Cloudways: AWS Middle East (Bahrain) Outage
• JFrog: JFrog Cloud Platform potential impact due to AWS Datacenter issues in UAE Region
• Lambda: Launches Failing in Multiple Regions
• Palo Alto Networks: AWS Middle East(Bahrain) outage impacting Cloud NGFW Services.

1. 1 2026-03-02 05:56 UTC

   We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.

2. 1 2026-03-02 07:09 UTC

   We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing...

3. 1 2026-03-02 09:03 UTC

   We continue to work on a localized power issue affecting a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. In the impacted Availability Zone, EC2 Instances, DB Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies...

4. 1 2026-03-02 10:41 UTC

   We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. At this time, some AWS services have shifted traffic away from the affected Availability Zone and are seeing recovery for their affected operations and workflows....

5. 1 2026-03-02 14:23 UTC

   We continue to work toward restoring power in the impacted Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. Meanwhile, EC2 instance and networking APIs have been restored for the other Availability Zones. Additionally, we have made improvements to the availability of RDS...

6. 1 2026-03-02 18:52 UTC

   We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We currently expect our recovery efforts to take at least a day. Our current guidance regarding immediate recovery remains unchanged from our previous update....

7. 1 2026-03-02 22:29 UTC

   We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue to advise...

8. 1 2026-03-03 00:22 UTC

   We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts...

9. 1 2026-03-03 06:27 UTC

   We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is...

10. 1 2026-03-03 11:10 UTC

    We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. The overall state of the region remains largely unchanged from our previous update. At this time, we have no updated guidance on expected timelines for fully...

11. 1 2026-03-03 14:02 UTC

    Recovery efforts in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region are ongoing, with the situation remaining consistent with our last update. We have no change to expected timelines for fully restoring power and connectivity. While progress is being made,...

12. 1 2026-03-03 16:40 UTC

    We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to...

13. 3 2026-04-30 07:07 UTC

    We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups....

14. 3 2026-09-15 10:22 UTC

    We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment,...

Excerpts are shortened. Read the full incident on AWS's status page.

Affected: AWS Amplify, AWS AppConfig, AWS AppSync, AWS Application Migration Service, AWS Backup, AWS Batch, AWS Certificate Manager, AWS Client VPN, AWS Cloud Map, AWS Cloud WAN, AWS CloudFormation, AWS CloudHSM, AWS CloudShell, AWS CloudTrail, AWS CodeBuild, AWS CodeCommit, AWS CodeDeploy, AWS CodePipeline, AWS Compute Optimizer, AWS Config, AWS Console Mobile App, AWS Control Tower, AWS DataSync, AWS Database Migration Service, AWS Direct Connect, AWS Directory Service, AWS Elastic Beanstalk, AWS Elastic Disaster Recovery, AWS Elemental, AWS End User Messaging, AWS Fargate, AWS Fault Injection Service, AWS Firewall Manager, AWS Global Accelerator, AWS Glue, AWS IAM Identity Center, AWS Identity and Access Management Roles Anywhere, AWS Internet Connectivity, AWS IoT Core, AWS IoT Device Defender, AWS IoT Device Management, AWS Key Management Service, AWS Lake Formation, AWS Lambda, AWS Launch Wizard, AWS License Manager, AWS Management Console, AWS NAT Gateway, AWS Network Firewall, AWS Outposts, AWS Private CA Connector for Active Directory, AWS Private CA Connector for SCEP, AWS Private Certificate Authority, AWS Resource Access Manager, AWS Resource Explorer, AWS Resource Groups, AWS Resource Groups Tagging API, AWS Secrets Manager, AWS Security Hub, AWS Security Incident Response, AWS Security Token Service, AWS Service Catalog, AWS Service Quotas, AWS Sign-In, AWS Site-to-Site VPN, AWS Step Functions, AWS Storage Gateway, AWS Systems Manager, AWS Systems Manager for SAP, AWS Transfer Family, AWS Transit Gateway, AWS VPCE PrivateLink, AWS Verified Access, AWS WAF, AWS X-Ray, Amazon API Gateway, Amazon Athena, Amazon Bedrock, Amazon CloudFront, Amazon CloudWatch, Amazon CloudWatch Application Insights, Amazon CloudWatch Internet Monitor, Amazon CloudWatch RUM, Amazon CloudWatch Synthetics, Amazon Cognito, Amazon Data Firehose, Amazon Data Lifecycle Manager, Amazon DocumentDB, Amazon DynamoDB, Amazon EC2 Instance Connect, Amazon EMR Serverless, Amazon ElastiCache, Amazon Elastic Compute Cloud, Amazon Elastic Container Registry, Amazon Elastic Container Service, Amazon Elastic File System, Amazon Elastic Kubernetes Service, Amazon Elastic Load Balancing, Amazon Elastic MapReduce, Amazon EventBridge, Amazon EventBridge Scheduler, Amazon FSx, Amazon Glacier, Amazon GuardDuty, Amazon Inspector, Amazon Kinesis Data Streams, Amazon MQ, Amazon Managed Grafana, Amazon Managed Service for Apache Flink, Amazon Managed Service for Prometheus, Amazon Managed Streaming for Apache Kafka, Amazon Managed Workflows for Apache Airflow, Amazon Neptune, Amazon OpenSearch Service, Amazon Quick Suite, Amazon Redshift, Amazon Relational Database Service, Amazon Route 53, Amazon Route 53 Private DNS, Amazon Route 53 Resolver, Amazon S3 Replication Time Control, Amazon SageMaker, Amazon Simple Email Service, Amazon Simple Notification Service, Amazon Simple Queue Service, Amazon Simple Storage Service, Amazon Simple Workflow Service, Amazon VPC IP Address Manager, Amazon VPC Lattice, Amazon Verified Permissions, Amazon Virtual Private Cloud, Amazon WorkSpaces, Auto Scaling, Control Catalog, EC2 Image Builder, EC2 Serial Console, Infrastructure Performance, Reachability Analyzer, Traffic Mirroring, VM Import/Export

Knock-on incidents at other vendors that started during this one and name AWS:

• Wiz: AWS service disruptions affecting the me-central-1 region, effected DC's: prod-me1
• CloudAMQP: AWS region me-central-1 outage
• Snowflake: AWS - Middle East (UAE): INC0152681
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
• Cloudways: AWS Middle East (UAE) Outage
• CockroachDB Cloud: Cluster unavailability and degraded cluster operations in AWS me-central...
• Confluent Cloud: Elevated Error Rates in AWS me-central-1 region
• Asana: AWS UAE issues might affect the ME region
• Wiz: AWS service disruptions affecting the me-central-1 region, affected DCs: prod-me1
• Aiven: Amazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region status
• CloudAMQP: AWS region me-south-1 outage
• Genesys Cloud: Elevated Error Rates - EMEA (UAE)
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regions
• SingleStore: AWS UAE multiple services disrupted
• Cloudways: AWS Middle East (Bahrain) Outage
• JFrog: JFrog Cloud Platform potential impact due to AWS Datacenter issues in UAE Region

1. 1 2026-03-01 12:51 UTC

   We are investigating issues with AWS services in the ME-CENTRAL-1 Region.

2. 1 2026-03-01 13:19 UTC

   We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing...

3. 1 2026-03-01 14:09 UTC

   We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others resources are currently unavailable and will experience connectivity issues at this time. Other AWS...

4. 2 2026-03-01 15:09 UTC

   We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes,...

5. 2 2026-03-01 16:59 UTC

   We continue to work toward restoring power in the affected Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). In parallel, we are actively working on improving error rates and latencies that some customers are observing for EC2 Networking and EC2 Describe APIs. Due to...

6. 3 2026-03-01 17:41 UTC

   We want to provide some additional information on the power issue in a single Availability Zone in the ME-CENTRAL-1 Region. At around 4:30 AM PST, one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire...

7. 3 2026-03-01 20:14 UTC

   We are aware that some customers are experiencing errors when calling EC2 APIs, specifically networking related APIs (AllocateAddress, AssociateAddress, DescribeRouteTable, DescribeNetworkInterfaces). We are actively working on multiple paths to mitigate these issues. For...

8. 3 2026-03-01 22:28 UTC

   We are seeing positive signs of recovery for many of the EC2 APIs, such as Describes and AllocateAddress. We recognize that customers are still experiencing errors when attempting to call the AssociateAddress API, and are unable to disassociate addresses from resources that are...

9. 3 2026-03-02 00:26 UTC

   We are seeing significant signs of recovery for AssociateAddress requests, and continue to work toward fully mitigating this issue. This combined with the earlier recovery of the AllocateAddress API means customers can now successfully create and associate new network addresses...

10. 3 2026-03-02 02:01 UTC

    We confirm the recovery of the AssociateAddress API requests. We have also applied a change that enables customers to disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. With these mitigations, customers can now successfully create...

11. 3 2026-03-02 05:59 UTC

    We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.

12. 3 2026-03-02 06:46 UTC

    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...

13. 3 2026-03-02 08:52 UTC

    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...

14. 3 2026-03-02 10:53 UTC

    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...

15. 3 2026-03-02 14:22 UTC

    We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities,...

16. 3 2026-03-02 17:59 UTC

    We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. The impact is causing elevated errors rates for both the Management Console and CLI. Our current expectation is that recovery will take at least a day...

17. 3 2026-03-02 21:36 UTC

    We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We have partially restored access to the AWS Management Console, however, some pages will continue to load unsuccessfully until we have recovered core...

18. 3 2026-03-03 00:19 UTC

    We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts...

19. 3 2026-03-03 05:13 UTC

    We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region with a focus on restoring functionality to foundational services. Since our last update we have made incremental progress in recovering the DynamoDB...

20. 3 2026-03-03 09:04 UTC

    We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged from our previous update. We continue to work closely with local authorities and are prioritizing...

21. 3 2026-03-03 12:58 UTC

    We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged, though our teams continue to make progress on recovery efforts across multiple workstreams. For...

22. 3 2026-03-03 16:14 UTC

    We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability....

23. 3 2026-04-30 07:25 UTC

    We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to...

24. 3 2026-09-15 10:27 UTC

    We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to...

Excerpts are shortened. Read the full incident on AWS's status page.