Gemini Bermuda cable: latency up to 2.1× normal, 22 Oct 2026
What we measured
| Cable | Gemini Bermuda |
| Segment | Manasquan, US → St. David’s, BM |
| Detected | 2026-10-22 15:02 UTC |
| Duration | 1d 21h (ongoing) |
| Observed latency | 49.1 ms |
| Baseline | 23.3 ms · 2.12× |
| Increase | +112% |
| Severity | warning |
Who is affected
Countries where Gemini Bermuda 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 |
|---|---|---|---|
| Bermuda resilience index: 52 · vulnerable |
1 of 6 cables (17% of submarine diversity) | Canoa, Caribbean-Bermuda U.S. (CBUS), GlobeNet +2 more | median 164 ms today vs 172 ms over 30 days (7 routes) - unchanged |
| United States resilience index: 100 · resilient |
1 of 122 cables (1% of submarine diversity) | ACS Alaska-Oregon Network (AKORN), AEC-1, Airraq +118 more | median 116 ms today vs 108 ms over 30 days (3282 routes) - unchanged |
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. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.
Timeline
- Alert 2026102202: warning - ratio 2.12x
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.