Ulleung-Mainland 2 cable: endpoint unreachable from all probes, 29 Sep 2026
What we measured
| Cable | Ulleung-Mainland 2 |
| Segment | Kazakhstan → Hosan-ri |
| Detected | 2026-09-29 09:31 UTC |
| Resolved | 2026-09-29 11:32 UTC |
| Duration | 2h 0m |
| Observed latency | 315.7 ms |
| Severity | critical |
Who is affected
Countries where Ulleung-Mainland 2 comes ashore, how much of their submarine diversity this cable represents, and what our measurements into them show.
| Country | Dependence on this cable | Other submarine cables | What the measurements show |
|---|---|---|---|
| South Korea resilience index: 100 · resilient |
1 of 17 cables (6% of submarine diversity) | APCN-2, Asia Pacific Gateway (APG), Asia United Gateway East (AUG East) +13 more | no measurement today; median 107 ms over 30 days (33 routes) |
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
- Alert #214 improving: 1/3 consecutive OK
- Alert #214 improving: 2/3 consecutive OK
- Alert #214 resolved: RTT 315.65ms (baseline 0ms), 3 consecutive OK
Evidence
Network measurements behind this detection, verifiable independently:
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.