Guam Okinawa Kyushu Incheon (GOKI): 1.94× baseline latency

What we measured

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

• 2026-07-05 21:32 UTC Alert 2026070503: warning — ratio 2.92x
• 2026-07-06 00:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-06 06:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-06 14:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-06 18:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 00:04 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 06:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 08:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 12:34 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 17:32 UTC Alert #146 improving: 2/3 consecutive OK
• 2026-07-07 18:32 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-07 22:02 UTC Alert #146 improving: 2/3 consecutive OK
• 2026-07-08 00:33 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-08 10:01 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-08 11:02 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-08 12:01 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-08 13:02 UTC Alert #146 improving: 1/3 consecutive OK
• 2026-07-08 14:01 UTC Alert #146 improving: 2/3 consecutive OK
• 2026-07-08 14:32 UTC Alert #146 resolved: RTT 99.09ms (baseline 51.01ms), 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.

How to cite

Embed this map