Sweden-Estonia (EE-S 1) cable: latency up to 2× normal, 30 Jul 2026
What we measured
| Cable | Sweden-Estonia (EE-S 1) |
| Segment | Tallinn, EE → Stavsnas, SE |
| Detected | 2026-07-30 11:01 UTC |
| Resolved | 2026-07-30 14:00 UTC |
| Duration | 2h 59m |
| Observed latency | 47.2 ms |
| Baseline | 52.1 ms · 2.04× |
| Increase | +104% |
| Severity | warning |
Who is affected
Countries where Sweden-Estonia (EE-S 1) 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 |
|---|---|---|---|
| Estonia resilience index: 80 · resilient |
1 of 8 cables (13% of submarine diversity) | Baltic Sea Submarine Cable, E-FINEST, Finland Estonia Connection 1 (FEC-1) +4 more | median 67 ms today vs 56 ms over 30 days (1405 routes) - slower |
| 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 61 ms today vs 64 ms over 30 days (2925 routes) - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
Vessel data for this period is not available.
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
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. Other measurements did not confirm the event, so we do not count it as a cable fault.
Timeline
- Alert 2026073002: warning - ratio 2.04x
- Alert #161 improving: 1/3 consecutive OK
- Alert #161 improving: 2/3 consecutive OK
- Alert #161 resolved: RTT 47.17ms (baseline 52.08ms), 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.