BCS North - Phase 2: 0.9× baseline latency
What we measured
| Cable | BCS North - Phase 2 |
| Segment | Logi, RU → Helsinki, FI |
| Detected | 2026-05-08 13:01 UTC |
| Resolved | 2026-05-08 16:31 UTC |
| Duration | 3h 29m |
| Observed latency | 32.9 ms |
| Baseline | 36.5 ms · 0.9× |
| Increase | +146% |
| 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 55 ms over 30 days (10 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 124 ms today vs 79 ms over 30 days (213 routes) - slower |
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. Multiple independent probes saw the same degradation, so this was not a local artefact.
Timeline
- Alert 2026050801: warning - ratio 2.46x
- Alert #113 improving: 1/3 consecutive OK
- Alert #113 improving: 1/3 consecutive OK
- Alert #113 improving: 2/3 consecutive OK
- Alert #113 resolved: RTT 32.93ms (baseline 36.45ms), 4 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.