On Tue, 3 Mar 2026, Hank Nussbacher via NANOG wrote:
We had F5 announce a /24 on our behalf. We then asked F5 to withdraw that /24. Route-views showed the /24 still being announced via an F5 path. F5 claims that route-views is incorrect and the route had been properly withdrawn. They state that public route collectors (including route-views) reflect what their individual collector peers are seeing at a given moment. Due to propagation timing, peer refresh intervals, and collector update cycles, visibility across different monitoring platforms is not always perfectly synchronized in real time.
It does take time for route updates to propagate, and I've seen some providers/platforms take what seems like unreasonable minutes to drop routes after origination has ceased...but if they're hanging around longer than that, odds are [extremely high], F5 is still leaking the route to someone who's propagating it to the Internet (or at least to route-views) in order for route-views to see it. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________