AWS is experiencing a service disruption in me-south-1, me-central-1
Increased Error Rates - 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. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
Real-time per-service status. Live embeds via updog.ai.
Active incidents · 2
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. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
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. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
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 a more targeted communication model. Going forward, 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. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
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, significant work remains before full restoration is complete. We continue to recommend customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. Given the extended nature of this event, we continue to encourage customers to replicate Amazon S3 data and other critical workloads from ME-SOUTH-1 to another AWS Region using the guidance shared previously. We will provide our next update by 12:00 PM PST on March 3, or sooner if conditions change.
Affected: AWS IAM, AWS Lambda, Amazon API Gateway, Amazon CloudFront, Amazon CloudWatch, Amazon DynamoDB, Amazon EC2, Amazon EKS, Amazon ElastiCache, Amazon RDS, Amazon Route 53, Amazon S3, Amazon SNS, Amazon SQS, Amazon VPC · me-south-1 · View the live incident timeline → · Official AWS Health status ↗ · Plan for this: Multi-AZ vs Multi-Region →
Post-mortems
What actually broke, why, and what it means for your architecture - every major AWS incident, explained clearly.
A latent race condition in DynamoDB’s DNS management automation left the regional endpoint with an empty DNS record. Because half of AWS depends on DynamoDB in us-east-1, the failure cascaded into EC2 launches, Lambda, and NLB health checks for ~15 hours.
9 min read
A degradation in the subsystem that manages Lambda’s execution capacity caused elevated invocation error rates in us-east-1 for about three hours. Because Lambda sits inside so many AWS features - including STS and parts of the console - the blast radius reached far beyond “serverless” workloads.
6 min read
An automated scaling activity triggered unexpected behavior in the network connecting AWS’s internal control plane to the main network. The resulting congestion blinded AWS’s own monitoring, broke the consoles and EC2 APIs, and degraded services from SQS to Ring doorbells for about seven hours.
8 min read
A playbook command executed with a mistyped parameter removed far more S3 index capacity than intended in us-east-1. The subsystems needed a full restart - something S3 hadn’t done in years at that scale - and for ~4 hours, a huge share of the web (including AWS’s own status dashboard) broke.
7 min read
Guides
Evergreen resilience playbooks written from real incident patterns.
A step-by-step, game-day-tested DR checklist for AWS: dependency mapping, RTO/RPO targets, strategy selection, backup verification, control-plane drills, and the failover test most teams skip.
10 min read
What Availability Zones actually protect you from, what only a second region can, and a cost/RTO decision framework - grounded in how real AWS outages (2017, 2021, 2025) actually failed.
11 min read
Instant email alerts the moment an AWS incident is detected - with the affected services and regions, not a vague status tweet.
aws