Just an FYI- Please see: http://engr.ans.net/route-dumps/problem-summary.html 51923 prefixes in the IRR that have not been announced in the last 3 months. 7328 registered and never announced This is the list of prefixes that are registered in the IRR but have not been announced in the last three months. If these are no longer used, deleting the route objects is very easy. <http://engr.ans.net/route-dumps/orphans.html> 44595 never announced but aggregated This is the list of prefixes that are registered in the IRR but have not been announced in the last three months but are likely to still be reachable since and aggregate is announced. The route objects can be deleted, marked as withdrawn, or using RPSL, the aggregate can be marked to limit the scope of the more specific routes. <http://engr.ans.net/route-dumps/leaks.html> Reports are broken down by origin AS: http://engr.ans.net/route-dumps/orphans.html There were 7328 prefixes that are registered in the IRR but have not been announced and recorded in the route dumps taken during the past 3 months. Route dumps are taken at all border routers within ANS every 1-2 days. Below is the set of 914 origin AS under which these route objects are registered. [ ... table follows ... ] http://engr.ans.net/route-dumps/leaks.html There were 44595 prefixes that are registered in the IRR but have not been announced and recorded in the route dumps taken during the past 3 months, but are covered by an announced aggregate. These prefixes are likely to be due to previously registered and announced prefixes that are now aggregated and no longer individually announced. Route dumps are taken at all border routers within ANS every 1-2 days. Below is the set of 1417 origin AS under which these route objects are registered. [ ... table follows ... ] Please clean up your own origin AS. We'll be cleaning up the no longer announced prefixes in our origin AS and customer AS. Thanks in advance, Curtis ps- flames to /dev/null please.