Incident report · 2026052801
Botnia: 0.7× baseline latency
Resolved · 20h 26m
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 |
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.
How to cite
GeoCables (2026). Incident 2026052801: Botnia. https://geocables.com/incident/2026052801
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=botnia" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>