Home
Explore What GeoCables can do Cables Locations Map My path ISP status Country resilience Check my connection Blocked websites
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Test yourself Research Guide Methodology Latency Overland links Deployments by year Earthquakes Open dataset API Widgets What's new About Contact
Incident report · 2026092602

Hokkaido-Sakhalin Cable System (HSCS): latency up to 2.1× normal, 26 Sep 2026

Resolved · 5h 32m
XTelegramWhatsAppFacebook

What we measured

CableHokkaido-Sakhalin Cable System (HSCS)
SegmentIshikari, JP → Nevelsk, RU
Detected2026-09-26 21:02 UTC
Resolved2026-09-27 02:34 UTC
Duration5h 32m
Observed latency215.9 ms
Baseline108.4 ms · 2.06×
Increase+106%
Severitywarning

Who is affected

Countries where Hokkaido-Sakhalin Cable System (HSCS) comes ashore, how much of their submarine diversity this cable represents, and what our measurements into them show.

CountryDependence on this cableOther submarine cablesWhat the measurements show
Japan
resilience index: 100 · resilient
1 of 53 cables (2% of submarine diversity) 5 Villages 6 Islands, APCN-2, APX North +49 more median 229 ms today vs 224 ms over 30 days (2905 routes) - unchanged
Russia
resilience index: 100 · resilient
1 of 13 cables (8% of submarine diversity) BCS North - Phase 2, Energy Bridge Cable, Far East Submarine Cable System +9 more median 61 ms today vs 54 ms over 30 days (17623 routes) - unchanged

Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.

Vessels nearby at the time of the incident

No vessel activity was seen within 5 km of the cable route in the window from 48 hours before to 6 hours after the start (by AIS; vessels with transmitters off are not visible).

Alert check

Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means

Path analysis

Traffic kept the same route. Latency rose without a visible path change, which points at congestion or a fault on the existing route rather than a reroute.

Cross-probe verdict. Other measurements did not confirm the event, so we do not count it as a cable fault.

Timeline

Detection method

Latency is sampled continuously from our probe network. An alert opens when round-trip time to a monitored endpoint holds above its rolling baseline, and closes automatically once it returns. Full method is described on the methodology page.

How to cite

GeoCables (2026). Incident 2026092602: Hokkaido-Sakhalin Cable System (HSCS). https://geocables.com/incident/2026092602

Embed this map

<iframe src="https://geocables.com/embed.php?type=map&id=hokkaido-sakhalin-cable-system-hscs" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>

← All cable events

Advertisement

Log In

Access your routes, favorites, and API key

Create account Forgot password?