Circe North cable: latency up to 2× normal, 8 Jun 2026
What we measured
| Cable | Circe North |
| Segment | Lowestoft, GB → Zandvoort, NL |
| Detected | 2026-06-08 21:01 UTC |
| Resolved | 2026-06-09 01:02 UTC |
| Duration | 4h 1m |
| Observed latency | 31.6 ms |
| Baseline | 34.5 ms · 2× |
| Increase | +100% |
| Severity | warning |
Who is affected
Countries where Circe North 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 |
|---|---|---|---|
| Netherlands resilience index: 100 · resilient |
1 of 12 cables (8% of submarine diversity) | Amerigo Vespucci, Atlantic Crossing-1 (AC-1), COBRAcable +8 more | median 46 ms today vs 54 ms over 30 days (724 routes) - unchanged |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 103 ms today vs 74 ms over 30 days (1011 routes) - slower |
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. Other measurements did not confirm the event. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026060801: warning - ratio 2x
- Alert #132 improving: 1/3 consecutive OK
- Alert #132 improving: 2/3 consecutive OK
- Alert #132 resolved: RTT 31.56ms (baseline 34.51ms), 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.