Incident report · 2026080501
Nigeria Cameroon Submarine Cable System (NCSCS): 1.03× baseline latency
Resolved · 2h 0m
What we measured
| Cable | Nigeria Cameroon Submarine Cable System (NCSCS) |
| Segment | Kribi, CM → Lagos, NG |
| Detected | 2026-08-05 09:32 UTC |
| Resolved | 2026-08-05 11:32 UTC |
| Duration | 2h 0m |
| Observed latency | 20.6 ms |
| Baseline | 20.1 ms · 1.03× |
| Increase | +815% |
| Severity | critical |
Who is affected
Countries where Nigeria Cameroon Submarine Cable System (NCSCS) 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 |
|---|---|---|---|
| Cameroon resilience index: 58 · moderate |
1 of 5 cables (20% of submarine diversity) | Ceiba-2, SAT-3/WASC, South Atlantic Inter Link (SAIL) +1 more | median 171 ms today vs 171 ms over 30 days (2 routes) - unchanged |
| Nigeria resilience index: 67 · moderate |
1 of 8 cables (13% of submarine diversity) | 2Africa, Africa Coast to Europe (ACE), Equiano +4 more | median 201 ms today vs 210 ms over 30 days (6 routes) - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Timeline
- Alert 2026080501: critical - ratio 9.15x
- Alert #165 improving: 2/3 consecutive OK
- Alert #165 resolved: RTT 20.61ms (baseline 20.08ms), 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 2026080501: Nigeria Cameroon Submarine Cable System (NCSCS). https://geocables.com/incident/2026080501
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=nigeria-cameroon-submarine-cable-system-ncscs" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>