BCS North - Phase 2: 0.86× baseline latency

What we measured

Path analysis

Traffic changed route while latency was elevated. A reroute of this kind usually follows a fault somewhere on the original path.

Cross-probe verdict. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.

Timeline

• 2026-05-07 23:01 UTC Alert 2026050703: warning — ratio 2.16x
• 2026-05-08 04:30 UTC Alert #112 improving: 1/3 consecutive OK
• 2026-05-08 05:01 UTC Alert #112 improving: 2/3 consecutive OK
• 2026-05-08 05:30 UTC Alert #112 resolved: RTT 79.65ms (baseline 92.2ms), 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