Konstanz-Friedrichshafen cable: latency up to 2.1× normal, 30 Jul 2026
What we measured
| Cable | Konstanz-Friedrichshafen |
| Segment | Minsk, BY → Friedrichshafen, DE |
| Detected | 2026-07-30 15:02 UTC |
| Resolved | 2026-07-31 00:02 UTC |
| Duration | 9h 0m |
| Observed latency | 36.3 ms |
| Baseline | 70.9 ms · 2.08× |
| Increase | +109% |
| Severity | warning |
Who is affected
Countries where Konstanz-Friedrichshafen 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 |
|---|---|---|---|
| Germany resilience index: 100 · resilient |
1 of 11 cables (9% of submarine diversity) | Atlantic Crossing-1 (AC-1), C-Lion1, Elektra-GlobalConnect 1 (GC1) +7 more | median 52 ms today vs 62 ms over 30 days (1805 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
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. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026073003: warning - ratio 2.08x
- Alert #162 resolved: RTT 36.33ms (baseline 70.92ms), 4 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.