Amazon Web Services reported on March 1, 2026, that one of its Availability Zones in the Middle East (UAE) Region — designated mec1-az2 — experienced an emergency power shutdown after objects struck the data center, creating sparks and igniting a fire at approximately 4:30 a.m. PST.
The fire department cut power to the affected zone and its generators while emergency crews extinguished the blaze. AWS stated connectivity restoration would require several hours, but confirmed all other Availability Zones in the ME-CENTRAL-1 (UAE) region remained operational — per Reuters reporting and Data Center Dynamics.
The incident coincided with a wave of Iranian missile and drone strikes across the Gulf region. When asked by Reuters whether the strike on the facility was connected, AWS did not confirm or deny a link.
Breaking — Developing Story
Incident at a Glance — mec1-az2
- •Provider Amazon Web Services (AWS)
- •Affected Zone mec1-az2 (ME-CENTRAL-1, UAE)
- •Incident Date March 1, 2026
- •Time of Impact ~4:30 a.m. PST
- •Cause Objects struck facility; sparks and fire ignited
- •Response Fire department cut power to zone and generators
- •Recovery ETA Several hours (per initial AWS statement)
- •Other UAE Zones Operational — no broader regional outage
- •AWS Confirmation Did not confirm or deny connection to Iranian strikes
- •Geopolitical Context Iranian missile and drone strikes across Gulf region, March 1, 2026
- •Region Launch ME-CENTRAL-1 launched 2022
- •Design Multiple AZs with independent power, cooling, networking
1. Incident Timeline and AWS Statement Details
The event unfolded in the early hours of Sunday, March 1, 2026:
Chronology
- •4:30 a.m. PST: Objects struck the mec1-az2 facility, generating sparks and fire.
- •Immediate response: Fire department shut off power to the zone and generators to contain the blaze.
- •Recovery estimate: Several hours required to restore connectivity and recover affected resources.
- •Regional status: Other Availability Zones in ME-CENTRAL-1 continued normal operations throughout.
In its statement, AWS emphasized the isolation design of Availability Zones — each functioning as a separate, physically distinct location within the region, with independent power, cooling, and networking, to maintain redundancy even during single-zone failures.
2. Affected Infrastructure: ME-CENTRAL-1 and mec1-az2
The Middle East (UAE) Region — AWS region code me-central-1 — launched in 2022 to serve local and regional workloads with low-latency access and in-country data residency compliance. It comprises multiple Availability Zones engineered for high availability.
ME-CENTRAL-1 Infrastructure
2022
Region launch year
mec1-az2
Affected zone
3+
AZs in region (est.)
0
Other zones affected
- mec1-az2 — The specific zone offline pending power restoration and resource recovery.
- Redundancy design — AWS advises customers to distribute workloads across multiple zones to avoid single-zone failure impact.
- No global impact — Other AWS regions worldwide were unaffected.
3. Geopolitical Context: Iranian Strikes Across the Gulf Region
The incident occurred as Iran launched retaliatory missile and drone attacks targeting locations across the UAE and broader Gulf, following prior U.S. and Israeli strikes on Iranian targets. Reports documented strikes on airports, ports, and residential areas, with additional incidents involving debris from intercepted drones impacting civilian sites — per Reuters and the Economic Times.
UAE authorities reported casualties and disruptions at aviation hubs. No official source or AWS has confirmed a direct causal link between the military strikes and the mec1-az2 incident.
Important Note
4. Customer Impact and Recovery Guidance
AWS directed affected customers to reroute traffic to unaffected Availability Zones within ME-CENTRAL-1. Services in other zones remained available, minimizing widespread disruption for customers using multi-zone architectures.
Restoration efforts prioritized power reinstatement followed by resource recovery, with no specific full-resolution timeline beyond "several hours" in the initial statement.
Customer Action
5. Broader Implications for Regional Cloud Infrastructure
The mec1-az2 incident illustrates a risk increasingly relevant to global cloud providers: physical data centers in geopolitically sensitive regions face exposure to conflicts that no amount of software redundancy can fully abstract away.
AWS's multi-zone, multi-region architecture is specifically designed to limit blast radius — a single zone offline does not cascade to a full regional or global outage. The ME-CENTRAL-1 region's continued operation across its other zones demonstrates that design working as intended.
However, the event raises questions about the risk calculus for enterprises hosting compliance-sensitive workloads under UAE data residency requirements in a region that now sits within an active missile exchange corridor.
Key Risk & Architecture Takeaways
- •Physical risk: Data centers in conflict zones face kinetic threats software redundancy cannot eliminate.
- •AZ isolation: AWS's multi-AZ design contained the failure — other UAE zones stayed online.
- •Data residency tension: UAE compliance requirements may force workloads to remain in a zone with elevated physical risk.
- •Customer posture: Multi-AZ and multi-region architectures are essential in geopolitically exposed regions.
When objects strike a cloud data center during missile exchanges but the rest of the region stays online, the real availability zone turns out to be geographic redundancy.