Unisur: 1.81× 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-14 03:04 UTC Alert 2026071401: warning — ratio 2.05x
• 2026-07-14 06:33 UTC Alert #149 improving: 1/3 consecutive OK
• 2026-07-14 08:03 UTC Alert #149 improving: 1/3 consecutive OK
• 2026-07-14 12:34 UTC Alert #149 improving: 1/3 consecutive OK
• 2026-07-14 16:33 UTC Alert #149 improving: 1/3 consecutive OK
• 2026-07-15 00:37 UTC Alert #149 improving: 2/3 consecutive OK
• 2026-07-15 01:33 UTC Alert #149 resolved: RTT 10.58ms (baseline 5.85ms), 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