Apricot cable: latency up to 2.1× normal, 4 Sep 2026
What we measured
| Cable | Apricot |
| Segment | Sydney, AU → Davao, PH |
| Detected | 2026-09-04 12:31 UTC |
| Resolved | 2026-09-04 21:03 UTC |
| Duration | 8h 31m |
| Observed latency | 259.8 ms |
| Baseline | 181.2 ms · 2.12× |
| Increase | +112% |
| Severity | warning |
Who is affected
Countries where Apricot 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 |
|---|---|---|---|
| Guam resilience index: 83 · resilient |
1 of 19 cables (5% of submarine diversity) | Asia Connect Cable-1 (ACC-1), Asia-America Gateway (AAG) Cable System, Atisa +15 more | median 297 ms today vs 264 ms over 30 days (59 routes) - unchanged |
| Indonesia resilience index: 100 · resilient |
1 of 73 cables (1% of submarine diversity) | Asia Connect Cable-1 (ACC-1), Asia United Gateway East (AUG East), Australia-Singapore Cable (ASC) +69 more | median 230 ms today vs 203 ms over 30 days (1061 routes) - unchanged |
| Japan resilience index: 100 · resilient |
1 of 53 cables (2% of submarine diversity) | 5 Villages 6 Islands, APCN-2, Asia Direct Cable (ADC) +49 more | median 225 ms today vs 203 ms over 30 days (468 routes) - unchanged |
| Philippines resilience index: 100 · resilient |
1 of 26 cables (4% of submarine diversity) | APCN-2, Asia Connect Cable-1 (ACC-1), Asia Direct Cable (ADC) +22 more | median 284 ms today vs 244 ms over 30 days (102 routes) - slower |
| Singapore resilience index: 78 · resilient |
1 of 46 cables (2% of submarine diversity) | APCN-2, Asia Connect Cable-1 (ACC-1), Asia Direct Cable (ADC) +42 more | median 155 ms today vs 163 ms over 30 days (509 routes) - unchanged |
| Taiwan resilience index: 100 · resilient |
1 of 21 cables (5% of submarine diversity) | APCN-2, Asia Pacific Gateway (APG), Asia United Gateway East (AUG East) +17 more | median 9 ms today vs 147 ms over 30 days (129 routes) - 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 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 2026090401: warning - ratio 2.12x
- Alert #183 improving: 1/3 consecutive OK
- Alert #183 improving: 2/3 consecutive OK
- Alert #183 resolved: RTT 259.78ms (baseline 181.18ms), 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.