Incident report · 2026081502
COBRAcable: 0.96× baseline latency
Resolved · 2h 28m
What we measured
| Cable | COBRAcable |
| Segment | Eemshaven, NL → Endrup, DK |
| Detected | 2026-08-15 23:02 UTC |
| Resolved | 2026-08-16 01:31 UTC |
| Duration | 2h 28m |
| Observed latency | 45 ms |
| Baseline | 46.6 ms · 0.96× |
| Increase | +110% |
| 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.
Timeline
- Alert 2026081502: warning - ratio 2.1x
- Alert #170 improving: 1/3 consecutive OK
- Alert #170 improving: 2/3 consecutive OK
- Alert #170 resolved: RTT 44.95ms (baseline 46.64ms), 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.
How to cite
GeoCables (2026). Incident 2026081502: COBRAcable. https://geocables.com/incident/2026081502
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=cobracable" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>