Meta's 2Africa Cable Force Majeure: Iran War Closes Both Internet Chokepoints

Alcatel Submarine Networks — the French state-owned company contracted to lay Meta's 2Africa Pearls cable through the Persian Gulf — issued force majeure notices to its clients in March 2026, declaring it can no longer safely operate in the Gulf due to active military operations. The 2Africa cable, which would have been the longest submarine cable in the world upon completion, is now indefinitely delayed for its Gulf segment.

For the first time in the history of global internet infrastructure, both of the world's critical maritime data chokepoints are simultaneously compromised. The Red Sea — through which roughly 17 submarine cables carry the majority of data traffic between Europe, Asia, and Africa — was already disrupted by Houthi activity dating back to late 2023. The Persian Gulf is now inaccessible to cable laying and repair vessels due to active military operations. The two routes are not independent alternatives to each other. They are the only two exits.

What the 2Africa Force Majeure Means

The 2Africa Pearls cable is a $1 billion+ project backed by Meta and a consortium of telecom partners designed to circle the African continent and extend into the Middle East via a branch through the Persian Gulf. When completed, it would add roughly 45 Tbps of capacity to the Africa-Middle East connectivity corridor.

Force majeure suspends contract obligations due to circumstances beyond the parties' control. In this context, Alcatel is telling Meta and the other consortium members: we cannot send cable ships into the Persian Gulf to lay or repair cable while Iranian drones and US-Israeli airstrikes are operating in the same airspace and maritime corridor. The force majeure is not about technical failure — the cable hardware exists and is partially deployed. It is about physical access to the operational theater.

The affected Gulf segment covers connectivity for Iran, Iraq, Kuwait, Bahrain, and Qatar. Bahrain hosts the US Fifth Fleet. Qatar hosts Al Udeid Air Base. Both are active military operations areas. No commercial maritime operator is going to send a specialized cable ship into that environment.

The Double Chokepoint Problem

Submarine cable infrastructure has two critical maritime chokepoints connecting the globe: the Red Sea / Bab el-Mandeb Strait (connecting the Mediterranean to the Indian Ocean) and the Persian Gulf / Strait of Hormuz (connecting Gulf states to the broader Indian Ocean network).

The Red Sea has been operationally compromised since the Houthi cable cutting operations of early 2024 and the continuing security environment that prevents cable repair vessels from transiting safely. Three major cables were cut in the Red Sea in early 2024; at least two remain unrepaired because repair ships cannot get access under safe maritime conditions.

The Persian Gulf closure via force majeure from the Iran war now closes the only geographic alternative. Data traffic that cannot route through the Red Sea could previously detour through overland connections or via the Persian Gulf branches. With both compromised simultaneously, traffic is routing through longer paths — around the Cape of Good Hope, through overland fiber in Turkey and the Caucasus, or through satellite links — all with higher latency and lower aggregate capacity.

Which Cables and Projects Are Affected

Beyond 2Africa, multiple major projects are in limbo:

SEA-ME-WE 6 (Southeast Asia to Middle East to Western Europe, consortium including Orange, Telecom Italia, and major Asian carriers) has segments that route through the Persian Gulf and Red Sea. The conflict has thrown its completion timeline into uncertainty.

The Fibre in Gulf (FIG) cable system, which connects UAE, Qatar, Bahrain, Kuwait, Iraq, and Pakistan, is operated infrastructure in an active conflict zone. Repair vessels cannot access damaged segments.

WorldLink Transit Cable Project, an emerging connectivity initiative for Gulf-to-Europe routing, has paused development activities.

What Gulf States Are Building Instead

Six competing overland cable projects backed by Gulf sovereign funds are racing to provide an alternative to maritime routes. The approaches vary: routing through Syria and Turkey to reach Mediterranean landing points, routing through Iraq and the Caucasus toward Eastern Europe, and a proposed Horn of Africa overland route skirting the Red Sea entirely.

The technical challenge is that overland routes add latency versus direct submarine cables (roughly 1 ms per 200 km of fiber), require right-of-way negotiations across multiple sovereign territories, and need to traverse politically unstable regions including Syria and Iraq. None of these projects can deliver the capacity equivalent of a major submarine cable system within a 12-to-24 month window.

Saudi Arabia and the UAE are the primary investors in overland diversification. Both countries have concluded that maritime route dependency is a structural vulnerability — one that the current conflict has converted from theoretical to actual.

What This Means for Developers and Latency

For developers running applications serving users in the Middle East, Africa, and South Asia, the cable disruption environment means:

Latency to Gulf-region users from European and US origin points is elevated. Traffic that previously routed through the Red Sea and Gulf cables is now taking longer paths, adding 20 to 80 ms of additional latency depending on the route. CDN cache hit rates in the region drop when origin pulls take longer.

API calls from Gulf-region developers to US or European cloud services are similarly affected. If you are building applications in the UAE, Saudi Arabia, or Qatar and relying on API endpoints hosted in the US or Europe, your baseline latency assumptions from 18 months ago may no longer be accurate.

The risk of physical cable damage adds a discontinuous failure mode on top of the latency increase. A cable that gets struck by a drone or anchor-dragged during military operations does not produce graceful degradation — it produces complete path failure until an alternative route absorbs the load. With both chokepoints compromised, the alternative route capacity is already partially consumed.

For Gulf region applications requiring low latency — real-time trading, AI inference with time-sensitive SLAs, video conferencing — the engineering response is to push more workloads to Gulf-region cloud infrastructure (Azure UAE, AWS ME-CENTRAL-1 if it recovers, Oracle Gulf) rather than backhauling to US or European data centers. That recommendation is unchanged from pre-conflict best practice, but the urgency is now significantly higher.

Key Takeaways

• Meta's 2Africa Pearls cable is force majeure: Alcatel Submarine Networks cannot operate in the Persian Gulf due to active military operations — Gulf segment of the world's largest planned submarine cable is indefinitely delayed
• First time both global internet chokepoints are simultaneously compromised: Red Sea disrupted since Houthi cable-cutting in 2024, Persian Gulf now inaccessible for cable operations due to Iran war
• SEA-ME-WE 6, FIG, and WorldLink projects are all in limbo: major cable systems serving the Middle East-Europe corridor are affected
• Traffic is rerouting via longer paths: Cape of Good Hope, Turkish overland, Caucasus fiber — all with higher latency and lower capacity than the compromised direct routes
• Six overland alternatives are in development: Gulf sovereign fund-backed projects routing through Syria, Iraq, and Horn of Africa — none deliverable within 12 months
• Developer action: if you serve Gulf-region users, audit your latency baselines and push workloads to in-region cloud infrastructure rather than backhauling through degraded maritime routes