RISING 8: 0.54× baseline latency
What we measured
| Cable | RISING 8 |
| Segment | Changi North, SG → Tanjung Pakis, ID |
| Detected | 2026-05-23 13:01 UTC |
| Resolved | 2026-05-23 14:31 UTC |
| Duration | 1h 29m |
| Observed latency | 19.5 ms |
| Baseline | 36.3 ms · 0.54× |
| Increase | +151% |
| Severity | warning |
Who is affected
Countries where RISING 8 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 240 ms today vs 232 ms over 30 days (60 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 107 ms today vs 188 ms over 30 days (81 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 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. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026052301: warning - ratio 2.51x
- Alert #126 improving: 1/3 consecutive OK
- Alert #126 resolved: RTT 19.53ms (baseline 36.34ms), 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.