Pull to refresh
Logo
What Changed
Following Why Sign Up
AWS cannot restore data lost in Iranian-struck Middle East data centers

AWS cannot restore data lost in Iranian-struck Middle East data centers

Built World

Bahrain region and one UAE availability zone permanently lost; 270+ services still down

September 15th, 2026: AWS says restoration will take months

Overview

Updated Sep 16

Iranian drone strikes damaged Amazon's Gulf data centers in March. Six months later, Amazon Web Services (AWS) confirmed it cannot restore customer data stored only in Bahrain and one of three UAE availability zones.

The Bahrain damage exceeded what AWS regional services were designed to withstand. More than 130 computing services remain down in Abu Dhabi and 140 in Bahrain, with five restored in each. The UAE relaxed data-sovereignty rules, which normally require data to stay in the country, so affected companies could move data abroad.

Why it matters

Regional conflict can now permanently erase cloud data, so single-region disaster plans are no longer sufficient for any business.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

1
AWS regions permanently lost
Bahrain region exceeded the damage thresholds AWS infrastructure was designed to withstand
1
UAE availability zones permanently lost
Zone mec1-az2 cannot be restored; two other UAE zones remain under recovery
3
Gulf availability zones affected
Damage spanned multiple zones across Bahrain and the UAE
6
Months between strikes and permanent-loss verdict
Strikes hit in early March; AWS confirmed irrecoverable data on September 15
270+
Computing services still disrupted
More than 130 in Abu Dhabi and 140 in Bahrain; only five restored in each

Voices

Curated perspectives — historical figures and your fellow readers.

Sign up to generate historical perspectives on this story.

Log in Sign Up

People Involved

MG
Matt Garman
Chief executive, Amazon Web Services
Overseeing recovery from Gulf strikes

Organizations Involved

Amazon Web Services (AWS)
Amazon Web Services (AWS)
Cloud computing provider
Confirmed permanent data loss in Bahrain and one UAE availability zone

Amazon's cloud computing division and the world's largest cloud infrastructure provider.
United Arab Emirates
United Arab Emirates
National government
Revising AI data center plans after strikes

The UAE is reconsidering plans for a major AI data-center project after Iranian attacks, including dispersing facilities and using underground or blast-resistant infrastructure.

Timeline

February 2026 September 2026

6 events Latest: September 15th, 2026 · 2 months ago
Tap a bar to jump to that date

  1. AWS says restoration will take months

    Latest Statement

    In its September 15 Health Dashboard update, AWS said it had stopped billing for affected regions and urged customers to migrate accessible resources and rebuild from backups.

  2. AWS confirms permanent data loss in Gulf

    Announcement

    AWS determined it cannot restore resources and data hosted exclusively in Bahrain and UAE zone mec1-az2.

  3. Second Bahrain zone disrupted; region unavailable

    Infrastructure

    Further attacks hit another availability zone, rendering the entire Bahrain region unavailable.

  4. AWS urges Bahrain customers to migrate

    Statement

    After first Bahrain availability zone damaged, AWS advised customers to move workloads to other regions.

  5. Iran retaliates; strikes hit AWS Gulf facilities

    Attack

    Iran fired missiles and drones; two AWS UAE facilities hit directly, nearby strike damaged Bahrain site.

  6. US and Israel launch offensive strikes against Iran

    Conflict

    US and Israeli forces began their offensive against Iran on February 28.

Scenarios

1

AWS restores remaining UAE zones as Gulf builds hardened data centers

Possible Resolves by Q2 2027

Discussed by: Reuters, The National

AWS continues recovery work on the two other affected UAE zones, mec1-az1 and mec1-az3. The UAE proceeds with plans to disperse and harden AI data center facilities, using underground and blast-resistant construction. AWS replaces the damaged UAE infrastructure and confirms service restoration for the surviving zones.

2

Bahrain region permanently decommissioned

Likely Resolves by Q1 2027

Discussed by: The Register, Tom's Hardware

AWS formally writes off the Bahrain region, which suffered damage across multiple availability zones. Customers who migrated to European regions stay there permanently. AWS issues its promised early 2027 update confirming the region will not return to service in its current form.

3

Customers sue AWS over permanently lost data

Possible Resolves by Mar 1, 2028

Discussed by: The Register, legal observers covering the outage

Companies that kept data exclusively in the affected zones file claims against AWS, arguing the company failed to protect stored data. AWS counters that it advised migration after the first strikes and that regional conflict fell outside service-level guarantees. The case tests whether cloud providers bear liability for war damage.

4

UAE data-sovereignty exceptions become permanent policy

Possible

Discussed by: Hindustan Times, industry insiders

The UAE allowed some companies to move data abroad despite strict data-sovereignty rules. If the exceptions become permanent, Gulf cloud customers gain a legal path to cross-region backups. AWS's recovery timeline and the UAE's underground data center plans will determine whether the relaxation is temporary or structural.

5

AWS shifts Gulf investment to hardened or alternative sites

Likely

Discussed by: CRN, Tom's Hardware

AWS partners hope the company's $220 billion spending plan continues despite Gulf losses. AWS may redirect some Middle East capital to the planned Saudi Arabia region or to hardened facilities. New Gulf capacity announcements will show whether the strikes changed AWS's regional strategy.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

March 2021

OVHcloud Strasbourg fire (2021)

A fire broke out in OVHcloud's SBG2 data center in Strasbourg, France, and destroyed the building. Customers without off-site backups lost data permanently. The fire also forced the adjacent SBG1 center offline.

Then

OVHcloud rebuilt and offered tiered compensation that covered only a fraction of customer losses.

Now

The fire became a benchmark for physical data center risk, showing that even industrial-grade facilities can fail catastrophically.

Why this matters now

Like Strasbourg, the Gulf loss proves physical events can permanently destroy cloud data. Unlike a fire, a war creates escalating regional risk that redundancy within one geographic area cannot mitigate.

2022-2023

Russian strikes on Ukrainian infrastructure (2022-2023)

Russian missiles targeted Ukrainian power grids and data infrastructure as part of the invasion. Cloud providers moved workloads to Polish and other European regions, and some Ukrainian data became inaccessible for extended periods.

Then

European data centers absorbed displaced workloads. Ukrainian businesses adopted multi-region backup strategies.

Now

The war demonstrated that active conflict zones cannot host reliable cloud infrastructure, reshaping where providers build capacity.

Why this matters now

The Gulf strikes repeat the Ukraine pattern of wartime migration to safer regions. AWS's Gulf loss extends it by confirming complete data destruction, not just temporary outage, inside a conflict zone.

September 2001

September 11 attacks (2001)

Companies in the World Trade Center lost servers, records, and operations when the towers fell. Firms without off-site backups lost data permanently; others recovered from tape archives stored elsewhere.

Then

The disaster pushed businesses to adopt off-site backup and geographic redundancy as standard practice.

Now

Disaster recovery and business continuity became formal disciplines with dedicated vendors and standards.

Why this matters now

The 9/11 lesson was about replicating data off-site. AWS's Gulf loss shows the limits of that approach: backups kept in the same war zone can be destroyed alongside primary systems, forcing true cross-region strategies.

Sources

(9)
+3
The Wall Street Journal Bloomberg The Register The National Reuters via The Express Tribune The Next Web Tom's Hardware Hindustan Times CRN