Matrix Cable System: latency up to 2.2× normal, 28 Jul 2026
What we measured
| Cable | Matrix Cable System |
| Segment | Jakarta, ID → Changi South, SG |
| Detected | 2026-07-28 17:01 UTC |
| Resolved | 2026-08-07 15:03 UTC |
| Duration | 9d 22h |
| Observed latency | 13 ms |
| Baseline | 15.8 ms · 2.24× |
| Increase | +124% |
| Severity | warning |
Who is affected
Countries where Matrix Cable System 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 |
|---|---|---|---|
| Indonesia resilience index: 100 · resilient |
1 of 73 cables (1% of submarine diversity) | Apricot, Asia Connect Cable-1 (ACC-1), Asia United Gateway East (AUG East) +69 more | median 215 ms today vs 203 ms over 30 days (1224 routes) - unchanged |
| Singapore resilience index: 78 · resilient |
1 of 46 cables (2% of submarine diversity) | APCN-2, Apricot, Asia Connect Cable-1 (ACC-1) +42 more | median 191 ms today vs 164 ms over 30 days (600 routes) - slower |
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. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026072801: warning - ratio 2.24x
- Alert #159 improving: 2/3 consecutive OK
- Alert #159 improving: 1/3 consecutive OK
- Alert #159 improving: 1/3 consecutive OK
- Alert #159 improving: 1/3 consecutive OK
- Alert #159 improving: 1/3 consecutive OK
- Alert #159 improving: 2/3 consecutive OK
- Alert #159 improving: 2/3 consecutive OK
- Alert #159 resolved: RTT 12.96ms (baseline 15.77ms), 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.