PGASCOM: 0.46× 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-05-31 23:02 UTC Alert 2026053101: warning — ratio 2x
• 2026-06-01 00:01 UTC Alert #130 improving: 1/3 consecutive OK
• 2026-06-01 00:32 UTC Alert #130 resolved: RTT 25.17ms (baseline 54.58ms), 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