← Cable Watch

1 September 2026 · Issue 39

Four Subsea Cable Faults Cause Connectivity Outages in Vietnam

Multiple cable systems are experiencing faults simultaneously, impacting national connectivity. The specific systems affected and the status of repairs remain unconfirmed.

Markdown · Subscribe

Executive summary

Vietnam is experiencing fresh connectivity outages following reported faults on four of its subsea cables [1]. DCD reported the incidents, though the specific cable systems, landing points, and repair timelines have not been disclosed [1].

International Infrastructure Integrity and Licensing

The Dutch survey specialist Deep has secured a four-year contract from TenneT to conduct annual integrity surveys of TenneT offshore cable infrastructure between 2026 and 2029 [2]. These surveys will utilize hydrographic and geophysical methods to measure cable burial and identify seabed threats, with visual inspections conducted as needed to support TenneT's North Sea offshore grid expansion [2]. In the United States, the FCC reached a settlement with a submarine cable company and three co-licensees, who agreed to split a $45,000 fine for failing to renew landing licenses on time [3]. While these events occur outside the Indo-Pacific, they highlight the ongoing regulatory and maintenance requirements for maintaining subsea infrastructure integrity and legal compliance [2, 3].

References

  1. Four of Vietnam's subsea cables suffer faults, leading to fresh connectivity outages for country (DCD, subsea)
    datacenterdynamics.com
  2. Deep wins four-year TenneT offshore cable survey deal (Splash 247)
    splash247.com
  3. FCC Fines Undersea Cable Cos. For Expired Landing Licenses - Law360 UK (law360.com)
    law360.com

Standing status

Operator-reported state (read directly from each operator's own status page, not summarised by any model):

Cable systems shown are those named anywhere on the captured page, matched against the systems tracked in geofences.yaml. A named system is not by itself a claim that it is the affected one.

Changes in the last 7 days:

Incident threads:

Measured path state (RIPE Atlas traceroute, median across probes over 24h, no model involved):

A corridor is a city pair, not a cable. Several systems serve each of these routes and IP routing does not reveal which one carries a packet, so a healthy corridor is not evidence that any particular cable is intact: traffic reroutes onto a survivor within seconds of a fault. Per-probe detail is in cablewatch segments.

Vessel review queue:

Review priority is a heuristic score from this repo ordering which tracks a human should look at. It is not evidence, and it implies nothing about any vessel.

Collection: 454 successful fetches in 24h, 45 errors across 10 source(s). Generated 2026-09-01 21:43 UTC.