---
date: 2026-09-21
issue: 59
title: Vocus Sets November 4 Completion Date for Australia Singapore Cable Repairs
standfirst: The operator expects to finalize permanent repairs to the ASC following
  the restoration of the Indigo West system. Services between Australia and Singapore
  remain impacted, though specific Layer 2 Ethernet routes remain operational.
jurisdictions:
- AU
- SG
- INT
- ES
- AR
- UY
tags: []
vertical: cablewatch
---

## Situation

- **INDIGO West**: open since 8 Aug, 44 days, per AusInternet. Operator status: Partial Service Disruption.  
  **New update**, 21 Sep 05:49 UTC (today): “Scheduled to repair the fault on Indigo West off the coast of Perth has completed. Unfortunately the existing shunt fault on Indigo West in Singapore has deteriorated into a full cable break and services remain down. Repairs off Singapore is expected to be on 16 Oct 2026 until 26 Oct 2026.”
- **Australia Singapore Cable**: open since 4 Sep, 17 days, per Global Secure Layer. Operator status: Identified.  
  Latest update, 4 Sep 06:49 UTC (17 days ago): “We observed short flaps occurring on the ASC submarine cable system at 04/09/2026 03:50:33 UTC. However a hard down event followed at 04/09/2026 06:19:12 UTC Due to the Indigo West cable system also being offline for shunt fault repairs, traffic will take a longer path which will result in higher latency between Australia and Singapore. We are waiting for further information from Vocus regarding this outage. Information received will be shared via our status page.”
- **INDIGO West**: notice posted by Superloop, already on its page when monitoring began 14 Sep; 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.”
- **INDIGO West**: works scheduled 2 Oct 00:00 UTC to 8 Oct 23:00 UTC, per AusInternet: “Indigo West (Perth-Singapore) Shunt Fault Repairs (Singapore)”
- **Measured route**: Perth to Oman [DIRECT_LOST] at 21 Sep 05:00 UTC — every direct path is gone: 2 path(s) were within Perth to Oman's physical floor, now none. Best path 112.1ms -> 137.0ms. 2 of 4 paths stepped with it. 2 independent vantages. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- **Measured route**: Perth to Oman [GROUP_STEP] at 21 Sep 07:00 UTC — 2 of 4 paths stepped, median +20.0ms against each path's own floor. 1 independent vantages. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- **Measured route**: Perth to Oman [RECOVERY] at 21 Sep 07:00 UTC — DIRECT_LOST has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- **Measured route**: Perth to Oman [RECOVERY] at 21 Sep 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 Oman Australia Cable (OAC) (TeleGeography).
- **Measured route**: Perth to Oman [DIRECT_LOST] at 21 Sep 14:00 UTC — every direct path is gone: 2 path(s) were within Perth to Oman's physical floor, now none. Best path 112.1ms -> 137.6ms. 2 of 4 paths stepped with it. 2 independent vantages. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- **Measured route**: Perth to Oman [RECOVERY] at 21 Sep 16:00 UTC — DIRECT_LOST has cleared: two consecutive hours back to normal. 0 independent vantages. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- **Measured latency** (RIPE Atlas, best measured path over 24 hours against each route's best sustained floor over 31 days): Perth to Singapore 191.6ms, up 145.0ms on its 46.6ms floor; Sydney to Singapore 144.5ms, up 48.1ms 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. 1 of these operator incidents or notices is new since the last brief (20 Sep 19:36 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

Vocus expects to complete permanent repairs to the Australia Singapore Cable (ASC) by 4 November [1]. This follows the scheduled restoration of the Indigo West subsea cable on 24 October, which serves as a primary route between Australia and Singapore [1]. While the ASC fault continues to affect services, Vocus stated that Layer 2 Ethernet services via the Perth-Singapore route through Jakarta remain operational [1].

## International Infrastructure Developments

The ACE Cable consortium selected Ciena to upgrade the Africa Coast to Europe (ACE) system to over 30 Tb/s using WaveLogic 6 Extreme coherent optics [2]. Meanwhile, Meta and its partners announced Petal, a petabit-class transoceanic cable between France and the United States, which is expected to enter service in 2029 using multi-core fiber technology [5]. In the South Atlantic, Fugro clarified that its vessel, Fugro Supporter, conducted a seabed survey off Argentina for a project contracted by SubCom, rather than the UK government [4]. 

Canalink completed the marine deployment of the Atlántica cable project in the Canary Islands, with the vessel Teliri installing 553 kilometers of cable to connect Gran Canaria, Fuerteventura, and Lanzarote [3]. To support growing installation demands, Jan De Nul ordered a second subsea trenching vessel capable of burying cables up to five metres deep [6].

## Capacity Upgrades and Infrastructure Interdependencies

FLAG announced on 21 September 2026 that it is deploying Ciena WaveLogic 6 Extreme technology on its dedicated fiber pair within the ECHO submarine cable system [7]. The upgrade covers more than 16,000 kilometers of the trans-Pacific route connecting Singapore, Guam, and California, and is intended to support new 400GbE and 800GbE services for hyperscalers and cloud providers [7]. 

Additionally, the Submarine Telecoms Forum released Issue 150, which includes expert assessments on the intersection of offshore energy and submarine networks [8]. The publication highlights how fiber networks support oil, gas, and wind operations, while also addressing AI capacity, South Pacific resilience, and the SAEx East cable system [8].

## Also noted

- A ship off Sicily reportedly dragged its anchor for 300 kilometres and sliced through six submarine cables, an event that went unnoticed by anyone onshore [9].

## References

1. [Vocus expects ASC repairs to be completed on 4 November](https://www.telecompaper.com/news/vocus-expects-asc-repairs-to-be-completed-on-4-november--1583221) (telecompaper.com)
   telecompaper.com
2. [ACE Cable Selects Ciena for 30 Tb/s Upgrade](https://subtelforum.com/ace-cable-selects-ciena-for-30-tb-s-upgrade/) (Submarine Telecoms Forum)
   subtelforum.com · Also reported by: capacityglobal.com
3. [Canalink Completes Atlántica Cable Deployment](https://subtelforum.com/canalink-completes-atlantica-cable-deployment/) (Submarine Telecoms Forum)
   subtelforum.com
4. [Fugro Clarifies Argentina Telecom Cable Survey](https://subtelforum.com/fugro-clarifies-argentina-telecom-cable-survey/) (Submarine Telecoms Forum)
   subtelforum.com
5. [Inside Petal: Building the World’s First Petabit-Class Transoceanic Subsea Cable](https://engineering.fb.com/2026/09/21/connectivity/petal-petabit-transoceanic-subsea-cable/) (Meta, Engineering Connectivity blog)
   engineering.fb.com
6. [Jan De Nul Orders Second Subsea Trenching Vessel](https://www.marinelink.com/news/jan-de-nul-orders-second-subsea-trenching-543122) (marinelink.com)
   marinelink.com
7. [FLAG Launches 400GbE and 800GbE on Echo](https://subtelforum.com/flag-launches-400gbe-and-800gbe-on-echo/) (Submarine Telecoms Forum)
   subtelforum.com
8. [SubTel Forum Issue 150, Offshore Energy OUT NOW!](https://subtelforum.com/subtel-forum-issue-150-offshore-energy/) (Submarine Telecoms Forum)
   subtelforum.com
9. [Almost everything you do online crosses the seabed through cables about as thick as a garden hose, not satellites. There are roughly 1.5 million kilometres of them, and repair ships spend their ...](https://scienceblog.com/d-almost-everything-you-do-online-crosses-the-seabed-through-cables-about-as-thick-as-a-garden-hose-not-satellites-there-are-roughly-1-5-million-kilometres-of-them-and-repair-ships-spend-their-workin) (scienceblog.com)
   Published: 20 Sep 2026 · scienceblog.com · Claim type: analyst_assessment · Subject: analysis, precedent · Systems named: SMW4, IMEWE · Vessels named: KIS-ORCA · 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
  - `21 Sep 05:49 UTC` Identified: Scheduled to repair the fault on Indigo West off the coast of Perth has completed. Unfortunately the existing shunt fault on Indigo West in Singapore has deteriorated into a full cable break and services remain down. Repairs off Singapore is expected to be on 16 Oct 2026 until 26 Oct 2026.
  - `16 Sep 08:45 UTC` Identified: We would like to provide you with the latest update regarding the shunt fault in Indigo West cable system. Our submarine cable provider has informed the completion of restoration works as scheduled was completed on 15 September 03:53 UTC. They have powered up Indigo West after the final bight was released and power control was handed back to CLS. However, traffic failed to restore. …
  <sub>page last checked 2026-09-21 19:08 UTC · https://ausinternet.com.au/status/</sub>
- **Australia Singapore Cable** · Global Secure Layer — network status · Identified, open since 4 Sep
  - `4 Sep 06:49 UTC` Identified: We observed short flaps occurring on the ASC submarine cable system at 04/09/2026 03:50:33 UTC. However a hard down event followed at 04/09/2026 06:19:12 UTC Due to the Indigo West cable system also being offline for shunt fault repairs, traffic will take a longer path which will result in higher latency between Australia and Singapore. We are waiting for further information from Vocus regarding this outage. Information received will be shared via our status page.
  <sub>page last checked 2026-09-21 19:08 UTC · https://status.gslnetworks.com.au/incidents/wqmz5wt7l8qj</sub>
- **INDIGO West** · Superloop — outages · active notice, on the page when monitoring began 14 Sep 21:44 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.
  <sub>page last checked 2026-09-21 19:08 UTC · https://www.superloop.com/outages/</sub>
- **INDIGO West** · AusInternet — network status · works scheduled 2 Oct 00:00 UTC to 8 Oct 23:00 UTC: “Indigo West (Perth-Singapore) Shunt Fault Repairs (Singapore)”
  <sub>page last checked 2026-09-21 19:08 UTC · https://ausinternet.com.au/status/</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: 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) — 15 documents, last 2026-09-15 (quiet 7d)

**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 273.6ms (+73.5ms per probe against its own history, 22 probes); ocean crossing 151.0ms; queuing 0.7ms; 31 days of history; clean crossing (22 probe(s), 41 reading(s) excluded as below the corridor's physical floor)
- **sydney to japan** — best path 100.4ms; typical path 168.2ms (-0.1ms per probe against its own history, 17 probes); ocean crossing 127.3ms; queuing 0.5ms; 31 days of history; clean crossing (17 probe(s))
- **sydney to nz** — best path 26.7ms; typical path 34.4ms (-0.0ms per probe against its own history, 8 probes); ocean crossing 28.1ms; queuing 0.2ms; steady against 31 days of history; clean crossing (8 probe(s))
- **sydney to singapore** — best path **144.5ms, +48.1ms on its best sustained 96.5ms**; typical path 228.5ms (+47.5ms per probe against its own history, 22 probes); ocean crossing 153.6ms; queuing 0.7ms; 31 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.5ms against a 52.0ms floor; 11/23 paths direct (normally 12) <br><sub>Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S), PIPE Pacific Cable-1 (PPC-1)</sub>
- **Dili to Australia** — best 52.1ms 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 64.0ms against a 29.5ms floor; 43 paths measured <br><sub>INDIGO-West, Australia-Singapore Cable (ASC)</sub>
- **Perth to Oman** — best 112.8ms 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 51.6ms against a 38.3ms floor; 8/67 paths direct (normally 22) <br><sub>INDIGO-West, Australia-Singapore Cable (ASC), Darwin-Jakarta-Singapore Cable (DJSC)</sub>
- **Sydney to Fiji** — best 37.7ms 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.2ms against a 80.0ms floor; 2 paths measured <br><sub>Telstra Endeavour, Southern Cross Cable Network (SCCN), Hawaiki</sub>
- **Sydney to Honiara** — best 38.2ms 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; 23/94 paths direct (normally 25) <br><sub>Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S)</sub>
- **Sydney to New Zealand** — best 23.4ms against a 21.1ms floor; 50/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; 6/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.6ms against a 118.3ms floor; 276/296 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>

<sub>Collection: 566 successful fetches in 24h, 45 errors across 10 source(s). Generated 2026-09-21 19:37 UTC.</sub>
