---
date: 2026-10-02
issue: 70
title: Philippine Coast Guard Confronts Chinese Research Vessel in Luzon Strait
standfirst: The standoff occurred near critical undersea international communications
  cables and a strategic maritime chokepoint. The incident highlights escalating tensions
  as China asserts territorial claims in the region.
jurisdictions:
- PH
- CN
- TW
- US
- AZ
- KZ
tags: []
vertical: cablewatch
---

## Situation

- **Australia Singapore Cable**: first update on the page 23 Sep, per Vocus.  
  Latest update, 25 Sep 07:45 UTC (7 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**: open since 8 Aug, 55 days, per AusInternet. Operator status: Partial Service Disruption.  
  Latest update, 21 Sep 05:49 UTC (11 days ago): “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, 28 days, per Global Secure Layer. Operator status: Identified.  
  Latest update, 4 Sep 06:49 UTC (28 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 Singapore [RECOVERY] at 02 Oct 02:00 UTC — DIRECT_LOST has cleared: two consecutive hours back to normal. 0 independent vantages. Systems serving this route: INDIGO-West, Australia-Singapore Cable (ASC), Darwin-Jakarta-Singapore Cable (DJSC) (TeleGeography). The measurement cannot say which one moved.
- **Measured route**: Australia to Guam [DIRECT_LOST] at 02 Oct 12:00 UTC — direct paths down to 6 of the 12 this route normally holds. Best path 70.5ms -> 70.9ms. 4 independent vantages. Systems serving this route: Australia-Japan Cable (AJC), Japan-Guam-Australia South (JGA-S), PIPE Pacific Cable-1 (PPC-1) (TeleGeography). The measurement cannot say which one moved.
- **Measured latency** (RIPE Atlas, best measured path over 24 hours against each route's best sustained floor over 42 days): Perth to Singapore 191.7ms, up 145.1ms on its 46.6ms floor; Sydney to Japan 100.4ms, up 39.8ms on its 100.5ms floor; Sydney to Singapore 144.6ms, 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. No operator has posted an update or a new notice on these since the last brief (1 Oct 19:22 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

The Philippine Coast Guard (PCG) confronted the Chinese research vessel Jia Hai Ke 7 on September 28, 2026, after the vessel was observed loitering northwest of Itbayat in the Luzon Strait [1]. The PCG deployed the BRP Teresa Magbanua and PCG Islander 251 to intercept the ship, using assertive maneuvers to close within 50 to 100 yards [1]. The Jia Hai Ke 7 eventually withdrew after being shielded by the Chinese Coast Guard vessel 2503, which issued threatening radio challenges to the Philippine ships [1].

## International Infrastructure and Policy Developments

The United States Submarine Cable Security Policy Act of 2026 was introduced by Representatives August Pfluger and Rob Menendez on October 1, 2026 [2]. The bipartisan legislation aims to replace case-by-case security agreements with standardized requirements for cables landing in the United States, seeking to provide predictable rules for trusted companies while protecting infrastructure that carries over 95 percent of international data flows [2].

In the Middle East and Central Asia, Azerbaijan and Kazakhstan confirmed a commitment to commission the 380-kilometre Trans-Caspian fiber-optic link by the end of 2026 [3]. The project, a joint venture between AzerTelecom and Kazakhtelecom called CaspiLink, will connect Sumgayit to Aktau with over 400 Tbps of capacity [3]. Additionally, Mobily highlighted its landing footprint across Jeddah, Al Khobar, Yanbu, and Duba, while detailing the Mobily Red Sea Cable, a Saudi-owned project linking Duba to Sharm El Sheikh, Egypt [5]. Meanwhile, a post on baobabnewsletter.substack.com reports that Africa's internet infrastructure relies almost exclusively on a single 43-year-old vessel, the Léon Thévenin, which contributes to repair times exceeding 50 days in the region [6].

## SGI Cable System Development in Indonesia

SGI and its consortium partners, including INET, Surge, and Weave, are developing the SGI Cable System, a 6,870-kilometer subsea backbone across Indonesia [7]. The system features a 16-fiber-pair architecture with a 25 Tbps design capacity and will connect 14 landing stations across Java, Kalimantan, Sulawesi, Nusa Tenggara, Maluku, and Papua [7]. The project is targeted to be Ready-for-Service in late 2028, with wet-plant materials scheduled for delivery in September 2027 [7].

## Also noted

- The Greece-Cyprus electricity interconnection project is entering a new phase, amid new tensions with Ankara [8].
- DNA from 436 water bottles inside four North Sea wind farms confirmed the presence of five shark and ray species, including a basking shark found in winter [9].

## References

1. [Philippine Coast Guard Confronts Chinese Research Vessel](https://chiangraitimes.com/news-asia/philippines-cost-guard-china) (chiangraitimes.com)
   Published: 02 Oct 2026 · chiangraitimes.com · Claim type: analyst_assessment · Subject: vessel_activity, analysis · Vessels named: BRP Teresa Magbanua, Jia Hai Ke 7, Vessel 2503 · Jurisdictions: PH, CN, TW · Also reported by: The Maritime Executive
2. [Pfluger, Menendez Propose Undersea Cable Security Law](https://subtelforum.com/pfluger-menendez-propose-undersea-cable-security-law/) (Submarine Telecoms Forum)
   subtelforum.com
3. [Azerbaijan, Kazakhstan Target 2026 Cable Launch](https://subtelforum.com/azerbaijan-kazakhstan-target-2026-cable-launch/) (Submarine Telecoms Forum)
   subtelforum.com
4. [Medusa subsea cable system expands to Jordan, partners with NaiTel](https://www.datacenterdynamics.com/en/news/medusa-subsea-cable-system-expands-to-jordan-partners-with-naitel/) (DCD, subsea)
   datacenterdynamics.com
5. [Mobily at Submarine Networks World 2026: Connecting Continents, Powering Cloud and AI](https://www.telecomreviewasia.com/news/interviews/30447-mobily-at-submarine-networks-world-2026-connecting-continents-powering-cloud-and-ai/) (Telecom Review Asia)
   telecomreviewasia.com
6. [🔅 Entire Internet Hanging On By One 43-Year-Old Ship](https://baobabnewsletter.substack.com/p/leon-thevenin-internet-africa) (baobabnewsletter.substack.com)
   Published: 02 Oct 2026 · baobabnewsletter.substack.com · Publisher: self-published, not an official or analyst source · Claim type: analyst_assessment · Subject: analysis, policy · Vessels named: Léon Thévenin · Jurisdictions: AF, INT
7. [SGI Plans 6,870-km Subsea Backbone Across Indonesia](https://www.telecomreviewasia.com/news/industry-news/30450-sgi-plans-6870-km-subsea-backbone-across-indonesia/) (Telecom Review Asia)
   telecomreviewasia.com
8. [New Tensions with Ankara over Greece-Cyprus Electricity Cable](https://www.thenationalherald.com/new-tensions-with-ankara-over-greece-cyprus-electricity-cable/) (thenationalherald.com)
   thenationalherald.com
9. [DNA from 436 water bottles inside four North Sea wind farms confirmed five shark and ray species present, including a basking shark found in winter](https://www.ecoportal.net/en/dna-436-water-bottles-inside-four/40483/) (ecoportal.net)
   ecoportal.net

---

## Standing status

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

- **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-02 13:28 UTC · https://www.vocus.com.au/news/update-on-repairs-to-australia-singapore-cable</sub>
- **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.
  <sub>page last checked 2026-10-02 18:11 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-10-02 18:11 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-10-02 18:11 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-10-02 18:11 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: 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) — 18 documents, last 2026-09-26 (quiet 7d)

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

- **perth to singapore** — best path **191.7ms, +145.1ms on its best sustained 46.6ms**; typical path 273.8ms (+79.2ms per probe against its own history, 22 probes); ocean crossing 151.5ms; queuing 0.6ms; 42 days of history; clean crossing (22 probe(s), 70 reading(s) excluded as below the corridor's physical floor)
- **sydney to japan** — best path 100.4ms; typical path 181.1ms (+39.8ms per probe against its own history, 18 probes); ocean crossing 134.8ms; queuing 0.5ms; 42 days of history; clean crossing (18 probe(s))
- **sydney to nz** — best path 26.7ms; typical path 34.5ms (-0.0ms per probe against its own history, 8 probes); ocean crossing 27.4ms; queuing 0.2ms; steady against 42 days of history; clean crossing (8 probe(s))
- **sydney to singapore** — best path **144.6ms, +48.1ms on its best sustained 96.5ms**; typical path 223.2ms (+43.3ms per probe against its own history, 22 probes); ocean crossing 154.4ms; queuing 0.6ms; 42 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.8ms against a 52.0ms floor; 6/17 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 50.4ms 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.1ms 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.1ms against a 29.5ms floor; 46 paths measured <br><sub>INDIGO-West, Australia-Singapore Cable (ASC)</sub>
- **Perth to Oman** — best 138.9ms against a 85.0ms floor; **0/2 paths direct (normally 2)** <br><sub>Oman Australia Cable (OAC) · only system on this route</sub>
- **Perth to Singapore** — best 52.9ms against a 38.3ms floor; 8/67 paths direct (normally 8) <br><sub>INDIGO-West, Australia-Singapore Cable (ASC), Darwin-Jakarta-Singapore Cable (DJSC)</sub>
- **Sydney to Fiji** — best 38.2ms 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.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.4ms against a 76.7ms floor; 19/106 paths direct (normally 25) <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; 41/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.4ms 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.7ms against a 118.3ms floor; 281/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-09-23` GY — NETWORK — A cut fibre-optic cable caused a significant drop in Internet traffic from One Communications (AS19863) in Guyana.

<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: 588 successful fetches in 24h, 13 errors across 5 source(s). Generated 2026-10-02 18:36 UTC.</sub>
