On Thu, Apr 22, 2021 at 01:24:54AM +0200, Job Snijders via NANOG wrote: [...]
Another one is http://lg.ring.nlnog.net/prefix_detail/lg01/ipv6?q=2a0b:6b86:d24::/48
2a0b:6b86:d24::/48 via: BGP.as_path: 201701 9002 6939 42615 212232 BGP.as_path: 34927 9002 6939 42615 212232 BGP.as_path: 207960 34927 9002 6939 42615 212232 BGP.as_path: 44103 50673 9002 6939 42615 212232 BGP.as_path: 208627 207910 34927 9002 6939 42615 212232 BGP.as_path: 3280 34927 9002 6939 42615 212232 BGP.as_path: 206628 34927 9002 6939 42615 212232 BGP.as_path: 208627 207910 34927 9002 6939 42615 212232 (first announced March 24th, last withdrawn March 24th, 2021)
[...]
I checked the AS 6939 Looking glass, but the d24::/48 route is not visible in the http://lg.he.net/ web interface. This leads me to believe the the route got stuck somewhere along way in either of 201701, 204092, 206628, 207910, 207960, 208627, 3280, 34927, 35280, 44103, 50673, 57199, and/or 9002.
9002. Hit by Juniper PR1562090, route stuck in DeletePending.. Workaround applied, sessions with 6939 restarted, route is gone.