Incident report · 2026031402
BCS East: 0.81× baseline latency
Resolved · 8h 59m
What we measured
| Cable | BCS East |
| Segment | Stockholm, SE → Stockholm, SE |
| Detected | 2026-03-14 10:32 UTC |
| Resolved | 2026-03-14 19:32 UTC |
| Duration | 8h 59m |
| Observed latency | 21.1 ms |
| Baseline | 26 ms · 0.81× |
| Increase | +225% |
| Severity | warning |
Who is affected
Countries where BCS East 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) | Latvia-Sweden 1 (LV-SE 1), Sweden-Latvia | median 71 ms today vs 71 ms over 30 days (6 routes) - unchanged |
| Lithuania resilience index: 40 · vulnerable |
1 of 3 cables (33% of submarine diversity) | BCS East-West Interlink, NordBalt | median 53 ms today vs 78 ms over 30 days (16 routes) - faster |
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 #10: warning - Ventspils
- Alert #10 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 2026031402: BCS East. https://geocables.com/incident/2026031402
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=bcs-east" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>