TL;DR
Two major “data chokepoints” — the Red Sea and the Strait of Hormuz — are under simultaneous stress, raising the risk of slower, more expensive routing for international traffic.
Iran’s Revolutionary Guards have issued explicit warnings that the Strait of Hormuz is closed and threatened ships attempting passage.
AWS says drone strikes physically damaged facilities in the UAE and Bahrain, disrupting cloud services and forcing some customers to rely on failovers and reroutes.
The story isn’t “the internet will shut down.” It’s “the internet will get worse.”
The internet is built to survive cable cuts. Traffic can reroute across alternate paths, and cloud providers run redundant systems. That’s why a global “off switch” is unlikely even in a serious escalation.
But this moment is still dangerous in a very practical way: when multiple high-capacity routes are stressed at the same time, the backup routes get crowded. The outcome isn’t darkness — it’s congestion: higher latency, more packet loss, and higher transit costs that can show up as slower apps, degraded video calls, and cloud performance issues.
Why the Red Sea matters (and why everyone keeps citing the “17 cables” number)
The Red Sea is one of the world’s densest subsea corridors for data moving between Europe, Asia, and Africa. Reporting notes 17 submarine cables pass through it, carrying a large share of intercontinental traffic. When cables here are damaged or repair activity becomes difficult, networks often reroute around longer paths — which can add time and pressure.
Even in normal times, a few cuts can be enough to raise latency for certain routes because operators move traffic onto whatever capacity remains available.
Why Hormuz is different: it’s not just about cables — it’s about access
The Strait of Hormuz is a critical maritime choke point. For digital infrastructure, it’s one of the gateways for cables serving Gulf states and for maintenance access to parts of that network.
What makes this escalation uniquely alarming is the explicitness of the threat. Reuters reported an IRGC-linked official saying the strait is closed and that any ship attempting to pass would be attacked (“set ablaze”). That kind of language changes behavior quickly — insurers reprice risk, commercial operators pause movements, and repair logistics become harder.
The “digital battlefield” isn’t metaphorical anymore: AWS says facilities were physically hit
This is the part that turns the story from “telecom theory” into “real-world outage risk.”
AWS said drone strikes caused physical damage to multiple facilities in its UAE and Bahrain footprint, with disruptions tied to structural damage, power delivery issues, and fire suppression impacts that created additional damage. AWS also said parts of its regional capacity remained impaired.
This matters because the Gulf’s cloud regions don’t just host consumer apps — they host enterprise systems for banks, government platforms, media, logistics, and payment flows. Even when services recover, customers often tighten disaster recovery posture and shift workloads out of affected zones, which can create secondary strain elsewhere.
What “global impact” could look like in real business terms
If both major corridors are constrained, the impact won’t be uniform. It tends to show up first in:
Cross-region cloud traffic: apps that depend on calls between Gulf cloud regions and Europe/Asia can slow down.
Banking and payments: not because banks “go offline,” but because latency and service degradation can affect transaction speeds and reliability windows.
Enterprise VPNs and corporate networks: congestion makes remote operations and cross-border workflows less stable.
Cost: transit providers and insurers price higher risk; businesses feel it through network bills and cloud architecture changes.
The realistic risk window
The highest-risk period is when:
multiple cables are already constrained, and
ships and repair crews can’t safely access key sea lanes, and
cloud regions face direct security incidents.
That combination doesn’t have to last long to cause meaningful disruption: even a few days of congestion can be costly for businesses that operate on tight latency and uptime assumptions.
