# AWS: Region Availability (Bahrain)

> AWS services do not work in the Middle East (Bahrain) me-south-1 Region. The affected components include Amazon Simple Storage Service, Amazon API Gateway, AWS WAF, and AWS Internet Connectivity. AWS reports that the damage exceeded the design limits of its regional and multi-AZ services. AWS states that it cannot restore access to resources and data hosted only in this Region.

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

## Updates from AWS

### active, 2026-10-31 21:45 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, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the disruption of a second Availability Zone in April. Since then, we have supported the remaining customers in re-establishing their operations in alternate Regions, using backups where available or implementing alternative solutions to mitigate the impact of inaccessible data. In parallel, we assessed all affected infrastructure and exhausted every option for restoring data and resources that had not