Lower Indian Ocean Network (LION): latency up to 2.4× normal, 10 Nov 2026
What we measured
| Cable | Lower Indian Ocean Network (LION) |
| Segment | Toamasina, MG → Terre Rouge, MU |
| Detected | 2026-11-10 21:01 UTC |
| Resolved | 2026-11-11 02:01 UTC |
| Duration | 4h 59m |
| Observed latency | 307.3 ms |
| Baseline | 154.3 ms · 2.37× |
| Increase | +137% |
| Severity | warning |
Who is affected
Countries where Lower Indian Ocean Network (LION) 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 |
|---|---|---|---|
| Madagascar resilience index: 75 · resilient |
1 of 5 cables (20% of submarine diversity) | 2Africa, Djibouti Africa Regional Express 1 (DARE 1), Eastern Africa Submarine System (EASSy) +1 more | median 253 ms today vs 219 ms over 30 days (127 routes) - slower |
| Mauritius resilience index: 68 · moderate |
1 of 5 cables (20% of submarine diversity) | Mauritius and Rodrigues Submarine Cable System (MARS), Meltingpot Indianoceanic Submarine System (METISS), SAFE +1 more | median 132 ms today vs 182 ms over 30 days (91 routes) - faster |
| Réunion resilience index: 46 · vulnerable |
1 of 4 cables (25% of submarine diversity) | Meltingpot Indianoceanic Submarine System (METISS), ReuNION, SAFE | median 74 ms today vs 69 ms over 30 days (45 routes) - 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).
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
Path analysis
Traffic changed route while latency was elevated. A reroute of this kind usually follows a fault somewhere on the original path.
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 2026111001: warning - ratio 2.37x
- Alert #248 improving: 2/3 consecutive OK
- Alert #248 resolved: RTT 307.3ms (baseline 154.28ms), 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.