Arnaud, I am not sure what you mean by intimidation. I have no intent to intimidate anyone.
I merely point out the areas where you are mistaken in your statements and your accusation. > Even though the prefix is no longer seen in global routing table, it is been > seen by some route collectors. > > One route collector at RIPE Stat sees as shown in the picture as at now. Yes… Route collectors keep route data for a long time after the routes are withdrawn, especially if they do not get replaced with a conflicting announcement for the same prefix. That is the case here. The route hasn’t been present on any router for months. You are looking at historical data and acting like it is current data. > > [ picture] > And the ASPATH speaks for itself. Yes, that was the errant AS PATH months ago when the prefix was last announced. LOOK AT the BGPLAY link I sent. Even RIPE database shows that the data is historical and not current. > > Nonetheless, we are actively working to get those errant entries cleaned up. > Thank you for bringing them to our attention. > > Please let the community know when everything is cleaned. > Thank you Everything we can control has been cleaned. Seem my reply to Noah which will be next. Owen > > -- > Arnaud > > ... >> _______________________________________________ >> Community-Discuss mailing list >> [email protected] <mailto:[email protected]> >> https://lists.afrinic.net/mailman/listinfo/community-discuss >> <https://lists.afrinic.net/mailman/listinfo/community-discuss> >> _______________________________________________ >> Community-Discuss mailing list >> [email protected] <mailto:[email protected]> >> https://lists.afrinic.net/mailman/listinfo/community-discuss >> <https://lists.afrinic.net/mailman/listinfo/community-discuss> > > <IMG_20200529_074734_512.jpg>
_______________________________________________ Community-Discuss mailing list [email protected] https://lists.afrinic.net/mailman/listinfo/community-discuss
