BCS North - Phase 1: 0.27× 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. Some probes saw the degradation and others did not, which usually means a partial or regional effect.

Timeline

• 2026-04-17 15:01 UTC Alert 2026041705: warning — ratio 2.17x
• 2026-04-17 16:00 UTC Alert #83 improving: 1/3 consecutive OK
• 2026-04-17 16:31 UTC Alert #83 resolved: RTT 10.14ms (baseline 37.45ms), 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