Iran strikes knock AWS zones offline in UAE
What happened
Iran-linked strikes reportedly hit key Amazon Web Services availability zones in Bahrain and Dubai, leaving parts of both regions effectively offline. Internal communications cited in the pool describe those zones as “hard down” and indicate Amazon expected them to be unavailable for an extended period.
Where the disruption hit
The affected infrastructure is tied to cloud capacity in the Gulf: at least two AWS zones—one in Bahrain and one in Dubai—were taken out by the reported strikes. For customers, that typically means workloads hosted in those zones could fail over slowly, lose access to dependent services, or experience degraded performance until capacity returns.
Why this matters
Cloud outages tied to geopolitical events are a reminder that “regional” resiliency is only as strong as the independence of the underlying facilities. Even though major cloud providers build redundancy across zones, a strike that simultaneously affects multiple locations within a region can force organizations to rely on cross-region failover plans—and to test them.
The disruption also reinforces that global cloud reliability is increasingly influenced by non-technical risks like energy, logistics, and physical security. For enterprises with strict uptime requirements, incidents like this elevate the importance of:
- multi-region architecture,
- well-defined disaster recovery procedures,
- and monitoring that can quickly detect when a specific zone is “hard down.”
What to watch next
Expect customer follow-ups on how quickly deployments recovered and whether AWS offered additional guidance for impacted services. Organizations will likely review which dependencies were pinned to the affected zones and whether their failover runbooks worked as intended.