AWS down and when will it be back up? AWS outage, affected regions, services, error messages, recovery efforts, desktop and mobile users issues explained

AWS down and when will it be back up? Amazon Web Services (AWS) experienced a major outage in its Middle East (UAE) region after unidentified objects struck one of its data centers, causing sparks and a fire. The incident affected the mec1-az2 availability zone, leading emergency crews to shut off power while containing the fire. Other availability zones in the UAE continued to operate, but customers reported errors and service delays. AWS immediately began rerouting traffic and advised users to use alternate zones or regions. The outage disrupted multiple services including EC2, S3, and DynamoDB, highlighting the importance of redundancy and regional recovery planning.

AWS Down and When Will It Be Back Up?

AWS is currently down in its UAE region after a fire at the mec1-az2 availability zone caused by unidentified objects. The outage disrupted multiple services, including EC2, S3, and DynamoDB, affecting customer operations across the Gulf. AWS has begun rerouting traffic to unaffected zones, but full recovery will take several hours as engineers restore power, connectivity, and assess data health. Customers are advised to use alternate availability zones or other AWS regions where possible. AWS updates indicate that restoration efforts may extend into the next day, depending on facility repairs and safety checks.

AWS Down?

AWS is down in the UAE region after a fire at the mec1-az2 availability zone caused by unidentified objects. The outage disrupted multiple services, including EC2, S3, and DynamoDB. Customers reported errors and delays. AWS rerouted traffic to other zones to reduce the impact. Other availability zones in the UAE continued to operate normally.

When Will AWS Be Back Up?

AWS recovery is ongoing and may take several hours. Engineers are restoring power, connectivity, and assessing data health. Full restoration of the affected availability zones could extend into the next day. Customers are advised to use alternate AWS regions or availability zones where possible.

AWS outage explained

Amazon Web Services (AWS) experienced a major outage in the United Arab Emirates (UAE) after unidentified objects struck a data center, causing sparks and a fire. The incident affected one availability zone in the ME-CENTRAL-1 region. AWS reported that the event began around 4:30 p.m. Dubai time on Sunday, March 1. Emergency crews cut off power to contain the fire.

AWS outage affected regions

AWS confirmed that the affected zone is mec1-az2. The company rerouted customer traffic while engineers worked to restore connectivity. Other availability zones in the UAE continued to operate, but some customers reported errors and delays. AWS said recovery would take several hours. Customers were advised to use alternate availability zones or other AWS regions.

The disruption affected services across the Gulf, including EC2, Amazon S3, and DynamoDB. AWS described the situation as a localized power and connectivity issue. The fire department shut off power and generators to ensure safety. AWS has not confirmed the type of objects that caused the fire.

The affected regions are:

ME-CENTRAL-1 Region (UAE)
mec1-az2 (primary impacted zone)
mec1-az3 (later impacted)
mec1-az1 (operational but facing API and launch errors)

Bahrain
Reported connectivity and power-related issues

AWS server down issues and customer impact

AWS stated that connectivity and power issues extended to Bahrain, though the UAE incident remained the most serious. Customers faced errors in cloud functions and networking APIs. AWS rerouted traffic away from the impacted zone, which is a standard resilience procedure. Customers with systems tightly coupled to mec1-az2 may continue to experience interruptions until full recovery.

The company operates 123 availability zones across 39 global regions. Most worldwide operations remained unaffected, but the UAE incident highlighted the importance of regional redundancy. Major local businesses rely on AWS in the UAE, especially as Gulf states expand cloud and AI infrastructure.

The outage coincided with missile and drone threats in the UAE during wider regional tensions involving Iran, Israel, and the United States. UAE authorities reported interceptions over the weekend. AWS has not confirmed any direct connection between these events and the data center fire.

AWS affected services

Multiple AWS services were disrupted, including EC2, S3, DynamoDB, Lambda, CloudTrail, Redshift, and others. Some services experienced degraded performance, including Elastic Beanstalk, Elastic Load Balancing, Amazon OpenSearch Service, and Amazon RDS. AWS advised customers to failover to other regions and use remote backups.

The affected AWS services are:

Disrupted Services (16)

• AWS CloudTrail
• AWS Fargate
• AWS Lambda
• AWS Management Console
• Amazon Athena
• Amazon Elastic Compute Cloud (EC2)
• Amazon Elastic Container Registry
• Amazon Elastic Container Service
• Amazon Elastic File System
• Amazon Elastic Kubernetes Service
• Amazon EventBridge
• Amazon EventBridge Scheduler
• Amazon Kinesis Data Streams
• Amazon Redshift
• Amazon Simple Notification Service
• Amazon Simple Storage Service (S3)

Degraded Services (25)

• AWS Application Migration Service
• AWS Config
• AWS Direct Connect
• AWS Elastic Beanstalk
• AWS IoT Core
• AWS IoT Device Defender
• AWS IoT Device Management
• AWS Key Management Service
• AWS NAT Gateway
• AWS Network Firewall
• AWS Step Functions
• AWS Transit Gateway
• Amazon CloudWatch
• Amazon Cognito
• Amazon DynamoDB
• Amazon EMR Serverless
• Amazon Elastic Load Balancing
• Amazon Elastic MapReduce
• Amazon FSx
• Amazon GuardDuty
• Amazon OpenSearch Service
• Amazon Relational Database Service (RDS)
• Amazon Simple Email Service
• Amazon Simple Queue Service
• Amazon Simple Workflow Service

AWS outage error messages

During the AWS outage, customers reported increased error rates and failed API calls across multiple services. Common issues included EC2 API errors, instance launch failures, S3 data ingest and egress failures, and DynamoDB latency. Networking-related APIs such as AllocateAddress and AssociateAddress also returned errors. AWS Management Console and CLI access were disrupted due to the failure of two availability zones, mec1-az2 and mec1-az3. Customers were advised to retry failed requests or shift workloads to alternate regions.

The error messages and technical issues are:

• Increased EC2 API errors
• Instance launch failures
• Inability to launch new instances in region
• High S3 data ingest and egress failure rates
• Elevated S3 error rates and latencies
• DynamoDB significant error rates and elevated latency
• Networking API failures (AllocateAddress, AssociateAddress)
• DescribeRouteTable API failures without specified IDs
• DescribeNetworkInterfaces API failures without specified IDs
• Elastic IP disassociation errors
• AWS Management Console access disruption
• AWS CLI access disruption
• Connectivity issues across affected availability zones
• Elevated latencies across multiple services
• Throttling errors on AllocateAddress API

AWS server down desktop and mobile users issues

AWS server down issues affected both desktop and mobile users who rely on cloud-hosted applications. Since many websites and apps run on AWS infrastructure, users experienced login failures, slow loading times, and service interruptions. Businesses operating in the ME-CENTRAL-1 region reported system downtime and connectivity problems. While unaffected availability zones continued operating, users connected to impacted services faced disruptions until traffic was rerouted and recovery steps progressed.

AWS recovery efforts

AWS continues to work on restoring power and connectivity. Updates indicate recovery for the two impaired availability zones (mec1-az2 and mec1-az3) could take at least a day. Engineers are assessing data health, repairing facilities, and coordinating with local authorities to ensure operator safety.

FAQs

Q1: What caused the AWS outage in the UAE?
AWS said unidentified objects struck a data center, causing sparks and fire. Emergency crews cut power to contain the fire. Full details of the objects are not confirmed.

Q2: When will AWS services be fully restored?
Recovery may take multiple hours. AWS expects restoration of the affected zones to include facility repairs, power checks, and data health assessments, possibly extending into the next day.