Ultramar GE cable: latency up to 5.3× normal, 18 Sep 2026
What we measured
| Cable | Ultramar GE |
| Segment | Annobon, GQ → Sao Tome, GQ |
| Detected | 2026-09-18 21:31 UTC |
| Resolved | 2026-09-18 23:32 UTC |
| Duration | 2h 1m |
| Observed latency | 60.2 ms |
| Baseline | 62.8 ms · 5.32× |
| Increase | +432% |
| Severity | critical |
Who is affected
Countries where Ultramar GE 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 |
|---|---|---|---|
| Equatorial Guinea resilience index: 61 · moderate |
1 of 4 cables (25% of submarine diversity) | Africa Coast to Europe (ACE), Ceiba-1, Ceiba-2 | average 110 ms over 30 days |
| São Tomé & Príncipe resilience index: 33 · vulnerable |
1 of 2 cables (50% of submarine diversity) | Africa Coast to Europe (ACE) | average 59 ms over the last day vs 59 ms over 30 days - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
No vessel activity was seen within 5 km of the cable route in the window from 48 hours before to 6 hours after the start (by AIS; vessels with transmitters off are not visible).
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 2026091801: critical - ratio 5.32x
- Alert #204 improving: 1/3 consecutive OK
- Alert #204 improving: 2/3 consecutive OK
- Alert #204 resolved: RTT 60.22ms (baseline 62.81ms), 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.