Gemini Bermuda: 0.88× baseline latency
What we measured
| Cable | Gemini Bermuda |
| Segment | Manasquan, US → St. David’s, BM |
| Detected | 2026-04-05 02:32 UTC |
| Resolved | 2026-04-05 05:30 UTC |
| Duration | 2h 58m |
| Observed latency | 61.4 ms |
| Baseline | 69.7 ms · 0.88× |
| Increase | +103% |
| 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 175 ms today vs 176 ms over 30 days (6 routes) - unchanged |
| United States resilience index: 100 · resilient |
1 of 119 cables (1% of submarine diversity) | ACS Alaska-Oregon Network (AKORN), AEC-1, Airraq +115 more | median 88 ms today vs 115 ms over 30 days (290 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
Not enough history on this endpoint to compare the path against a baseline.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert #45: warning (backfilled)
- Alert #45 improving: 1/3 consecutive OK checks
- Alert #45 improving: 2/3 consecutive OK checks
- Alert #45 resolved: RTT 61.41ms (baseline 69.69ms)
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.