Outage in AWS

Increased Connectivity Issues and API Error Rates - Bahrain

Minor

March 02, 2026 - Started about 8 hours ago

Incident Report

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

Components affected

Amazon CloudFront Amazon CloudWatch Amazon CloudWatch (me-south-1) Amazon Cognito Amazon Cognito (me-south-1) Amazon EC2 Amazon EC2 (me-south-1) Amazon ECR Amazon ECR (me-south-1) Amazon ECS Amazon ECS (me-south-1) Amazon Elastic File System Amazon Elastic File System (me-south-1) Amazon EKS Amazon EKS (me-south-1) Amazon ELB Amazon ELB (me-south-1) Amazon EMR Amazon EMR (me-south-1) Amazon ElastiCache Amazon ElastiCache (me-south-1) Amazon EventBridge Amazon EventBridge (me-south-1) Amazon FSx Amazon FSx (me-south-1) Amazon Inspector Amazon Kinesis Data Streams Amazon Kinesis Data Streams (me-south-1) Amazon Kinesis Firehose Amazon Kinesis Firehose (me-south-1) Amazon Managed Streaming for Apache Kafka Amazon Managed Streaming for Apache Kafka (me-south-1) Amazon MQ Amazon MQ (me-south-1) Amazon OpenSearch Service Amazon OpenSearch Service (me-south-1) Amazon Redshift Amazon Redshift (me-south-1) Amazon RDS Amazon RDS (me-south-1) Amazon Route 53 Amazon SageMaker Amazon SageMaker (me-south-1) Amazon SNS Amazon SNS (me-south-1) Amazon SWF Amazon SWF (me-south-1) Amazon Transcribe Amazon Transcribe (me-south-1) Auto Scaling Auto Scaling (me-south-1) AWS AppSync AWS AppSync (me-south-1) AWS Cloud9 AWS Cloud9 (me-south-1) AWS CloudFormation AWS CloudFormation (me-south-1) AWS CloudHSM AWS CloudHSM (me-south-1) AWS CloudShell AWS CloudTrail AWS CloudTrail (me-south-1) AWS CodeBuild AWS CodeBuild (me-south-1) AWS CodeDeploy AWS CodeDeploy (me-south-1) AWS CodePipeline AWS Control Tower AWS Database Migration Service AWS Database Migration Service (me-south-1) AWS DataSync AWS DataSync (me-south-1) AWS Directory Service AWS Directory Service (me-south-1) AWS EB AWS EB (me-south-1) AWS Elastic Disaster Recovery AWS Elastic Disaster Recovery (me-south-1) AWS Global Accelerator AWS Glue AWS Glue (me-south-1) AWS IoT Core AWS IoT Core (me-south-1) AWS IoT Device Defender AWS IoT Device Defender (me-south-1) AWS IoT Device Management AWS KMS AWS KMS (me-south-1) AWS Lake Formation AWS Lake Formation (me-south-1) AWS Lambda AWS Lambda (me-south-1) AWS NAT Gateway AWS NAT Gateway (me-south-1) AWS Network Firewall AWS Network Firewall (me-south-1) AWS Resource Groups Tagging API AWS Resource Groups Tagging API (me-south-1) AWS Service Catalog AWS Service Catalog (me-south-1) AWS Site-to-Site VPN AWS Site-to-Site VPN (me-south-1) AWS Step Functions AWS Step Functions (me-south-1) AWS Storage Gateway AWS Storage Gateway (me-south-1) AWS Transit Gateway AWS Transit Gateway (me-south-1) AWS VPCE PrivateLink AWS VPCE PrivateLink (me-south-1) Multiple services Multiple services (me-south-1) AWS Cloud WAN AWS Resource Explorer AWS Resource Explorer (me-south-1) AWS CloudShell (me-south-1) AWS CodePipeline (me-south-1) AWS Control Tower (me-south-1) Amazon EMR Serverless Amazon EMR Serverless (me-south-1) Amazon EventBridge Scheduler Amazon EventBridge Scheduler (me-south-1) AWS Fargate AWS Fargate (me-south-1) AWS IAM Identity Center AWS IAM Identity Center (me-south-1) Amazon Inspector (me-south-1) AWS IoT Device Management (me-south-1)

Need to monitor AWS outages?

Monitor all your external dependencies in one place
Get instant alerts when outages are detected
Be the first to know if service is down
Show real-time status on private or public status page
Keep your team informed

Start monitoring for free

Latest Updates ( sorted recent to last )

UPDATE about 3 hours ago - at 03/02/2026 10:41AM

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. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline. Power has not yet been restored to the affected Availability Zone. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate Region. In parallel, we are actively working on reducing the error rates and latencies that some customers are experiencing with EC2 APIs. For now, we recommend continuing to retry any failed API requests. We will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.

UPDATE about 4 hours ago - at 03/02/2026 09:03AM

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 for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the ME-SOUTH-1 Region, as existing instances in other AZs remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin recovering affected resources. Currently, we expect recovery to take many hours. We will provide an update by 2:30 AM PST, or sooner if we have additional information to share.

UPDATE about 6 hours ago - at 03/02/2026 07:09AM

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 increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. During this time, we are also experiencing delays in propagating DNS changes for Route53 to pops (Points of Presence) in ME-SOUTH-1. Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.

UPDATE about 8 hours ago - at 03/02/2026 05:56AM

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

Latest AWS outages

Increased Error Rates - UAE - 1 day ago

Intermittent missing or delayed EC2 instance and status check metrics - N. Virginia - 5 days ago

AWS Direct Connect Connectivity Issues - N. Virginia - 10 days ago

AWS Direct Connect connectivity loss - N. Virginia - 10 days ago

Change Propagation Delays - 20 days ago

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6020 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook