Can I recommend the following web site to the list? http://www.cidr-report.org Lots of interesting stats about route announcements on the core of the net in particular those which are less than optimal. I'd suggest that all of us here who announce prefixes by BGP should at least go the the section at the very bottom of the page and generate the report for the AS numbers we're responsible for and take some action on the output if necessary. For example, Citylink's office network uses AS23754 and the report shows the following: (http://www.cidr-report.org/cgi-bin/as-report?as=as23754 will give a better formatted view) --- Announced Prefixes Rank AS Type Originate Addr Space (pfx) Transit Addr space (pfx) Description 8920 AS23754 ORIGIN Originate: 2560 /20.68 Transit: 0 /0.00 CITYLINK-AS-NZ Citylink Aggregation Suggestions This report does not take into account conditions local to each origin AS in terms of policy or traffic engineering requirements, so this is an approximate guideline as to aggregation possibilities. Rank AS AS Name Current Wthdw Aggte Annce Redctn % 12949 AS23754 CITYLINK-AS-NZ Citylink 4 0 0 4 0 0.00% AS23754: CITYLINK-AS-NZ Citylink Prefix (AS Path) Aggregation Action 198.48.0.0/22 1221 2764 3643 7657 23754 202.8.44.0/22 1221 2764 3643 7657 23754 202.37.19.0/24 1221 2764 3643 7657 23754 203.118.144.0/24 1221 2764 3643 7657 23754 Advertisements that are fragments of the original RIR allocation (more specifics) originated by this AS. AS23754 1 More Specifics 4 Total Advertisements CITYLINK-AS-NZ Citylink 203.118.144.0/24 (203.118.128.0/18) --- So it looks like I need to check with IHUG, our upstream, and see why they're announcing our particular subnet of 203.118.128.0/18 as well as the superblock. I've just come back from APRICOT where I saw a presentation that indicated that if we all were to get this sort of thing sorted out we'd reduce the size of the global routing table by 30% Let's get the NZ annoucements sorted at least!