Situation
- Australia Singapore Cable: open since 4 Sep, 76 days, per Global Secure Layer. Operator status: Monitoring.
Latest update, 6 Nov 02:37 UTC (13 days ago): “Update from Vocus: Vocus continues to progress restoration activities following the Australia Singapore Cable (ASC) fault, with marine repair operations having commenced at the ASC fault location. The repair vessel successfully commenced cable recovery operations, with one end of the damaged cable recovered onboard. During repair operations, a crew member of the repair vessel required urgent medical attention. …” - Australia Singapore Cable: first update on the page 23 Sep, per Vocus.
Latest update, 25 Sep 07:45 UTC (55 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. …”
Vocus's page has not been checked since 2026-11-12; this may be out of date. - Measured route: Perth to Oman [RECOVERY] at 18 Nov 20:00 UTC — DIRECT_LOST has cleared: two consecutive hours back to normal. The only system leaving Australia for this destination is Oman Australia Cable (OAC) (TeleGeography).
- Measured corridor (RIPE Atlas traceroute between fixed anchors, best path over 24 hours; baseline is the corridor's best sustained path over 89 days): Sydney to Japan best path 100.4ms, typical path up 22.2ms per probe against its own history.
- 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.
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 (18 Nov 16:04 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.
Executive summary
- The Pakistan Telecommunication Authority confirmed a technical fault on the SEA-ME-WE 5 system 11km off Pakistan's coast [1].
- The Pakistan Telecommunication Authority reported rerouting traffic to mitigate service degradation from the SEA-ME-WE 5 fault [2].
- The Quad, India, the US, Australia, and Japan announced the Indo-Pacific Maritime Surveillance Collaboration to improve information sharing [3].
- India and Japan issued a joint statement committing to strengthen undersea cable infrastructure and cybersecurity [4].
- SK Broadband announced it will build a quantum-security test network on the Busan to Singapore segment of the SJC2 cable [7].
Today
The Pakistan Telecommunication Authority (PTA) confirmed a technical fault occurred on the SEA-ME-WE 5 (SMW5) submarine cable system on November 18, 2026 [1]. The fault, located approximately 11 kilometres off Pakistan's coast, has resulted in intermittent connectivity and slowed speeds for domestic users [1]. Transworld Associates (TWA) is currently coordinating with the SMW5 Consortium to investigate the cause and establish a restoration timeline [1].
SEA-ME-WE 5 Fault and Regional Security Context
The Pakistan Telecommunication Authority (PTA) reported a fault in the SEA-ME-WE 5 international submarine cable system approximately 11 kilometres off Pakistan's coast on November 19, 2026 [2]. Transworld Associates (TWA) is coordinating with the SMW5 consortium to identify the cause, while the PTA is currently rerouting traffic through alternative links to mitigate service degradation [2].
Mathrubhumi English reports that this incident follows a separate report from October 23 stating that Iran considered targeting undersea cables in the Gulf during potential future conflicts [2]. While the PTA is managing the immediate technical impact, the report highlights broader concerns regarding the vulnerability of regional digital infrastructure [2].
Indo-Pacific Maritime Security and Infrastructure Cooperation
During a meeting in Manila on November 17, 2026, leaders from the Quad, India, the United States, Australia, and Japan, announced the Indo-Pacific Maritime Surveillance Collaboration to improve information sharing [3]. The summit signaled a shift toward 'deterrence by awareness and resilience' by pledging cooperation on cybersecurity, artificial intelligence, and critical mineral supply chains [3]. Additionally, the ministers from India and Japan issued a joint statement during a 2+2 Foreign and Defence Ministerial Meeting in Tokyo committing to strengthen undersea cable infrastructure and cybersecurity to maintain a free and open Indo-Pacific [4].
International Cable Repair Capacity and Mitigation
The International Cable Protection Committee (ICPC) reports that fishing and anchoring remain responsible for approximately 84% of subsea cable faults, though the frequency of these incidents has improved from one per 5,000 km in 2015 to one per 10,500 km [5]. While the industry maintains sufficient repair vessels, the ICPC notes that bureaucratic hurdles such as permits and customs are the primary bottlenecks delaying restoration, which typically takes 5 to 9 days [5].
In the Baltic Sea, the European Union has awarded EUR 9.55 million in co-funding to Merikarhu to establish rapid repair capacity [6]. This project, coordinated by Finland's National Emergency Supply Agency, aims to procure equipment that can be deployed on a vessel within three days of arrival to support telecommunications and energy links when commercial capacity is unavailable [6].
Quantum Security and Infrastructure Expansion
SK Broadband announced it will build an international quantum-security test network on the Busan, Singapore segment of the SJC2 (Southeast Asia-Japan Cable 2) undersea cable, with a target launch date of 2027 [7]. Selected for South Korea's 'Open Quantum Testbed Advancement and Expansion' program, the company plans to deploy a hybrid system using Quantum Key Distribution (QKD) for short-range networks and Post-Quantum Cryptography (PQC) for the long-distance undersea stretch to mitigate 'harvest now, decrypt later' attacks [7].
In separate infrastructure developments, Google announced three new subsea cable systems, Alisios, Canoa, and OlaLuz, to expand connectivity across the Dominican Republic, Panama, Chile, Bermuda, and the United States [8]. Other regional projects include V.tal's 9,700-kilometer Synapse cable connecting New Jersey to São Paulo, EllaLink's Lum@link project connecting French Guiana, Brazil, and Portugal, and Chile's advancement of the Humboldt cable to connect South America to Australia [8].
References
- SMW5 Cable Fault Slows Down Pakistan Internet Again (techx.pk)
Published: 19 Nov 2026 · techx.pk · Claim type: official_statement · Subject: fault, repair · Systems named: SMW5 · Jurisdictions: PK · Also reported by: brandsynario.com, pakistantimes.com, phoneworld.com.pk, timesofkarachi.pk, techjuice.pk, humenglish.com - Pakistan's internet cable fault follows Iran's reported Gulf threat: What connects the two? | Mathrubhumi English (english.mathrubhumi.com)
Published: 19 Nov 2026 · english.mathrubhumi.com · Claim type: official_statement · Subject: fault, analysis, seabed_security · Systems named: SEA-ME-WE 5 · Jurisdictions: PK, IR, INT - Quad’s Quiet Deterrence (clarionindia.net)
Published: 18 Nov 2026 · clarionindia.net · Claim type: official_statement · Subject: policy, seabed_security · Jurisdictions: AU, ID, SG, TW, INT - India And Japan Condemn Terrorism, Call For Action Against UN-Listed Terror Groups (ommcomnews.com)
Published: 19 Nov 2026 · ommcomnews.com · Claim type: official_statement · Subject: policy, seabed_security · Jurisdictions: IN, JP, INT - Fault Finding: Understanding Cable Fault Mitigation and Repair (TeleGeography blog)
Published: 19 Nov 2026 · resources.telegeography.com · Claim type: analyst_assessment · Subject: analysis, repair · Jurisdictions: INT - EU Funds Baltic Subsea Cable Repair Capacity (Submarine Telecoms Forum)
Published: 18 Nov 2026 · subtelforum.com · Claim type: official_statement · Subject: policy, repair · Jurisdictions: FI, SE, EE, EU - SK Broadband to Build Quantum-Security Test Network on Busan, Singapore Undersea Cable (finance.biggo.com)
Published: 18 Nov 2026 · finance.biggo.com · Claim type: official_statement · Subject: policy, analysis · Systems named: SJC2 · Jurisdictions: KR, SG · Also reported by: Light Reading, kmib.co.kr - The New Internet Highways: Subsea Cables, Satellites, and Digital Sovereignty - Telecom Review Americas (telecomreviewamericas.com)
Published: 19 Nov 2026 · telecomreviewamericas.com · Claim type: official_statement · Subject: policy, analysis · Systems named: Alisios, Canoa, OlaLuz, Nuvem, Sol, Firmina (+4 more) · Jurisdictions: DO, PA, CL, BM, US, BR (+3 more)
Standing status
Operator incident timelines (quoted from each operator's own status page, not summarised by any model):
- Australia Singapore Cable · Global Secure Layer — network status · Monitoring, open since 4 Sep
6 Nov 02:37 UTCMonitoring: Update from Vocus: Vocus continues to progress restoration activities following the Australia Singapore Cable (ASC) fault, with marine repair operations having commenced at the ASC fault location. The repair vessel successfully commenced cable recovery operations, with one end of the damaged cable recovered onboard. During repair operations, a crew member of the repair vessel required urgent medical attention. …
page last checked 2026-11-19 15:11 UTC · https://status.gslnetworks.com.au/incidents/wqmz5wt7l8qj- Australia Singapore Cable · Vocus — ASC repair update · first update on the page 23 Sep
25 Sep 07:45 UTCUpdate: 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.
page last checked 2026-11-12 19:42 UTC · https://www.vocus.com.au/news/update-on-repairs-to-australia-singapore-cable
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.
Incident threads:
perth_indigo_2026_08(INDIGO West, INDIGO Central) — 18 documents, last 2026-11-02 (quiet 18d)
Measured corridors (RIPE Atlas traceroute between fixed anchors over 24h, no model involved):
- perth to singapore — best path 47.2ms; typical path 238.3ms (+0.8ms per probe against its own history, 21 probes); ocean crossing 46.9ms; queuing 0.4ms; 89 days of history; clean crossing (21 probe(s), 13 reading(s) excluded as below the corridor's physical floor)
- sydney to japan — best path 100.4ms; typical path 144.1ms (+22.2ms per probe against its own history, 18 probes); ocean crossing 131.1ms; queuing 0.5ms; steady against 89 days of history; clean crossing (18 probe(s), 22 reading(s) excluded as below the corridor's physical floor)
- sydney to nz — best path 24.7ms; typical path 29.5ms (+0.0ms per probe against its own history, 8 probes); ocean crossing 27.7ms; queuing 0.2ms; steady against 89 days of history; clean crossing (8 probe(s))
- sydney to singapore — best path 94.6ms; typical path 238.5ms (+8.5ms per probe against its own history, 21 probes); ocean crossing 118.1ms; queuing 0.5ms; 89 days of history; 2 intervening hop(s) included (21 probe(s))
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. A corridor's baseline is its best sustained path over the days of history shown, a different figure from a route's physical floor below. As data: https://cablewatch.liminallayers.com/data/corridors.json.
Every cable route leaving the mainland (measured hourly, no model involved):
- Australia to Guam — best 70.6ms against a 52.0ms physical floor; 7/24 paths direct (normally 12)
Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S), PIPE Pacific Cable-1 (PPC-1) - Dili to Australia — best 37.9ms against a 7.1ms physical floor; 3 paths measured
Timor-Leste South Submarine Cable (TLSSC), North-West Cable System - Melbourne to Tasmania — best 9.5ms against a 5.9ms physical floor; 8/17 paths direct (normally 8)
Basslink, Bass Strait-1, Bass Strait-2 - Perth to Jakarta — best 57.6ms against a 29.5ms physical floor; 43 paths measured
INDIGO-West, Australia-Singapore Cable (ASC) - Perth to Oman — best 106.1ms against a 85.0ms physical floor; 2/4 paths direct (normally 2)
Oman Australia Cable (OAC) · only system on this route - Perth to Singapore — best 46.0ms against a 38.3ms physical floor; 31/64 paths direct (normally 31)
INDIGO-West, Australia-Singapore Cable (ASC), Darwin-Jakarta-Singapore Cable (DJSC) - Sydney to Fiji — best 37.6ms against a 31.5ms physical floor; 4/6 paths direct (normally 6)
Southern Cross Cable Network (SCCN), Southern Cross NEXT - Sydney to Hawaii — best 194.7ms against a 80.0ms physical floor; 2 paths measured
Telstra Endeavour, Southern Cross Cable Network (SCCN), Hawaiki - Sydney to Honiara — best 38.3ms against a 28.0ms physical floor; 2/2 paths direct (normally 2)
Coral Sea Cable System (CS²) · only system on this route - Sydney to Japan — best 99.3ms against a 76.7ms physical floor; 21/108 paths direct (normally 28)
Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S) - Sydney to New Zealand — best 23.4ms against a 21.1ms physical floor; 41/65 paths direct (normally 48)
Southern Cross Cable Network (SCCN), Southern Cross NEXT, Hawaiki, Tasman Global Access (TGA) Cable - Sydney to Noumea — best 22.4ms against a 19.3ms physical floor; 5/9 paths direct (normally 5)
Gondwana-1 · only system on this route - Sydney to Port Moresby — best 37.6ms against a 26.9ms physical floor; 3/6 paths direct (normally 3)
Coral Sea Cable System (CS²), PIPE Pacific Cable-1 (PPC-1) - Sydney to US West Coast — best 135.8ms against a 118.3ms physical floor; 186/303 paths direct (normally 249)
Southern Cross Cable Network (SCCN), Southern Cross NEXT, Hawaiki, Telstra Endeavour
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 https://cablewatch.liminallayers.com/data/coverage.json.
Collection: 626 successful fetches in 24h, 40 errors across 13 source(s). Generated 2026-11-19 16:06 UTC.