---
date: 2026-10-11
issue: 79
title: Geological Events and Vessel Scarcity Threaten Subsea Cable Redundancy
standfirst: A recent analysis highlights how geographic proximity can create correlated
  failures across multiple cable systems. The report warns that a shortage of dedicated
  repair vessels is significantly extending restoration timelines.
jurisdictions:
- SN
- CI
- NG
- TW
- INT
- IE
tags: []
vertical: cablewatch
---

## Situation

- **INDIGO West**: open since 8 Aug, 64 days, per AusInternet. Operator status: Partial Service Disruption.  
  Latest update, 7 Oct 12:07 UTC (4 days ago): “Shunt Fault Repairs have been delayed to; Start Time: Oct 25, 2026 01:00 UTC End Time: Nov 3, 2026 23:59 UTC”
- **Australia Singapore Cable**: open since 4 Sep, 37 days, per Global Secure Layer. Operator status: Update.  
  Latest update, 7 Oct 08:12 UTC (4 days ago): “SUBCO has advised Indigo West's repair has been rescheduled to October 25th - November 3rd.”
- **Australia Singapore Cable**: first update on the page 23 Sep, per Vocus.  
  Latest update, 25 Sep 07:45 UTC (16 days ago): “Vocus continues to progress restoration and repair activities following the Australia Singapore Cable (ASC) fault. Layer 2 Ethernet services restored via the Perth to Singapore path through Jakarta remain operational, and Internet traffic continues to be managed across alternate paths where this delivers the best customer experience. Traffic originating from Perth on ASC towards Port Hedland, Christmas Island and Anyer, Indonesia remains stable and operational. …”
- **INDIGO West**: notice posted by Superloop, first seen 9 Oct (2 days ago); the notice carries no date of its own.  
  Notice: “We are currently experiencing a service disruption affecting the Indigo West link due to instability. Our team is actively investigating and working to resolve the issue. Updates will be provided as more information becomes available. Support remains available via phone and email during this time. Next Update :12-10-2026 11:00 AEDT (12-10-2026 00:00 UTC), or earlier should there be any significant developments.”
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 10 Oct 19:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 10 Oct 19:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 10 Oct 20:00 UTC — 5 of 9 paths stepped, median +43.3ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 10 Oct 20:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 10 Oct 21:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 10 Oct 21:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 10 Oct 22:00 UTC — 5 of 9 paths stepped, median +43.2ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 10 Oct 22:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 10 Oct 23:00 UTC — 5 of 9 paths stepped, median +43.2ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 10 Oct 23:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 01:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 01:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 02:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 02:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 04:00 UTC — 5 of 9 paths stepped, median +43.3ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 04:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 05:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 05:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 06:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 06:00 UTC — 5 of 9 paths stepped, median +43.2ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 07:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 07:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 08:00 UTC — 5 of 9 paths stepped, median +43.2ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 08:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 09:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 09:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 10:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 10:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 11:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 11:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 12:00 UTC — 5 of 9 paths stepped, median +43.3ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 12:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 13:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 13:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 14:00 UTC — 5 of 9 paths stepped, median +43.2ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 14:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 15:00 UTC — 5 of 9 paths stepped, median +43.0ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 15:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [GROUP_STEP] at 11 Oct 16:00 UTC — 5 of 9 paths stepped, median +43.1ms against each path's own floor. 3 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured route**: Sydney to Noumea [RECOVERY] at 11 Oct 16:00 UTC — GROUP_STEP has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Gondwana-1 (TeleGeography).
- **Measured latency** (RIPE Atlas, best measured path over 24 hours against each route's best sustained floor over 51 days): Perth to Singapore 191.6ms, up 145.0ms on its 46.6ms floor; Sydney to Japan 100.0ms, up 43.8ms on its 100.1ms floor; Sydney to Singapore 144.4ms, up 47.9ms on its 96.5ms floor.
- **Elsewhere**: Cloudflare Radar lists no outage with a cable cut as its cause, open or ended in the last 3 days, anywhere in the world.

<sub>No model writes this section. Operator updates are quoted from each operator's own status page and dated as the operator dated them. No operator has posted an update or a new notice on these since the last brief (10 Oct 18:09 UTC). Lines marked Elsewhere are Cloudflare Radar's own outage annotations, from anywhere in the world, with the cause as Radar labels it; this archive attributes nothing to anyone. Latency is measured between cities, not on any named cable: several systems serve each route and traffic moves to a survivor within seconds of a fault. Detail is in Standing status at the end of the brief.</sub>

## Today

A post on dev.to highlights how a March 2024 geological event off Côte d'Ivoire simultaneously damaged the WACS, MainOne, SAT-3, and ACE subsea cables, demonstrating how physical proximity can undermine logical redundancy [1]. The author notes that repair times have doubled since 2012 due to a scarcity of dedicated vessels like the Léon Thévenin and CS Sovereign, which must manage serialized repairs in regions such as Africa [1].

## Geopolitical Tensions and Infrastructure Vulnerability

A post on irishexaminer.com notes that while 70% to 80% of the 150 to 200 annual global cable faults are accidental, recent geopolitical tensions have increased concerns regarding deliberate sabotage [2]. In response, Ireland has published a National Maritime Security Strategy (2026-2030) and established a framework with Britain to coordinate responses to major subsea incidents [2]. 

A post on heraldscotland.com reports that military leaders and experts gathered in Edinburgh to assess threats of large-scale conflict by 2030, specifically highlighting Russia's 'hybrid war' and increased naval activity in UK waters [3]. The meeting emphasized that Scotland's subsea cables are vulnerable to sabotage, drawing parallels to recent incidents in the Baltic and off Norway [3].

## Seabed Warfare and Strategic Infrastructure

The U.S. Navy is transitioning to a comprehensive Undersea Warfare (USW) strategy that prioritizes Integrated Undersea Dominance (IUD) and Distributed Maritime Operations (DMO) to counter mines, uncrewed underwater vehicles (UUVs), and covert seabed operations [7]. This shift aims to maintain a persistent presence in contested environments where China and Russia are expanding undersea capabilities, moving away from a purely submarine-centric focus to a networked ecosystem of manned and autonomous systems [7].

In the Indo-Pacific, the Batanes Islands have emerged as a strategic geographic bridge for Taiwan-contingency planning due to their position overlooking the Bashi Channel, a critical corridor for submarine cables and commercial shipping [5]. Meanwhile, analyst Sam Lair assessed the Kola Peninsula's Olenya Guba as a primary hub for the Russian Main Directorate for Deep Sea-Research (GUGI), noting that GUGI vessels and special-mission submarines have been tracked near critical undersea cables and pipelines in British waters [6]. U.S. reports suggest these vessels may have used a secret weapon to disable cables without leaving fingerprints, highlighting a long-standing Russian priority on seabed warfare [6].

## References

1. [The Ship in Your Dependency Graph - DEV Community](https://dev.to/sonia_bobrik_1939cdddd79d/the-ship-in-your-dependency-graph-kj) (dev.to)
   Published: 10 Oct 2026 · dev.to · Publisher: self-published, not an official or analyst source · Claim type: analyst_assessment · Subject: fault, repair, analysis, precedent · Systems named: WACS, MainOne, SAT-3, ACE, Seacom, EASSy · Vessels named: Léon Thévenin, CS Sovereign · Jurisdictions: SN, CI, NG, TW, INT
2. [The cables beneath the sea carry our digital lives. What happens when something goes wrong?](https://irishexaminer.com/news/spotlight/arid-41921431.html) (irishexaminer.com)
   Published: 10 Oct 2026 · irishexaminer.com · Claim type: analyst_assessment · Subject: analysis, policy, seabed_security · Systems named: TAT-1 · Vessels named: Monarch · Jurisdictions: IE, GB, CA, US, RU
3. [Inside the security gathering as Scotland prepares for war](https://www.heraldscotland.com/news/26624623.inside-security-gathering-scotland-prepares-war/) (heraldscotland.com)
   heraldscotland.com
4. [Subsea Daily News#17](https://note.com/fine_alpaca6065/n/nc2e2151464ef?hl=en) (note.com)
   Published: 07 Oct 2026 · note.com · Publisher: self-published, not an official or analyst source · Claim type: confirmed_fact (the claim it relays, not the publisher) · Subject: fault, vessel_activity, analysis · Systems named: C2C Singapore-Hong Kong · Vessels named: Normand Maximus · Jurisdictions: PH, SG, HK, INT
5. [Why the Batanes Islands Matter to Taiwan and the US](https://www.riotimesonline.com/batanes-bashi-channel-taiwan-philippines-2026/) (riotimesonline.com)
   riotimesonline.com
6. [House Of GUGI: A Historical Imagery Analysis Of Olenya Guba](https://www.eurasiareview.com/11102026-house-of-gugi-a-historical-imagery-analysis-of-olenya-guba/) (eurasiareview.com)
   eurasiareview.com
7. [Undersea Warfare Beyond Submarines: US Navy's New Strategy | List25](https://list25.com/undersea-warfare-beyond-submarines) (list25.com)
   Published: 10 Oct 2026 · list25.com · Claim type: analyst_assessment · Subject: seabed_security, analysis · Jurisdictions: INT

---

## Standing status

**Operator incident timelines** (quoted from each operator's own status page, not summarised by any model):

- **INDIGO West** · AusInternet — network status · Partial Service Disruption, open since 8 Aug
  - `7 Oct 12:07 UTC` Identified: Shunt Fault Repairs have been delayed to; Start Time: Oct 25, 2026 01:00 UTC End Time: Nov 3, 2026 23:59 UTC
  <sub>page last checked 2026-10-11 18:11 UTC · https://ausinternet.com.au/status/</sub>
- **Australia Singapore Cable** · Global Secure Layer — network status · Update, open since 4 Sep
  - `7 Oct 08:12 UTC` Update: SUBCO has advised Indigo West's repair has been rescheduled to October 25th - November 3rd.
  - `7 Oct 04:54 UTC` Update: Repairs on Indigo West are scheduled for between the 16-26th of October. ASC is scheduled shortly after on the 4th of November. GSL will continue to route traffic on the best alternative paths to Singapore. Please note these timelines are subject to weather conditions, permits and condition of cables.
  <sub>page last checked 2026-10-11 18:12 UTC · https://status.gslnetworks.com.au/incidents/wqmz5wt7l8qj</sub>
- **Australia Singapore Cable** · Vocus — ASC repair update · first update on the page 23 Sep
  - `25 Sep 07:45 UTC` Update: Vocus continues to progress restoration and repair activities following the Australia Singapore Cable (ASC) fault. Layer 2 Ethernet services restored via the Perth to Singapore path through Jakarta remain operational, and Internet traffic continues to be managed across alternate paths where this delivers the best customer experience. Traffic originating from Perth on ASC towards Port Hedland, Christmas Island and Anyer, Indonesia remains stable and operational. Temporary restoration measures remain in place for affected services between Australia and Singapore. We continue to work with partners in Jakarta to manage intermittent instability associated with third-party network infrastructure. The new 100G path between Japan and Guam is in service, providing additional capacity to support Internet traffic into Asia and Europe and reducing reliance on longer alternate paths. This additional capacity further strengthens the temporary restoration arrangements in place while the permanent ASC repair progresses. Testing completed from the Perth and Singapore landing stations continues to indicate a cable break within Indonesian waters, approximately 615 km from the Singapore landing station. Restoring services remains our highest priority, and Vocus continues to work closely with our marine repair partner and relevant authorities to progress the repair program. As previously noted, Vocus agreed to sequence the repair of Indigo West ahead of ASC to provide the best overall restoration outcome for customers. Repairing ASC requires the affected section of the system to be powered down, which would temporarily remove capacity currently supporting restored services via Jakarta and place additional demand on alternate Internet paths. Restoring Indigo West first provides an additional diverse path between Australia and Asia, allowing affected customer services and Internet traffic to be rerouted before ASC is taken offline for its permanent repair. Planning for the marine repair operation continues. The repair vessel will depart Singapore on 11 October, and the Indigo West repair is expected to be completed around 24 October. The vessel is then expected to transit to the ASC repair location, with marine repair activities for ASC planned to start around 25 October. Based on the current repair schedule, completion of the ASC repair remains targeted for 4 November. Additional contingency has been incorporated into the marine program should conditions affect the planned repair activities. A key dependency of the repair remains completion of the required Indonesian operational permits and clearances. Documentation and approval activities are progressing with the relevant authorities and are part of the pre-repair program. Subsea cable repairs are complex and remain subject to a number of factors outside Vocus' direct control. The current schedule is dependent on permitting and regulatory approvals, completion of the preceding Indigo West repair, vessel movements, local sea and weather conditions, and the condition of the cable once recovered. While every effort will be made to complete the work within the planned timeframe, these dates may change if operational conditions require. Vocus will continue to closely monitor temporary restoration paths and available international capacity while the marine repair program progresses, and will provide further updates as key milestones are reached.
  <sub>page last checked 2026-10-11 13:23 UTC · https://www.vocus.com.au/news/update-on-repairs-to-australia-singapore-cable</sub>
- **INDIGO West** · Superloop — outages · active notice, first seen 9 Oct 16:08 UTC (the page gives no date)
  - We are currently experiencing a service disruption affecting the Indigo West link due to instability. Our team is actively investigating and working to resolve the issue. Updates will be provided as more information becomes available. Support remains available via phone and email during this time. Next Update :12-10-2026 11:00 AEDT (12-10-2026 00:00 UTC), or earlier should there be any significant developments.
  <sub>page last checked 2026-10-11 18:11 UTC · https://www.superloop.com/outages/</sub>

<sub>1 other open incident(s) on those pages name no tracked cable system and are not shown.</sub>

<sub>Also polled for changes, but carrying no incident listing, so nothing is said about their state: ACMA protection zone — Perth, ACMA protection zone — Sydney, AJC — cable system maintenance, AJC — news, SUBCO, SUBCO — INDIGO West, SUBCO — OAC, Southern Cross Cable Network, Telstra — service status, Vocus — network status.</sub>

**Incident threads:**

- `perth_indigo_2026_08` (INDIGO West, INDIGO Central) — 14 documents, last 2026-09-26 (quiet 16d)

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

- **perth to singapore** — best path **191.6ms, +145.0ms on its best sustained 46.6ms**; typical path 275.6ms (+72.3ms per probe against its own history, 21 probes); ocean crossing 150.9ms; queuing 0.5ms; 51 days of history; clean crossing (21 probe(s), 65 reading(s) excluded as below the corridor's physical floor)
- **sydney to japan** — best path 100.0ms; typical path 181.9ms (+43.8ms per probe against its own history, 18 probes); ocean crossing 134.2ms; queuing 0.5ms; 51 days of history; clean crossing (18 probe(s))
- **sydney to nz** — best path 26.7ms; typical path 34.5ms (+0.1ms per probe against its own history, 8 probes); ocean crossing 27.8ms; queuing 0.2ms; steady against 51 days of history; clean crossing (8 probe(s))
- **sydney to singapore** — best path **144.4ms, +47.9ms on its best sustained 96.5ms**; typical path 223.2ms (+43.9ms per probe against its own history, 22 probes); ocean crossing 172.0ms; queuing 0.5ms; 51 days of history; clean crossing (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>

**Every cable route leaving the mainland** (measured hourly, no model involved):

- **Australia to Guam** — best 70.6ms against a 52.0ms floor; 13/24 paths direct (normally 13) <br><sub>Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S), PIPE Pacific Cable-1 (PPC-1)</sub>
- **Dili to Australia** — best 49.3ms against a 7.1ms floor; 3 paths measured <br><sub>Timor-Leste South Submarine Cable (TLSSC), North-West Cable System</sub>
- **Melbourne to Tasmania** — best 10.0ms against a 5.9ms floor; 8/17 paths direct (normally 8) <br><sub>Basslink, Bass Strait-1, Bass Strait-2</sub>
- **Perth to Jakarta** — best 61.8ms against a 29.5ms floor; 46 paths measured <br><sub>INDIGO-West, Australia-Singapore Cable (ASC)</sub>
- **Perth to Oman** — best 111.0ms against a 85.0ms floor; 2/4 paths direct (normally 2) <br><sub>Oman Australia Cable (OAC) · only system on this route</sub>
- **Perth to Singapore** — best 50.6ms against a 38.3ms floor; 11/67 paths direct (normally 11) <br><sub>INDIGO-West, Australia-Singapore Cable (ASC), Darwin-Jakarta-Singapore Cable (DJSC)</sub>
- **Sydney to Fiji** — best 37.0ms against a 31.5ms floor; 6/6 paths direct (normally 6) <br><sub>Southern Cross Cable Network (SCCN), Southern Cross NEXT</sub>
- **Sydney to Hawaii** — best 189.3ms against a 80.0ms floor; 2 paths measured <br><sub>Telstra Endeavour, Southern Cross Cable Network (SCCN), Hawaiki</sub>
- **Sydney to Honiara** — best 38.3ms against a 28.0ms floor; 2/2 paths direct (normally 2) <br><sub>Coral Sea Cable System (CS²) · only system on this route</sub>
- **Sydney to Japan** — best 99.0ms against a 76.7ms floor; 25/106 paths direct (normally 24) <br><sub>Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S)</sub>
- **Sydney to New Zealand** — best 23.5ms against a 21.1ms floor; 46/65 paths direct (normally 50) <br><sub>Southern Cross Cable Network (SCCN), Southern Cross NEXT, Hawaiki, Tasman Global Access (TGA) Cable</sub>
- **Sydney to Noumea** — best 22.3ms against a 19.3ms floor; 4/9 paths direct (normally 6) <br><sub>Gondwana-1 · only system on this route</sub>
- **Sydney to Port Moresby** — best 37.7ms against a 26.9ms floor; 3/6 paths direct (normally 3) <br><sub>Coral Sea Cable System (CS²), PIPE Pacific Cable-1 (PPC-1)</sub>
- **Sydney to US West Coast** — best 133.7ms against a 118.3ms floor; 282/302 paths direct (normally 283) <br><sub>Southern Cross Cable Network (SCCN), Southern Cross NEXT, Hawaiki, Telstra Endeavour</sub>

<sub>A route is a pair of places, not a cable: several systems serve most of these and IP routing does not reveal which one carried a packet, so a healthy route is not evidence that every cable on it is intact. A path counts as direct when it is within reach of the physical floor between the two places. Routes with no vantage at the far end are listed in latency_watch.yaml under `uncovered`.</sub>

**Cloudflare Radar outages attributed to a cable cut in the last 7 days:**

- `2026-10-03` HT — NETWORK — Fiber optic cable damage on Route Nationale #1 caused a complete loss of Internet traffic from Digicel (AS27653), Haiti's largest mobile operator.

<sub>Cause is Cloudflare Radar's own classification of its own observation, reproduced as they state it. It is not this archive's finding and it attributes nothing to anyone.</sub>

<sub>Collection: 564 successful fetches in 24h, 44 errors across 26 source(s). Generated 2026-10-11 18:13 UTC.</sub>
