BCS North - Phase 2: 1.27× baseline latency
What we measured
| Cable | BCS North - Phase 2 |
| Segment | Logi, RU → Helsinki, FI |
| Detected | 2026-05-09 17:01 UTC |
| Resolved | 2026-05-09 20:31 UTC |
| Duration | 3h 29m |
| Observed latency | 75.5 ms |
| Baseline | 59.3 ms · 1.27× |
| Increase | +162% |
| 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. Some probes saw the degradation and others did not, which usually means a partial or regional effect.
Timeline
- Alert 2026050901: warning - ratio 2.61x
- Alert #114 improving: 1/3 consecutive OK
- Alert #114 improving: 2/3 consecutive OK
- Alert #114 resolved: RTT 75.49ms (baseline 59.26ms), 8 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.