← Cable Watch

18 September 2026 · Issue 56

Subsea Cable Project Proceeding at Bellbuoy Beach Without Council Approval

A 180km subsea cable project has been selected for landing at Bellbuoy Beach despite a lack of local government authorization. The development highlights ongoing regulatory friction regarding seabed infrastructure.

Markdown · Transcript · MP3 · Subscribe

Situation

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 (17 Sep 19:36 UTC). 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

Today

A 180km subsea cable project is moving forward at Bellbuoy Beach despite the fact that it has not received council approval [1]. Themercury.com.au reports that the site was chosen for the landing point, though the lack of official local government consent remains a point of contention.

Infrastructure Security and Sabotage Exercises

Finnish coast guard, police, and armed forces conducted a live exercise on September 17 involving the boarding and searching of a vessel in the Baltic Sea to improve response times for protecting underwater infrastructure [2]. The drill, which included officers fast-roping from helicopters, was designed to counter threats from divers, mini-submarines, and diving robots following several incidents since 2022 [2]. In the Arctic, the Foundation for Defense of Democracies (FDD) reports that Russia's GUGI unit conducted a covert operation near Norway’s Svalbard archipelago in spring 2026 to simulate attacks on fiber cables connecting the SvalSat ground station to mainland Norway [3]. Analyst Emmerson Overell assesses that these simulations target the interconnectedness of maritime and space infrastructure, noting that disruptions to these cables could impact NASA’s Near Space Network and human spaceflight missions [3].

International Infrastructure Developments and Security Claims

EllaLink announced on September 14, 2026, that it successfully laid two branching units for future Brazilian Amazon connections during its Lum@link marine campaign [5]. Manufactured and installed by Alcatel Submarine Networks, these units are positioned at depths of 3,920 metres and 3,690 metres to eventually connect Salinópolis in Pará and São Luís in Maranhão to the Lum@link system [5]. The installation is designed to allow for future 17 Tbps capacity branches to join the main route, which extends from Cayenne in French Guiana to EllaLink's trunk off Fortaleza [5].

Separately, a senior defence contractor claims that recent alleged Russian attempts to sever undersea cables may be rehearsals intended to knock out the United Kingdom's internet [6]. The source provided limited detail, characterizing the claims as a potential threat to UK national infrastructure and connectivity [6].

Regional Infrastructure Expansion and Policy

Taiwan's Ministry of Digital Affairs announced that the Taiwan-Matsu No. 4 submarine cable is now in service [7]. Built by Chunghwa Telecom, the nearly 300 km link connects the main island to Dongyin, Nangan, and Xiju, increasing aggregate Taiwan-Matsu transmission capacity to approximately 1.9 Tbps [7]. This system joins Taiwan-Matsu No. 2 and Taiwan-Matsu No. 3, with Taiwan-Penghu No. 4 and Penghu-Kinmen No. 4 expected to be completed by the end of the year [7].

In broader regional policy, Indonesia and India signed a five-year Memorandum of Understanding to collaborate on 4G, 5G, 6G, and quantum technologies, including disaster management communication systems [8]. Meanwhile, the Philippines is seeing U.S. support for new submarine cable and infrastructure projects in Subic Bay to counter Chinese influence [9]. These projects include the proposed Thailand-U.S. Submarine Cable System (THUS), which would connect Thailand to the U.S. via Indonesia, Malaysia, the Philippines, Singapore, and Vietnam [9].

References

  1. Bellbuoy Beach chosen for 180km subsea cable despite having no council approval (themercury.com.au)
    themercury.com.au
  2. Finnish Authorities Board Ship In Baltic Sea During Live Exercise To Protect Undersea Cables (Marine Insight)
    marineinsight.com
  3. Russia Is Practicing Attacks on Undersea Cables in the Arctic. The Consequences Could Reach Space. (fdd.org)
    fdd.org
  4. ESA awards $1.73m project to neXat for automated submarine cable backup (satelliteprome.com)
    satelliteprome.com
  5. EllaLink Lays Brazilian Amazon Branching Units (Submarine Telecoms Forum)
    subtelforum.com
  6. Russia is ‘rehearsing’ attacks that could knock out the UK’s internet (metro.co.uk)
    metro.co.uk
  7. Taiwan-Matsu No. 4 Cable Enters Service (Submarine Telecoms Forum)
    subtelforum.com
  8. Indonesia, India Forge Stronger Partnership in Telecom Innovation (Telecom Review Asia)
    telecomreviewasia.com
  9. Indo-Pacific 5x5: September 16th 2026 / Issue 419 (indopacificinsights.substack.com)
    Published: 16 Sep 2026 · indopacificinsights.substack.com · Claim type: official_statement · Subject: policy, analysis · Systems named: Thailand-U.S. Submarine Cable System (THUS) · Jurisdictions: TH, US, ID, MY, PH, SG (+1 more)

Standing status

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

Also polled for changes, but carrying no incident listing, so nothing is said about their state: SUBCO, SUBCO — INDIGO West, Telstra — service status, Vocus — network status.

Incident threads:

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

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.

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

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.

Collection: 548 successful fetches in 24h, 80 errors across 17 source(s). Generated 2026-09-18 19:28 UTC.