Amazon said its cloud operations in Bahrain were disrupted again on March 24, 2026, after drone activity linked to the Iran war affected data center operations, marking the second AWS disruption in the Middle East since the conflict escalated on March 1. The latest incident follows earlier damage to three AWS facilities in the United Arab Emirates and Bahrain, according to reporting from the Associated Press and other industry publications.
For cloud customers, the significance is not only the outage itself but the pattern. AWS is one of the world’s largest cloud providers, and its Middle East footprint is designed around multiple availability zones intended to isolate failures. The March 24 disruption shows that geopolitical conflict can still impair physical infrastructure even when cloud architecture is built for redundancy. Earlier in March, AWS said drone strikes caused structural damage, power disruption, fire, and water damage at facilities in the UAE and Bahrain.
🔴
AWS has now reported two Middle East disruptions in March 2026 tied to the Iran war.
AP reported on March 24 that Bahrain operations were disrupted again, after earlier March 1 attacks damaged three AWS facilities in the UAE and Bahrain.
AWS Middle East Disruption Snapshot
| Date | Location | Reported impact | Named source |
|---|---|---|---|
| March 1, 2026 | UAE and Bahrain | Three facilities damaged; fire, power and water damage reported | AP, AWS updates cited by industry media |
| March 24, 2026 | Bahrain | Operations disrupted again by drone activity | AP |
Source: Associated Press and industry coverage | accessed March 24, 2026 UTC.
March 24 disruption adds to a March 1 infrastructure shock
The latest reported disruption centers on Bahrain. According to the Associated Press on March 24, Amazon said data center operations in Bahrain were disrupted by drone activity, the second time AWS cloud facilities in the Middle East have been affected since the Iran war erupted. AP also reported that three AWS Middle East data centers, including two in the UAE and one in Bahrain, were damaged by Iranian drone strikes days after the war began.
That earlier incident was more extensively documented across technology and infrastructure outlets. Data Center Dynamics reported on March 3 that Amazon confirmed two UAE data centers were hit and a third Bahrain facility was damaged. Reuters-syndicated coverage carried by Yahoo said the drones caused structural damage, disrupted power delivery to infrastructure, and in some cases triggered fire suppression systems that added water damage. Those details matter because they show the outages were tied to physical facility impairment, not a software bug or routing error.
Timeline of AWS disruptions linked to the Iran war
March 1, 2026: AWS reports that objects struck a UAE data center, causing sparks and fire at the mec1-az2 availability zone, according to multiple technology reports citing AWS service updates.
March 2-3, 2026: Industry and AP reports say three AWS facilities in the UAE and Bahrain were damaged, with two impaired availability zones in the ME-CENTRAL-1 region.
March 24, 2026: AP reports a second disruption in Bahrain due to drone activity amid the ongoing Iran war.
How 3 damaged facilities exposed cloud redundancy limits
AWS regions are built around multiple availability zones, and AP noted on March 3 that each region is split into at least three data center availability zones that are physically separated but connected by low-latency networks. In theory, that design helps workloads survive the loss of one zone. In practice, reports from March 1-3 indicated that more than one zone in the Middle East Central region was impaired, which raises the operational pressure on customers that had not deployed cross-region failover.
The Register reported that AWS began investigating disruption to mec1-az2 at 12:51 UTC on March 1, and later said power disruptions spread to another UAE availability zone, mec1-az3, affecting services including S3. Business Today, citing AWS dashboard updates, also reported a power shutdown and fire at the UAE facility. Taken together, those reports suggest the first wave of damage was not confined to a single isolated fault domain.
Reported technical impact in early March 2026
| Metric | Reported detail | Context |
|---|---|---|
| Facilities damaged | 3 AWS facilities | Two in UAE, one in Bahrain |
| Availability zones impaired | At least 2 in ME-CENTRAL-1 | mec1-az2 and mec1-az3 cited in reports |
| Failure type | Physical damage | Fire, power disruption, water damage |
Source: AP, The Register, Business Today, Data Center Dynamics | March 1-3, 2026.
Why Bahrain matters in a second March 2026 incident
The March 24 report is important because it indicates the operational risk has not passed. AP said Bahrain operations were disrupted again by drone activity. That follows a period in which AWS had already urged customers, according to industry reports, to back up data, activate disaster recovery plans, and consider migrating workloads to alternate AWS regions. A repeat event in the same month can force enterprises to reassess whether in-region redundancy is sufficient in a conflict zone.
There is also a broader infrastructure angle. AP and SecurityWeek both emphasized that the strikes highlighted the vulnerability of data centers to physical disasters and conflict, even though hyperscale cloud systems are engineered for resilience. Euronews separately reported that experts see data centers as increasingly exposed in modern warfare. That does not mean cloud architecture failed in general; it means physical concentration risk becomes more visible when multiple facilities in one geographic theater are threatened within weeks.
ℹ️
AWS availability zones are designed to isolate failures, but they are still geographically clustered.
AP reported that zones are separated by meaningful distance yet remain within roughly 100 kilometers and are linked by low-latency networks, a design that improves resilience but does not remove regional conflict risk.
What the second disruption means for customers and cloud risk
For enterprises, the immediate issue is service continuity. Reports from early March said customers in the region, including banks, payments firms, and app platforms, experienced disruptions after the first strikes. Tom’s Hardware and Yahoo-cited reporting listed affected sectors ranging from banking to ride-hailing and data services. Those examples show that even localized cloud incidents can spill into consumer finance and digital commerce when workloads are concentrated in one region.
The second issue is architecture. If one availability zone fails, many applications should continue running. If two zones are impaired and a neighboring country’s facility is also affected in the same conflict cycle, the case for multi-region deployment becomes stronger. That is an inference based on AWS’s own regional design principles and the pattern of March incidents reported by AP and infrastructure outlets.
Third, the story broadens beyond Amazon. The March incidents have become a test case for whether cloud infrastructure is now treated as strategic economic infrastructure during wartime. TechPolicy.Press reported that the legal and policy fallout is already under discussion because the attacks targeted facilities tied to commercial and potentially government-linked workloads. That debate is likely to continue as operators, insurers, and regulators assess physical resilience standards for data centers in geopolitically exposed markets.
Frequently Asked Questions
Frequently Asked Questions
What happened to Amazon’s cloud facilities on March 24, 2026?
Associated Press reported on March 24, 2026, that Amazon said its Bahrain cloud operations were disrupted again by drone activity tied to the Iran war. AP described it as the second AWS Middle East disruption since the conflict escalated earlier in March.
How many AWS facilities were damaged in the earlier March incident?
AP reported on March 3, 2026, that three AWS facilities were damaged: two in the United Arab Emirates and one in Bahrain. Other infrastructure coverage, including Data Center Dynamics, matched that count and said the damage followed Iranian drone strikes.
Was this a software outage or physical damage?
Reports from March 1-3 described physical damage. Reuters-syndicated coverage said the strikes caused structural damage, power disruption, and in some cases fire suppression activity that added water damage. That distinguishes the incident from a typical software or networking fault.
Why did AWS redundancy not fully prevent disruption?
AWS regions use multiple availability zones to isolate failures, and AP said those zones are physically separated. But reports from early March indicated that at least two zones in the Middle East Central region were impaired, while Bahrain was also affected, reducing the protection customers get from single-zone redundancy alone.
Which customers or sectors were reported as affected?
Technology coverage in early March said disruptions were reported by banks, payments firms, ride-hailing platforms, and data service providers in the Gulf. Named examples in those reports included UAE banks and regional app platforms, showing the outages reached beyond internal AWS systems into customer-facing services.
Disclaimer: This article is for informational purposes only. Information may have changed since publication. Always verify information independently and consult qualified professionals for specific advice.
