AWS says it can't restore service to Bahrain, UAE facilities 6 months after Iran strikes
- ID
- 24820
- Status
- summarized
- Published
- 16 Sep 2026, 3:04 AM
- Fetched
- 16 Sep 2026, 3:50 AM
- Provider
- CNBC Technology
- Category
- technology
- Original URL
- https://www.cnbc.com/2026/09/15/aws-cant-restore-service-to-bahrain-uae-6-months-after-iran-strikes.html
- Source URL
- https://www.cnbc.com/id/19854910/device/rss/rss.html
Summary
- Score
- 7.5
- Created
- 16 Sep 2026, 3:54 AM
- Tags
- Audience
- developersdatabase_learnerssaas_startups
What happened
AWS publicly confirmed it cannot restore service or recover data from facilities in Bahrain and parts of the UAE, more than six months after drone strikes in March damaged multiple data centers. AWS stated the damage exceeded what its services are designed to withstand, and it is still working to restore two other UAE availability zones. This is AWS's first public update since April.
Why it matters
This is a rare case of a major cloud provider permanently losing customer data due to physical infrastructure destruction. If you run workloads in any single region—especially smaller or geopolitically exposed ones like AWS Middle East (me-south-1 or me-central-1)—this is your signal to verify your disaster recovery actually replicates to a second, geographically distant region and that you can tolerate total data loss in one region. Builders who assumed AWS's multi-AZ design protects against regional loss should note that all availability zones in Bahrain were lost together.
Discussion angle
How many of us actually have working cross-region backups vs just assuming multi-AZ is enough? This is a concrete case where multi-AZ failed because the threat was physical, not software—worth reviewing what your own DR plan assumes about simultaneous AZ loss.