BCS North - Phase 2 cable: latency up to 3× normal, 9 Oct 2026
What we measured
| Cable | BCS North - Phase 2 |
| Segment | Logi, RU → Helsinki, FI |
| Detected | 2026-10-09 03:02 UTC |
| Duration | 1h 29m (ongoing) |
| Observed latency | 38 ms |
| Baseline | 11.8 ms · 3.03× |
| Increase | +203% |
| Severity | warning |
Who is affected
Countries where BCS North - Phase 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 |
|---|---|---|---|
| Finland resilience index: 100 · resilient |
1 of 15 cables (7% of submarine diversity) | Baltic Sea Submarine Cable, BCS North - Phase 1, Botnia +11 more | no measurement today; median 45 ms over 30 days (66 routes) |
| Russia resilience index: 100 · resilient |
1 of 13 cables (8% of submarine diversity) | Energy Bridge Cable, Far East Submarine Cable System, Georgia-Russia +9 more | median 47 ms today vs 57 ms over 30 days (1723 routes) - faster |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
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. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.
Timeline
- Alert 2026100901: warning - ratio 3.03x
- Alert #222 improving: 2/3 consecutive OK
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.