Cloud · Amazon Web Services
AWS Middle East (UAE) and (Bahrain) regions damaged by drone strikes
- Started
- Mar 1, 2026, 12:30 UTC
- Duration
- Not published
- Affected
- Amazon EC2, Amazon EBS, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, AWS Management Console and CLI, Amazon Route 53 (DNS change propagation in ME-SOUTH-1)
- Cause
- Preliminary causeAWS first described a localized power issue in one UAE Availability Zone, then said objects struck the data center, causing sparks and fire, and the fire department cut power. On 3 March AWS said both Middle East regions had physical impacts from drone strikes: two UAE facilities were directly struck and a strike near a Bahrain facility damaged infrastructure. AWS later said it cannot restore resources and data held only in mec1-az2 or in the Bahrain region.
- Was it an attack?
- Not stated
- State
- monitoring
Anatomy
1. Trigger
Physical damage
2. Already broken
None stated
3. What made it spread
Control-plane dependency
4. Blast radius
multi region: me-central-1 (UAE), me-south-1 (Bahrain)
5. Cause category
Physical damage
Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.
How the explanation changed
March 1, 2026 · Preliminary cause
“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.”
March 1, 2026 · Preliminary cause
“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 department shut off power to the facility and generators as they worked to put out the fire.”
March 3, 2026 · Preliminary cause
“Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure.”
September 15, 2026 · Preliminary cause
“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.”
September 15, 2026 · Preliminary cause
“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.”
What the provider committed to change
- Replace the affected infrastructure in UAE; restoration update promised 'in the coming months' (15 Sep 2026)
- Further update on Bahrain promised in early 2027 (15 Sep 2026)
- Billing operations suspended for both regions while normal operations are restored (30 Apr 2026)
Impact, as reported
- UAE Availability Zones impaired: 2 of 3 (mec1-az2, mec1-az3), according to AWS Health Dashboard (AWS Health Dashboard current events JSON (ME-CENTRAL-1 and ME-SOUTH-1 'Region Availability' event logs)).
- facilities damaged: two UAE facilities directly struck; one Bahrain facility affected by a nearby drone strike, according to AWS Health Dashboard (AWS Health Dashboard current events JSON (ME-CENTRAL-1 and ME-SOUTH-1 'Region Availability' event logs)).
- data loss: resources and data hosted only in the Bahrain Region cannot be restored, according to AWS Health Dashboard (AWS Health Dashboard current events JSON (ME-CENTRAL-1 and ME-SOUTH-1 'Region Availability' event logs)).
Every figure is attributed to whoever stated it. Crowd reports are labelled user reports and never treated as users affected.
Other Amazon Web Services incidents
- AWS us-west-2 loses internet connectivity over the route to the Seattle metro, July 24, 2026
- AWS US-EAST-1 use1-az4 thermal event, May 7, 2026
- AWS us-east-1 outage from DynamoDB DNS automation race condition, October 20, 2025
Sources
- AWS Health Dashboard current events JSON (ME-CENTRAL-1 and ME-SOUTH-1 'Region Availability' event logs) (provider, read November 17, 2026)
- AWS Health Dashboard (provider, read November 17, 2026)
- The National: Drone strikes damage Amazon data centres in UAE and Bahrain, disrupting services (3 Mar 2026) (news, read November 17, 2026)
- Al Jazeera with Reuters: Amazon says AWS Bahrain region 'disrupted' following drone activity (24 Mar 2026) (news, read November 17, 2026)
Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.