T3: 1.6× baseline latency
What we measured
| Cable | T3 |
| Segment | Amanzimtoti, ZA → Baie Jacotet, MU |
| Detected | 2026-05-18 17:01 UTC |
| Resolved | 2026-05-18 19:01 UTC |
| Duration | 2h 0m |
| Observed latency | 123.6 ms |
| Baseline | 77.3 ms · 1.6× |
| Increase | +325% |
| Severity | critical |
Who is affected
Countries where T3 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 |
|---|---|---|---|
| Mauritius resilience index: 68 · moderate |
1 of 5 cables (20% of submarine diversity) | Lower Indian Ocean Network (LION), Mauritius and Rodrigues Submarine Cable System (MARS), Meltingpot Indianoceanic Submarine System (METISS) +1 more | median 257 ms today vs 268 ms over 30 days (6 routes) - unchanged |
| South Africa resilience index: 100 · resilient |
1 of 13 cables (8% of submarine diversity) | 2Africa, Africa Coast to Europe (ACE), Djibouti Africa Regional Express 1 (DARE 1) +9 more | median 226 ms today vs 210 ms over 30 days (22 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 changed route and the original path stopped responding. This is the pattern a real cable break produces.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026051801: warning - ratio 2.22x
- Alert #121 improving: 2/3 consecutive OK
- Alert #121 resolved: RTT 123.6ms (baseline 77.31ms), 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.