Botnia: 0.7× baseline latency
What we measured
| Cable | Botnia |
| Segment | Umeå, SE → Vaasa, FI |
| Detected | 2026-05-28 17:03 UTC |
| Resolved | 2026-05-29 13:29 UTC |
| Duration | 20h 26m |
| Observed latency | 16.5 ms |
| Baseline | 23.6 ms · 0.7× |
| Increase | +521% |
| Severity | critical |
Who is affected
Countries where Botnia 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, BCS North - Phase 2 +11 more | no measurement today; median 55 ms over 30 days (10 routes) |
| Sweden resilience index: 100 · resilient |
1 of 29 cables (3% of submarine diversity) | Baltic Sea Submarine Cable, Baltica, BCS East-West Interlink +25 more | median 68 ms today vs 71 ms over 30 days (42 routes) - unchanged |
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 changed route while latency was elevated. A reroute of this kind usually follows a fault somewhere on the original path.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026052801: critical - ratio 6.21x
- Alert #128 improving: 1/3 consecutive OK
- Alert #128 improving: 1/3 consecutive OK
- Alert #128 improving: 1/3 consecutive OK
- Alert #128 improving: 2/3 consecutive OK
- Alert #128 improving: 1/3 consecutive OK
- Alert #128 improving: 1/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.