North-West Cable System: latency up to 2× normal, 5 Sep 2026
What we measured
| Cable | North-West Cable System |
| Segment | Sydney, AU → Darwin, AU |
| Detected | 2026-09-05 11:33 UTC |
| Resolved | 2026-09-05 16:01 UTC |
| Duration | 4h 28m |
| Observed latency | 289.8 ms |
| Baseline | 153.8 ms · 2.03× |
| Increase | +103% |
| Severity | warning |
Who is affected
Countries where North-West 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 |
|---|---|---|---|
| Australia resilience index: 100 · resilient |
1 of 34 cables (3% of submarine diversity) | APX East, Asia Connect Cable-1 (ACC-1), Australia-Japan Cable (AJC) +30 more | no measurement today; median 250 ms over 30 days (492 routes) |
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 2026090508: warning - ratio 2.03x
- Alert #194 improving: 2/3 consecutive OK
- Alert #194 resolved: RTT 289.77ms (baseline 153.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.