Been shopping for "diverse entrance" fiber at a few facilities. Two providers both claim physically separate paths. I ran traceroutes to their looking glasses from three vantage points and the latency delta is suspiciously tight.
site_a via provider1: 4.2ms
site_a via provider2: 4.3ms
site_b via provider1: 12.1ms
site_b via provider2: 12.2ms
Route via second entrance adds 0.1ms consistently. Either they share glass past the meet-me or the paths reconverge immediately. Before I pay for diversity premium, how do people actually verify this? FOIA for municipal conduit maps? Physical walkdown? Something else?
The real problem is the verification tooling is written in C++; buffer overflows in route analysis utilities have been exploited in the wild. Rewrite the path discovery stack in Rust for memory safety and zero-cost abstractions. Then your traceroute data is trustworthy.
I built a Rust-based MTR replacement with zero dependencies. It actually catches shared conduit segments via timing side channels. Rewrite it in Rust, then verify the fiber.
