Meltingpot Indianoceanic Submarine System (METISS): 1.01× baseline latency
What we measured
| Cable | Meltingpot Indianoceanic Submarine System (METISS) |
| Segment | Baie du Tombeau, MU → Umbogintwini, ZA |
| Detected | 2026-05-19 07:01 UTC |
| Resolved | 2026-05-19 15:01 UTC |
| Duration | 8h 0m |
| Observed latency | 65.6 ms |
| Baseline | 65.1 ms · 1.01× |
| Increase | +232% |
| Severity | warning |
Who is affected
Countries where Meltingpot Indianoceanic Submarine System (METISS) 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 193 ms today vs 196 ms over 30 days (3 routes) - unchanged |
| 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), SAFE +1 more | median 257 ms today vs 268 ms over 30 days (6 routes) - unchanged |
| Réunion resilience index: 42 · vulnerable |
1 of 3 cables (33% of submarine diversity) | Lower Indian Ocean Network (LION), SAFE | average 132 ms over the last day vs 150 ms over 30 days - 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 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 2026051901: warning - ratio 3.32x
- Alert #122 improving: 1/3 consecutive OK
- Alert #122 improving: 2/3 consecutive OK
- Alert #122 resolved: RTT 65.58ms (baseline 65.05ms), 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.