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.
This is a developing story. AWS has not confirmed the nature of the objects that struck mec1-az2, nor any direct connection to Iranian military activity. ObjectWire will update as information becomes available.
Incident Timeline and AWS Statement Details
The event unfolded in the early hours of Sunday, March 1, 2026:
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.
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.
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.
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.
AWS explicitly declined to confirm or deny a connection to Iranian military activity when queried by Reuters. Reporting characterizing this as a confirmed strike should be treated with caution pending official clarification.
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.
Customers with workloads in mec1-az2 should check the AWS Service Health Dashboard for real-time updates and redirect traffic to mec1-az1 or mec1-az3 if available.
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.
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.