Bosun cable: latency up to 2.3× normal, 5 Sep 2026
What we measured
| Cable | Bosun |
| Segment | Sydney, AU → Flying Fish Cove, CX |
| Detected | 2026-09-05 16:32 UTC |
| Resolved | 2026-09-12 04:03 UTC |
| Duration | 6d 11h |
| Observed latency | 199.8 ms |
| Baseline | 115.4 ms · 2.25× |
| Increase | +125% |
| Severity | warning |
Who is affected
Countries where Bosun 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) |
| Christmas Island resilience index: 41 · vulnerable |
1 of 4 cables (25% of submarine diversity) | Australia-Singapore Cable (ASC), Dhivaru, TalayLink | average 200 ms over the last day vs 295 ms over 30 days - faster |
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 kept the same route. Latency rose without a visible path change, which points at congestion or a fault on the existing route rather than a reroute.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026090509: warning - ratio 2.25x
- Alert #195 improving: 1/3 consecutive OK
- Alert #195 improving: 1/3 consecutive OK
- Alert #195 improving: 2/3 consecutive OK
- Alert #195 resolved: RTT 199.78ms (baseline 115.37ms), 6 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.