Incident report · 2026033101
Sweden-Latvia cable: latency up 38%, 31 Mar 2026
Resolved · 2h 58m
What we measured
| Cable | Sweden-Latvia |
| Segment | Stockholm, SE → Ventspils, LV |
| Detected | 2026-03-31 02:33 UTC |
| Resolved | 2026-03-31 05:32 UTC |
| Duration | 2h 58m |
| Observed latency | 87.1 ms |
| Baseline | 63 ms · 1.38× |
| Increase | +332% |
| Severity | warning |
Who is affected
Countries where Sweden-Latvia 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 |
|---|---|---|---|
| Latvia resilience index: 40 · vulnerable |
1 of 3 cables (33% of submarine diversity) | BCS East, Latvia-Sweden 1 (LV-SE 1) | median 51 ms today vs 53 ms over 30 days (142 routes) - unchanged |
| 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 67 ms today vs 71 ms over 30 days (381 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
No usable traceroute data for this window.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert #32: warning - Ventspils
- Alert #32 resolved: Ventspils
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 2026033101: Sweden-Latvia. https://geocables.com/incident/2026033101
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=sweden-latvia" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>