BCS North - Phase 2: 0.9× 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. Multiple independent probes saw the same degradation, so this was not a local artefact.

Timeline

• 2026-05-08 13:01 UTC Alert 2026050801: warning — ratio 2.46x
• 2026-05-08 14:00 UTC Alert #113 improving: 1/3 consecutive OK
• 2026-05-08 15:01 UTC Alert #113 improving: 1/3 consecutive OK
• 2026-05-08 15:31 UTC Alert #113 improving: 2/3 consecutive OK
• 2026-05-08 16:31 UTC Alert #113 resolved: RTT 32.93ms (baseline 36.45ms), 4 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