Maybe? Never been an issue before. In this case the route does have a depref community on Telia hence why one wouldn’t expect it via the same path, but the other ghost route in question never had anything similar.
Matt > On Nov 15, 2020, at 23:07, Olivier Benghozi <olivier.bengh...@wifirst.fr> > wrote: > > One of the routing gears on the path don't like the large community inside > those routes maybe ? :) > By the way we currently see 2620:6e:a002::/48 at LINX LON1 from Choopa and > HE... > >> Le 16 nov. 2020 à 04:44, Matt Corallo <na...@as397444.net> a écrit : >> >> Yea, I did try that on that test prefix but it just stuck around anyway.. I >> don't care too much, its just some stale test prefix. >> >> Sadly, I now see it again with 2620:6e:a002::/48, which, somewhat more >> impressively, is now generating a routing loop Ashburn <-> NYC, and has >> always been announced from other places has was dropped/re-announced as wel. >> >> Must just be something with my particular prefixes, oh well. >> >> Matt >> >>> On 11/15/20 10:40 PM, Olivier Benghozi wrote: >>> Probably a ghost route. Such thing happens :( >>> https://labs.ripe.net/Members/romain_fontugne/bgp-zombies >>> Their (nice) LG shows that it's still advertised from a router of theirs in >>> Frankfurt (iBGP next hop ::ffff:2.255.251.224 – so by the way they use 6PE). >>> Your best option would probably be to re-advertise the exact same prefix, >>> then re-withdraw it, then yell at Telia's NOC if it fails... >>> Some years ago we experienced something similar (it was a router of TI >>> Sparkle still advertising a prefix of us in Asia to their clients, that >>> they were previously receiving from our former transit GTT – we were >>> advertising it in Europe...). >>>> Le 16 nov. 2020 à 02:58, Matt Corallo <na...@as397444.net> a écrit : >>>> >>>> Has anyone else experienced issues where Telia won't withdraw (though will >>>> happily accept an overriding) prefixes for the past week, at least? >>>> >>>> eg 2620:6e:a003::/48 was a test prefix and should not now appear in any >>>> DFZ, has not been announced for a few days at least, but shows up in >>>> Telia's LG and RIPE RIS as transiting Telia. Telia's LG traceroute doesn't >>>> of course, go anywhere, traces die immediately after a hop or with a !N. >>>> >>>> Wouldn't be a problem except that I needed to withdraw another route due >>>> to a separate issue which wouldn't budge out of Telia's tables until it >>>> was replaced with something else of higher pref. >>>> >>>> Matt >
