---
date: 2026-09-02
issue: 40
title: Four Subsea Cable Faults Cause Connectivity Outages in Vietnam
standfirst: Multiple cable systems are experiencing faults simultaneously, impacting
  national connectivity. The specific systems affected and the status of repairs remain
  unconfirmed.
jurisdictions:
- VN
- IE
- US
- INT
- BR
- AU
tags: []
vertical: cablewatch
---

## Executive summary

- Vietnam is experiencing fresh connectivity outages following reported faults on four of its subsea cables, though DCD has not disclosed the specific systems, landing points, or repair timelines [1].
- An Coimisiún Pleanála has granted planning approval for the Fastnet subsea cable landing station in West Cork, Ireland, which will support AWS's first wholly owned private transatlantic cable connecting County Cork with Maryland [2].
- The Maritime Executive describes the acquisition of Wilson Sons Ultratug and Atlantic Offshore Services by Tidewater, alongside the merger of Helix Energy Solutions and Hornbeck Offshore Services, as a wave of offshore consolidation to integrate specialty vessel capabilities [3].
- Taiwan is considering the adoption of satellite communications as a backup to improve infrastructure resilience, as policymakers and experts note that subsea cables currently account for more than 90% of the island's external communications [4].

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].

## AWS Fastnet Landing Station Approval

Amazon Web Services (AWS) has received planning approval from An Coimisiún Pleanála for the Fastnet subsea cable landing station in West Cork, Ireland [2]. The project, which includes a station at Tullyneasky West, will establish AWS's first wholly owned private transatlantic cable connecting County Cork with Maryland in the United States [2]. The system is targeted for service in 2028 with a capacity exceeding 320Tbps, though AWS still requires a Maritime Area Consent to occupy the seabed [2].

## Offshore Consolidation and Satellite Redundancy

Tidewater completed the acquisition of Wilson Sons Ultratug and Atlantic Offshore Services for $500 million on August 31, adding 22 PSVs to its fleet and bringing its total OSV count to 213 [3]. Simultaneously, Helix Energy Solutions merged with Hornbeck Offshore Services to form a rebranded entity as of September 1 [3]. These transactions are described by The Maritime Executive as a wave of offshore consolidation intended to integrate specialty vessel capabilities across the energy, defense, and renewables sectors [3].

In a separate policy shift, Taiwan is considering the adoption of satellite communications to reduce its reliance on subsea cables, which currently account for more than 90% of the island's external communications [4]. Policymakers and experts are advocating for these satellite systems to be brought onshore as a backup to improve infrastructure resilience against potential disruptions to the subsea cable network [4].

## References

1. [Four of Vietnam's subsea cables suffer faults, leading to fresh connectivity outages for country](https://www.datacenterdynamics.com/en/news/four-of-vietnams-subsea-cables-suffer-faults-leading-to-fresh-connectivity-outages-for-country/) (DCD, subsea)
   datacenterdynamics.com
2. [AWS Wins Final Fastnet Landing Station Approval](https://subtelforum.com/aws-wins-final-fastnet-landing-station-approval/) (Submarine Telecoms Forum)
   subtelforum.com
3. [Offshore Consolidation Continues as Both Tidewater and Helix Close Deals](https://maritime-executive.com/article/offshore-consolidation-continues-as-both-tidewater-and-helix-close-deals) (The Maritime Executive)
   Published: 01 Sep 2026 · maritime-executive.com · Claim type: official_statement · Subject: policy · Jurisdictions: INT, BR, AU
4. [Taiwan eyes satellite communications to cut sea cable reliance](https://www.digitimes.com/news/a20260901PD204/taiwan-satellite-communications-communications-cables-leo.html) (digitimes.com)
   digitimes.com

---

## Standing status

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

- **AusInternet — network status** — **INDIGO Central, INDIGO West**  
  Status: partial service disruption; Fault: shunt fault; Fault location: 65km from Perth Cable Landing Station; Repair ETA: 26 Aug 2026 / 30 Aug 2026 with an ETR on 4 Sep 2026; Delayed until: August 25th / 2nd of October; Repair vessel: repairing the Shunt Fault off Perth betwee; Planned maintenance: NBN POI 2MYF (Mayfield) - Permanent cable repair Planned Maintenance / September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9  
  <sub>as at 2026-09-01 20:11 UTC · https://ausinternet.com.au/status/</sub>
- **Global Secure Layer — network status**  
  Status: partial outage  
  <sub>as at 2026-08-27 11:08 UTC · https://status.gslnetworks.com.au</sub>
- **SUBCO — INDIGO West** — **INDIGO West**  
  <sub>as at 2026-08-19 04:36 UTC · https://sub.co/indigo-west/</sub>
- **SUBCO** — **Oman Australia Cable, INDIGO Central, INDIGO West, SMAP**  
  Status: monitoring  
  <sub>as at 2026-09-02 17:12 UTC · https://sub.co</sub>
- **Telstra — service status**  
  Status: monitoring  
  <sub>as at 2026-09-02 01:36 UTC · https://www.telstra.com.au/exchange</sub>
- **Vocus — network status**  
  Status: operational; Affected system: drum  
  <sub>as at 2026-08-31 01:33 UTC · https://www.vocus.com.au</sub>

<sub>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.</sub>

**Changes in the last 7 days:**

- `2026-09-01 20:11` AusInternet — network status — Planned maintenance: Data Centres → **NBN POI 2MYF (Mayfield) - Permanent cable repair Planned Maintenance**
- `2026-09-01 20:11` AusInternet — network status — Planned maintenance: NBN POI 2MYF (Mayfield) - Permanent cable repair Planned Maintenance → **September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9**
- `2026-09-01 20:11` AusInternet — network status — Planned maintenance: September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9 → **September 7, 2026 11:00PM - 6:00AM AEST September 7, 2026 1:00PM - 8**
- `2026-09-01 20:11` AusInternet — network status — Planned maintenance: September 7, 2026 11:00PM - 6:00AM AEST September 7, 2026 1:00PM - 8 → **September 8, 2026 12:00AM - 2:00AM AEST September 7, 2026 2:00PM - 4**
- `2026-09-01 20:11` AusInternet — network status — Planned maintenance: September 8, 2026 12:00AM - 2:00AM AEST September 7, 2026 2:00PM - 4 → **September 9, 2026 12:00AM - 2:00AM AEST September 8, 2026 2:00PM - 4**
- `2026-09-01 13:12` AusInternet — network status — Planned maintenance: NBN POI 2CAM (Campsie), 2PTH (Penrith), 2GBE (Glebe), 2MIR (Miranda → **Data Centres**
- `2026-09-01 13:12` AusInternet — network status — Planned maintenance: September 1, 2026 11:00PM - 6:00AM AEST September 1, 2026 1:00PM - 8 → **NBN POI 2MYF (Mayfield) - Permanent cable repair Planned Maintenance**
- `2026-09-01 13:12` AusInternet — network status — Planned maintenance: September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9 → **September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9**
- `2026-09-01 13:12` AusInternet — network status — Planned maintenance: September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9 → **September 7, 2026 11:00PM - 6:00AM AEST September 7, 2026 1:00PM - 8**
- `2026-09-01 13:12` AusInternet — network status — Planned maintenance: September 7, 2026 11:00PM - 6:00AM AEST September 7, 2026 1:00PM - 8 → **September 8, 2026 12:00AM - 2:00AM AEST September 7, 2026 2:00PM - 4**
- `2026-09-01 01:14` AusInternet — network status — Planned maintenance: September 3, 2026 11:00PM - 6:00AM AEST September 3, 2026 1:00PM - 8 → **September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9**
- `2026-09-01 01:14` AusInternet — network status — Planned maintenance: September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9 → **September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9**
- `2026-09-01 01:14` AusInternet — network status — Planned maintenance: September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9 → **September 7, 2026 11:00PM - 6:00AM AEST September 7, 2026 1:00PM - 8**
- `2026-08-31 20:13` AusInternet — network status — Planned maintenance: Data Centres → **NBN POI 2CAM (Campsie), 2PTH (Penrith), 2GBE (Glebe), 2MIR (Miranda**
- `2026-08-31 20:13` AusInternet — network status — Planned maintenance: NBN POI 2CAM (Campsie), 2PTH (Penrith), 2GBE (Glebe), 2MIR (Miranda → **September 1, 2026 11:00PM - 6:00AM AEST September 1, 2026 1:00PM - 8**
- `2026-08-31 20:13` AusInternet — network status — Planned maintenance: September 1, 2026 11:00PM - 6:00AM AEST September 1, 2026 1:00PM - 8 → **September 3, 2026 11:00PM - 6:00AM AEST September 3, 2026 1:00PM - 8**
- `2026-08-31 20:13` AusInternet — network status — Planned maintenance: September 3, 2026 11:00PM - 6:00AM AEST September 3, 2026 1:00PM - 8 → **September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9**
- `2026-08-31 20:13` AusInternet — network status — Planned maintenance: September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9 → **September 7, 2026 10:00PM - 7:00AM AEST September 7, 2026 12:00PM - 9**
- `2026-08-31 14:14` AusInternet — network status — Planned maintenance: September 1, 2026 11:00PM - 6:00AM AEST September 1, 2026 1:00PM - 8 → **NBN POI 2CAM (Campsie), 2PTH (Penrith), 2GBE (Glebe), 2MIR (Miranda**
- `2026-08-31 14:14` AusInternet — network status — Planned maintenance: September 7, 2026 12:00AM - 7:00AM AEST September 6, 2026 2:00PM - 9 → **September 3, 2026 11:00PM - 6:00AM AEST September 3, 2026 1:00PM - 8**

**Incident threads:**

- `other` — 56 documents, last 2026-09-01 (quiet 2d)
- `perth_indigo_2026_08` (INDIGO West, INDIGO Central) — 10 documents, last 2026-08-27 (quiet 7d)

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

- **perth to singapore** — ocean crossing 46.2ms; queuing 0.7ms; end to end floor 197.8ms, steady against its 13 day baseline; clean crossing (21 probe(s), 63 reading(s) excluded as below the corridor's physical floor)
- **sydney to japan** — ocean crossing 127.1ms; queuing 0.5ms; end to end floor 141.3ms, steady against its 13 day baseline; clean crossing (18 probe(s))
- **sydney to nz** — ocean crossing 27.7ms; queuing 0.2ms; end to end floor 34.4ms, steady against its 13 day baseline; clean crossing (8 probe(s))
- **sydney to singapore** — ocean crossing 116.2ms; queuing 0.6ms; end to end floor **172.2ms, +25.5ms against its 13 day baseline**; 2 intervening hop(s) included (22 probe(s))

<sub>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`.</sub>

**Vessel review queue:**

- `perth_cpz_2026_08` (INDIGO West, INDIGO Central) — 1 candidate(s), top review priority 0.33

<sub>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.</sub>

<sub>Collection: 453 successful fetches in 24h, 46 errors across 13 source(s). Generated 2026-09-02 18:58 UTC.</sub>
