Iran Threatens Undersea Cables — Gulf Digital Catastrophe Risk

Abhishek GautamAbhishek Gautam7 min read
Iran Threatens Undersea Cables — Gulf Digital Catastrophe Risk

Quick summary

Cable attacks would dwarf single-datacenter outages. Multi-region failover checklist for MENA and EU–Asia traffic.

Tasnim News Agency, which is directly linked to Iran's IRGC, published a piece on April 22, 2026 characterising undersea internet cables as Iran's "fatal weakness" and warning of a potential "digital catastrophe" if the conflict escalates. Alcatel Submarine Networks, the world's largest cable laying company, issued force majeure notices for Persian Gulf operations the same day, effectively suspending cable maintenance activities in waters adjacent to the conflict zone.

The timing makes the Tasnim framing unambiguous: this is not a warning to Iran to protect its cables. It is a signal to the US and Gulf states that the IRGC knows where the cables are and what cutting them would do.

What Tasnim Published and What It Means

Tasnim News Agency is not state media in the ordinary sense. It was founded in 2012 with direct IRGC backing and serves as the IRGC's semi-official communications channel — distinct from IRNA (the Islamic Republic News Agency, which reports to the government) and Press TV (which targets English-language audiences). When Tasnim publishes a strategic vulnerability assessment, it is the IRGC communicating to an informed audience.

The "fatal weakness" framing is deliberate. Iran has spent years building internet infrastructure specifically designed to route around the Hormuz choke point — most significantly the Jask cable landing station on the Gulf of Oman coast, south of Hormuz, which became operational in 2021 and was Iran's attempt to decouple its domestic internet from cable routes that pass through the Strait. The Tasnim article identifies that this decoupling is incomplete and that Iran's connectivity — and the connectivity of every country whose cables pass through or near IRGC-controlled waters — remains vulnerable.

This is deterrence communication. The IRGC is telling the US: the cables are there, we know they are there, and this crisis has a digital dimension that your conflict calculus may not have fully priced.

Which Cables Are at Risk

The Persian Gulf and Gulf of Oman host several major undersea cable systems that carry internet traffic between Asia, the Middle East, and Europe:

AAE-1 (Asia-Africa-Europe 1): A 25,000km cable connecting Hong Kong through Southeast Asia, the Indian subcontinent, the Middle East, East Africa, and into Europe. Its Middle East segment passes through the Gulf of Oman and connects at landing stations in Oman, UAE, and Pakistan. Traffic volume: estimated 40 terabits per second of capacity.

SEA-ME-WE 5 and SEA-ME-WE 6: The Southeast Asia-Middle East-Western Europe cable series. SEA-ME-WE 5 connects Singapore through the Indian subcontinent to France via the Red Sea and Mediterranean. The Persian Gulf segment feeds Gulf state connectivity. SEA-ME-WE 6 (completed 2025) follows a similar route with upgraded capacity.

FALCON: Dedicated Gulf states interconnect cable. Connects Saudi Arabia, Kuwait, Bahrain, Qatar, UAE, and Oman in a loop. Primarily used for intra-Gulf data centre interconnects and enterprise traffic.

Gulf Bridge International (GBI): Connects Iraq, Kuwait, Bahrain, Qatar, UAE, Oman, and Yemen. Provides redundant Gulf connectivity for telecom carriers.

2Africa: The 45,000km cable (completed 2024) connecting Africa, Europe, and the Middle East. Its eastern segment runs through the Red Sea and into the Gulf of Oman, with landing stations in Oman and Pakistan.

The IRGC's proximity to cable routes matters most in the Gulf of Oman approach to Hormuz — where cables converge before splitting toward their respective Persian Gulf and Indian Ocean destinations. The Jask area, specifically, sits at the junction where cables either terminate in Iran or continue northward into the Gulf.

Alcatel Force Majeure: What It Actually Means

Alcatel Submarine Networks (ASN), owned by Nokia since 2016, is the company that physically lays, maintains, and repairs most of the world's undersea cable systems. A force majeure declaration by ASN is not a press release — it is a legal notice to cable owners and operators that ASN cannot fulfill its maintenance obligations due to conditions outside its control.

Force majeure for Persian Gulf operations means:

No repair ships in the area. ASN operates cable repair vessels that respond to cable cuts (faults occur regularly from ship anchors, fishing trawl nets, and seabed movement). In normal operations, a cable fault in the Persian Gulf is repaired within 3-6 weeks. With force majeure in effect, the repair timeline becomes indefinite — no vessel enters the conflict zone.

Faults accumulate without repair. The Persian Gulf and Gulf of Oman have historically averaged 5-8 cable faults per year. With ASN standing down, any fault that occurs during the conflict period goes unrepaired. Multiple simultaneous faults — which is common when a major anchor drag or seabed event occurs — produce cascading degradation across systems.

Cable owners bear the liability. Force majeure shifts the liability for unrepaired cable damage from ASN to the cable consortium owners (Google, Meta, Amazon, Microsoft, and multiple telecom carriers each hold stakes in Persian Gulf cables). Their maintenance insurance does not cover war-risk damage.

The Red Sea precedent is directly relevant here. When Houthi-linked activity cut AAE-1, SEACOM, and EIG cables in the Red Sea in late 2023, ASN declared force majeure for Red Sea repair operations. Those cables remained unrepaired for months. Traffic was rerouted around Africa, adding 100-150 milliseconds of latency to Europe-Asia routes. The Persian Gulf scenario would produce similar or worse effects — because Persian Gulf cables serve the Gulf states themselves, not just east-west transit traffic.

The Red Sea + Hormuz Dual Chokepoint

The most significant dimension of the Tasnim warning is that it comes while Red Sea cable damage from the 2023-2024 Houthi operations remains partially unrepaired. The two major cable chokepoints between Asia and Europe are:

Red Sea: Cables running from the Indian Ocean through the Red Sea to the Mediterranean. Status: three major cables (AAE-1, SEACOM, EIG) cut in 2023-2024, partially repaired, operating at degraded capacity. Force majeure in effect for repair vessels.

Persian Gulf / Gulf of Oman: Cables running from the Indian subcontinent and Southeast Asia into the Gulf states and toward Iran. Status: intact but now under IRGC threat with Alcatel force majeure in effect.

Traffic that cannot route through the Red Sea uses the Cape of Good Hope route around Africa — adding 100-150ms latency. Traffic that cannot route through the Gulf of Oman has no comparable reroute option for Gulf-state terminating traffic. Gulf states (UAE, Saudi Arabia, Kuwait, Qatar) would face direct connectivity degradation with no reroute path.

For cloud infrastructure specifically: AWS ME-South (Bahrain), Azure UAE North, and Google Cloud ME Central all depend on Gulf of Oman cable connectivity for their low-latency links to European and Asian regions. Cable degradation or disruption would manifest as increased inter-region latency before the more visible effects of power cost increases or physical security threats.

IRGC Capability Assessment: Can They Actually Cut Cables?

The IRGC has demonstrated underwater operations capability. Iran operates midget submarines (Ghadir-class) capable of operating in Gulf of Oman depths. The IRGC Navy has combat swimmer units. And critically, Iran already knows exactly where the cables are — the Jask cable landing station has detailed charts of cable routes in adjacent waters as part of its operational documentation.

A cable cut does not require a submarine. The simplest method is a surface vessel dragging a grapple anchor over a known cable route — the same mechanism responsible for most commercial cable faults globally. In contested waters where no ASN repair vessel will respond, a grapple-drag cable fault and an intentional cable cut produce the same operational effect.

The Tasnim article calling this a "fatal weakness" is accurate in a specific sense: cable infrastructure cannot be hardened the way surface infrastructure can. You cannot put air defense over a cable route. The only mitigation is geographic redundancy — and the Red Sea damage means the geographic redundancy that normally absorbs Persian Gulf faults is already degraded.

Developer and Infrastructure Implications

For teams operating in or routing through Gulf cloud regions:

Immediate: Alcatel force majeure for Persian Gulf means any cable fault that occurs now goes unrepaired. Test your Gulf region failover paths — specifically latency from ME regions to EU-West and AP-Southeast via non-Gulf routes.

Connectivity monitoring: Set up synthetic monitoring from Gulf cloud regions to your primary application targets. Baseline latency now so cable degradation shows as deviation from baseline, not ambiguous slowdown.

Traffic engineering: If your application serves Gulf state users and you have multi-region presence, shift DNS weights away from ME-South/UAE-North preemptively. A 50/50 split now is better than emergency traffic shifting during a cable fault.

CDN and edge: Gulf PoPs for Cloudflare, Fastly, and Akamai all rely on the same cable infrastructure. A Persian Gulf cable disruption affects CDN performance for Gulf-state users even if your origin is in EU-West.

Key Takeaways

  • Tasnim (IRGC-linked) called undersea cables Iran's "fatal weakness" and warned of "digital catastrophe" on April 22, 2026 — this is IRGC deterrence signaling to the US, not a vulnerability disclosure for Iran's benefit
  • Alcatel Submarine Networks issued force majeure for Persian Gulf operations — no cable repair vessels will enter the conflict zone; any cable fault that occurs now goes unrepaired indefinitely
  • At-risk cables: AAE-1, SEA-ME-WE 5/6, FALCON, GBI, 2Africa — all converge near Jask/Gulf of Oman approach to Hormuz where IRGC underwater capability is highest
  • Dual chokepoint risk is real: Red Sea cables (AAE-1, SEACOM, EIG) already cut and partially unrepaired from 2023-2024 Houthi operations; Persian Gulf cables now under active IRGC threat; geographic redundancy between Asia and Europe is already degraded
  • Gulf cloud infrastructure latency risk: AWS ME-South, Azure UAE North, Google Cloud ME Central all route through Gulf of Oman cables; cable degradation shows as inter-region latency spike before physical infrastructure effects
  • Developer action: baseline ME region latency now, shift DNS weights preemptively, enable CDN failover, test Gulf-region-to-Europe paths via non-Gulf routes

For the IRGC ship seizure context, read IRGC Seizes Two Ships in Hormuz Hours After Trump Extends Ceasefire. For the dual chokepoint analysis with Red Sea context, read Red Sea and Hormuz Both Closed: What Losing Two Internet Chokepoints Means. For Gulf cloud infrastructure risk, read Iran Declares AWS, Google, and Microsoft Data Centers Military Targets.

FAQ

Frequently Asked Questions

Did Iran threaten to cut undersea internet cables in April 2026?

Tasnim News Agency, which has direct IRGC backing, published a piece on April 22, 2026 calling undersea cables Iran's "fatal weakness" and warning of a potential "digital catastrophe" if the conflict escalates. The framing is IRGC deterrence signaling — Iran demonstrating awareness of cable routes and capability to disrupt them — rather than an official government declaration. Alcatel Submarine Networks issued force majeure notices for Persian Gulf operations the same day, suspending cable maintenance in the conflict zone.

Which undersea cables could Iran cut in the Strait of Hormuz area?

The major cables at risk in the Persian Gulf and Gulf of Oman include AAE-1 (Asia-Africa-Europe 1, 25,000km), SEA-ME-WE 5 and SEA-ME-WE 6 (Southeast Asia to Europe), FALCON (Gulf states interconnect), Gulf Bridge International (GBI), and 2Africa. These cables converge near the Jask area on Iran's Gulf of Oman coast, where Iran operates the Jask cable landing station and has detailed knowledge of cable routes. The IRGC Navy operates midget submarines (Ghadir-class) and has combat swimmer units capable of cable interdiction in these waters.

What does Alcatel Submarine Networks force majeure mean for Persian Gulf cables?

Alcatel Submarine Networks (owned by Nokia) is the primary company that lays and repairs undersea cables globally. A force majeure declaration for Persian Gulf operations means ASN will not send repair vessels into the conflict zone. Any cable fault that occurs during this period — whether from anchor drag, seabed movement, or deliberate cut — goes unrepaired indefinitely. The Red Sea precedent: when Houthi activity cut three cables in 2023-2024, force majeure was declared and cables remained unrepaired for months, rerouting traffic around Africa with 100-150ms additional latency. A Persian Gulf scenario would produce similar effects for Gulf-state terminating traffic, with no equivalent reroute option.

What happens to internet connectivity if both Red Sea and Persian Gulf cables are disrupted?

Red Sea and Persian Gulf cables are the two chokepoints for internet connectivity between Asia and Europe. Red Sea cables (AAE-1, SEACOM, EIG) were already cut in 2023-2024 and remain at degraded capacity — traffic reroutes around Africa adding 100-150ms latency. If Persian Gulf cables are also disrupted, Gulf states (UAE, Saudi Arabia, Kuwait, Qatar) face direct connectivity degradation with no equivalent reroute option. Cloud infrastructure in Gulf regions (AWS ME-South, Azure UAE North, Google Cloud ME Central) would see increased inter-region latency to EU and AP regions, affecting LLM inference, real-time APIs, and CDN edge performance for Middle East users.

Free Weekly Briefing

The AI & Dev Briefing

One honest email a week — what actually matters in AI and software engineering. No noise, no sponsored content. Read by developers across 30+ countries.

No spam. Unsubscribe anytime.

Free Tool

Will AI replace your job?

4 questions. Get a personalised developer risk score based on your stack, role, and what you actually build day to day.

Check Your AI Risk Score →

Written by

Software Engineer based in Delhi, India. Writes about AI models, semiconductor supply chains, and tech geopolitics — covering the intersection of infrastructure and global events. 839+ posts cited by ChatGPT, Perplexity, and Gemini. Read in 164 countries.