COBRAcable: 1.39× baseline latency
What we measured
| Cable | COBRAcable |
| Segment | Eemshaven, NL → Endrup, DK |
| Detected | 2026-04-05 02:32 UTC |
| Resolved | 2026-04-05 05:30 UTC |
| Duration | 2h 58m |
| Observed latency | 36.7 ms |
| Baseline | 26.3 ms · 1.39× |
| Increase | +118% |
| Severity | warning |
Who is affected
Countries where COBRAcable 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 |
|---|---|---|---|
| Denmark resilience index: 100 · resilient |
1 of 33 cables (3% of submarine diversity) | Aurora, Baltica, CANTAT-3 +29 more | median 68 ms today vs 62 ms over 30 days (11 routes) - unchanged |
| Netherlands resilience index: 100 · resilient |
1 of 12 cables (8% of submarine diversity) | Amerigo Vespucci, Atlantic Crossing-1 (AC-1), Circe North +8 more | median 47 ms today vs 65 ms over 30 days (89 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 #44: warning (backfilled)
- Alert #44 improving: 1/3 consecutive OK checks
- Alert #44 improving: 2/3 consecutive OK checks
- Alert #44 resolved: RTT 36.68ms (baseline 26.31ms)
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.