Iran threatens Gulf data centres: How exposed is the region’s internet?

More than 90% of data capacity between Europe and Asia passes through undersea cables beneath the Red Sea, while nearly one-fifth of global internet traffic passes through the Bab al-Mandeb chokepoint, leaving Gulf connectivity exposed to conflict and disruption. Iran has threatened regional cables, data centres and AI facilities; AWS reported drone strikes directly hit two UAE facilities and caused physical impact near a Bahrain site, and it said some Bahrain and UAE sites could not be restored. Iraq and Microsoft have announced connectivity investments and Gulf states continue major AI and data-centre plans, but security risks could raise costs and alter where regional digital infrastructure is built.

Analysis

Analysis The key market mechanism is a higher reliability premium on Gulf compute: operators may need more geographic redundancy, backup power/cooling and connectivity routes. That raises build and operating costs and could slow utilization of planned AI capacity before it materially changes long-run demand. Sovereign-cloud requirements constrain the easiest fix—moving sensitive workloads outside the region—so resilience spending may not translate one-for-one into productive GPU capacity.

For listed hyperscalers, distinguish localized AWS disruption from Amazon’s consolidated earnings exposure; the article provides no outage-related financial estimate. A regional incident alone is not a basis for shorting AMZN, GOOG, MSFT or ORCL. Over 1–3 months, watch disclosed service availability, customer credits, impairment charges and regional capex revisions. Over 6–18 months, repeated outages or higher insurance/security costs could weaken Gulf project returns and defer demand for NVDA accelerators. Conversely, resilience requirements could support incremental infrastructure orders, though timing and beneficiaries are unverified.

The contrarian point: redundancy is costly, but alternate routes and dispersed facilities could reduce the probability that one chokepoint permanently limits regional digital growth. Headlines may overstate the near-term earnings risk to global platforms while understating the gradual return drag on Gulf-hosted projects. Thesis breaks if service restoration is rapid, customer workloads remain sticky and planned capacity comes online without material cost or schedule changes.

Key Decisions for Investors

• No broad short on the named US tech companies based on the threat alone. Treat AWS facility effects as subsidiary-level until Amazon quantifies consolidated impairment, lost revenue or customer credits.
• Watch AMZN versus MSFT as a conditional relative-value setup, not an immediate entry: consider underweighting AMZN only if subsequent disclosures show persistent AWS capacity/customer impacts while Microsoft reports no comparable regional disruption. Exit the thesis if AWS restoration and utilization normalize without material earnings revisions.
• Track Gulf data-centre project delays, regional cloud availability, insurance/security costs and disclosed capex returns over the next 1–3 months; a material schedule or utilization downgrade would strengthen the case to reduce exposure to Gulf-dependent AI buildout, including second-order demand risk to NVDA.
• For the 6–18 month view, monitor whether sensitive workloads can legally and commercially use non-Gulf redundancy. If sovereignty constraints prevent workload relocation and repeated outages raise operating costs, reassess Gulf project economics; if route diversity and recovery performance improve, the geopolitical discount may be overdone.