Incident report · 2026031505
Apricot: 2.38× baseline latency
Resolved · 8h 58m
What we measured
| Cable | Apricot |
| Segment | Singapore, SG → Tokyo, JP |
| Detected | 2026-03-15 20:32 UTC |
| Resolved | 2026-03-16 05:31 UTC |
| Duration | 8h 58m |
| Observed latency | 186.6 ms |
| Baseline | 78.4 ms · 2.38× |
| Increase | +168% |
| Severity | warning |
Path analysis
No usable traceroute data for this window.
Cross-probe verdict. The effect was confined to a narrow set of paths, so a cable-wide fault is unlikely.
Timeline
- Alert #17: warning — Minamiboso
- Alert #17 resolved: Minamiboso
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.
How to cite
GeoCables (2026). Incident 2026031505: Apricot. https://geocables.com/incident/2026031505
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=apricot" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>