From cscora at dev.apnic.net Thu Nov 2 13:14:33 2000 From: cscora at dev.apnic.net (Routing Analysis) Date: Fri, 3 Nov 2000 04:14:33 +1000 (EST) Subject: ARIN Region Weekly Routing Report Message-ID: <200011021814.EAA08775@dev.apnic.net> This is an automated weekly mailing sent to the ARIN RTMA WG e-mail list describing the state of the Internet Routing Table in North and South America and Southern Africa. Daily listings are sent to bgp-stats at lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Americas and Southern Africa Report 03 Nov, 2000 Analysis Summary ---------------- BGP routing table entries examined: 89629 Origin ASes present in the Internet Routing Table: 8896 Origin ASes announcing only one prefix: 3033 Transit ASes present in the Internet Routing Table: 1235 Average AS path length visible in the Internet Routing Table: 5.5 Max AS path length visible: 15 Illegal AS announcements present in the Routing Table: 6 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 0 Number of addresses announced to Internet: 1168799460 Equivalent to 69 /8s, 170 /16s and 118 /24s Percentage of available address space announced: 31.5 Percentage of allocated address space announced: 61.8 Percentage of available address space allocated: 51.0 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 61999 Prefixes being announced from the ARIN address blocks: 43214 ARIN Region origin ASes present in the Internet Routing Table: 5389 ARIN Region origin ASes announcing only one prefix: 1514 ARIN Region transit ASes present in the Internet Routing Table: 603 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 167316616 Equivalent to 9 /8s, 249 /16s and 12 /24s Percentage of available ARIN address space announced: 76.7 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 19455 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2107 3421 UUNET Technologies, Inc. 7018 893 3025 AT&T 1 887 4535 BBN Planet 1239 704 1628 Sprint ICM-Inria 7046 695 508 UUNET Technologies, Inc. 2914 691 1329 Verio, Inc. 705 688 39 UUNET Technologies, Inc. 816 605 143 UUNET Canada4 174 603 2717 PSINet Inc. 3561 567 1366 Cable & Wireless USA 8013 518 64 PSINet Ltd. Canada 209 508 553 Qwest 3549 479 426 Frontier GlobalCenter 271 454 378 BCnet Backbone 3908 446 290 Supernet, Inc. 4293 433 55 Cable & Wireless USA 2548 428 546 Digital Express Group, Inc. 3602 423 74 Sprint Canada 690 340 19 Merit Network Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2107 3421 UUNET Technologies, Inc. 7018 893 3025 AT&T 1 887 4535 BBN Planet 1221 752 979 Telstra 1239 704 1628 Sprint ICM-Inria 7046 695 508 UUNET Technologies, Inc. 2914 691 1329 Verio, Inc. 705 688 39 UUNET Technologies, Inc. 816 605 143 UUNET Canada4 174 603 2717 PSINet Inc. 3561 567 1366 Cable & Wireless USA 8013 518 64 PSINet Ltd. Canada 209 508 553 Qwest 3549 479 426 Frontier GlobalCenter 271 454 378 BCnet Backbone 3908 446 290 Supernet, Inc. 4293 433 55 Cable & Wireless USA 2548 428 546 Digital Express Group, Inc. 2764 426 129 connect.com.au pty ltd List of Illegal AS's (Global) ----------------------------- Bad AS Designation Network Transit AS Description 64750 PRIVATE 63.67.32.0/24 15218 Communications 65519 PRIVATE 64.124.60.0/24 6461 AboveNet Communicati 65519 PRIVATE 64.124.61.0/24 6461 AboveNet Communicati 65000 PRIVATE 64.209.92.0/24 14051 Roseville Telephone 65000 PRIVATE 64.209.95.0/24 14051 Roseville Telephone 57158 RESERVED 210.56.192.0/20 4628 Pacific Internet Pte Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:21 /9:4 /10:5 /11:9 /12:32 /13:56 /14:178 /15:287 /16:6677 /17:943 /18:1888 /19:6027 /20:3909 /21:3884 /22:5810 /23:7523 /24:51972 /25:89 /26:123 /27:44 /28:28 /29:60 /30:24 /31:0 /32:36 End of report From cjw at remarque.org Thu Nov 2 16:18:38 2000 From: cjw at remarque.org (CJW) Date: Thu, 02 Nov 2000 13:18:38 -0800 Subject: Please send me your comments Message-ID: <200011022118.NAA05559@pox.remarque.org> Hi everyone out there in rtma-land, I think it's time I try again to get you all involved. I'd like to come up with a list of agenda topics and perhaps meet as a working group at the next ARIN meeting. So far some topics I can think of are: ways to summarize the routing table info: a) discuss Scott Marcus's info on AS number depletion (perhaps compare it to Geoff Huston's data presented last week at the APNIC meeting) b) how do assigned ASNs compare to the ones showing up in the routing table? c) how many prefixes are being assigned per ASN? d) perhaps compare registered prefixes and length to advertisements. For example how many advertisements are generated for each assigned prefix? e) perhaps query experts on when the existing network equipment will no longer be able to handle the size of the routing table (not just # of prefixes but number of paths, not just amount of memory required, but what happens if there are flaps) Any other thoughts? What info should we be gathering? (if any) Thanks for your help! ---Cathy From kimh at arin.net Thu Nov 2 16:05:40 2000 From: kimh at arin.net (Kim Hubbard) Date: Thu, 2 Nov 2000 16:05:40 -0500 Subject: Please send me your comments References: <200011022118.NAA05559@pox.remarque.org> Message-ID: <001301c04510$a9151ba0$ccfc95c0@arin.net> Cathy, I think it's important to first define exactly what our goals are, i.e., what questions are we trying to answer or what problems need solving. Do you want to start with one topic, i.e., AS depletion or broaden it to include the size of the routing table, etc. Once these are defined, it should be easier to decide how to go about gathering the info. Kim ----- Original Message ----- From: CJW To: Cc: Sent: Thursday, November 02, 2000 4:18 PM Subject: Please send me your comments > Hi everyone out there in rtma-land, > > I think it's time I try again to get you all involved. I'd like to > come up with a list of agenda topics and perhaps meet as a working group > at the next ARIN meeting. So far some topics I can think of are: > > ways to summarize the routing table info: > a) discuss Scott Marcus's info on AS number depletion > (perhaps compare it to Geoff Huston's data presented > last week at the APNIC meeting) > b) how do assigned ASNs compare to the ones showing up > in the routing table? > c) how many prefixes are being assigned per ASN? > d) perhaps compare registered prefixes and length to > advertisements. For example how many advertisements > are generated for each assigned prefix? > e) perhaps query experts on when the existing network > equipment will no longer be able to handle the size of > the routing table (not just # of prefixes but number of > paths, not just amount of memory required, but what happens > if there are flaps) > > Any other thoughts? What info should we be gathering? (if any) > > Thanks for your help! > ---Cathy > > > > > From smarcus at genuity.com Thu Nov 2 18:44:51 2000 From: smarcus at genuity.com (J. Scott Marcus) Date: Thu, 02 Nov 2000 18:44:51 -0500 Subject: Please send me your comments In-Reply-To: <200011022118.NAA05559@pox.remarque.org> Message-ID: <3.0.5.32.20001102184451.00aaeab0@pobox3.genuity.com> At 13:18 11/02/2000 -0800, CJW wrote: >Hi everyone out there in rtma-land, > >I think it's time I try again to get you all involved. I'd like to >come up with a list of agenda topics and perhaps meet as a working group >at the next ARIN meeting. So far some topics I can think of are: > >ways to summarize the routing table info: > a) discuss Scott Marcus's info on AS number depletion > (perhaps compare it to Geoff Huston's data presented > last week at the APNIC meeting) > b) how do assigned ASNs compare to the ones showing up > in the routing table? I think that there are about 16,000 assigned between the three RIRs? The number active in the routing tables is 8,896 per Phillip Smith's data; thus, a ratio of just under 2:1. Anecdotally, I have heard it claimed that this number was much higher a few years ago, perhaps as high as 4:1. Has anybody done the arithmetic? > c) how many prefixes are being assigned per ASN? Per Smith's data, 89,629 entries in the routing table versus 8,896 origin ASes present in the Internet routing table. Thus, a ratio of 10:1 in comparing routing table entries to ASes assigned (which is not exactly what you asked for). I would be curious to know the trend in this ratio - it seems to me that conservative allocation practices will tend to push it higher, while CIDR pushes it much lower. And it may have a tendency to decrease, other things being equal, as the scale of the Internet increases. So it is being pushed in opposite directions by different forces... > d) perhaps compare registered prefixes and length to > advertisements. For example how many advertisements > are generated for each assigned prefix? > e) perhaps query experts on when the existing network > equipment will no longer be able to handle the size of > the routing table (not just # of prefixes but number of > paths, not just amount of memory required, but what happens > if there are flaps) > >Any other thoughts? What info should we be gathering? (if any) From randy at psg.com Fri Nov 3 01:36:23 2000 From: randy at psg.com (Randy Bush) Date: Thu, 02 Nov 2000 22:36:23 -0800 Subject: Please send me your comments References: <200011022118.NAA05559@pox.remarque.org> Message-ID: > Any other thoughts? What info should we be gathering? (if any) perhaos ask idr to look at increasing the size of the asn so this discussion becomes unnecessary. randy From pfs at cisco.com Fri Nov 3 02:23:10 2000 From: pfs at cisco.com (Philip Smith) Date: Fri, 03 Nov 2000 17:23:10 +1000 Subject: Please send me your comments In-Reply-To: <200011022118.NAA05559@pox.remarque.org> Message-ID: <5.0.0.25.2.20001103165350.00a64c60@lint.cisco.com> Hi Cathy, At 13:18 02/11/00 -0800, CJW wrote: >Hi everyone out there in rtma-land, > >I think it's time I try again to get you all involved. I'd like to >come up with a list of agenda topics and perhaps meet as a working group >at the next ARIN meeting. So far some topics I can think of are: > >ways to summarize the routing table info: > a) discuss Scott Marcus's info on AS number depletion > (perhaps compare it to Geoff Huston's data presented > last week at the APNIC meeting) > b) how do assigned ASNs compare to the ones showing up > in the routing table? > c) how many prefixes are being assigned per ASN? A study of ASNs usage/assignment/profile/depletion would be good. And like Randy suggested, a hint in the direction of idr to move from 16 bit ASNs to >16 bit ASNs within the next 4 years or so would be useful. Failing that, efforts to reclaim the ASNs assigned but unannounced? > d) perhaps compare registered prefixes and length to > advertisements. For example how many advertisements > are generated for each assigned prefix? It would be interesting to see this,... It would prove that the degree of multihoming is increasing and dare I say the level of aggregation clue is decreasing? > e) perhaps query experts on when the existing network > equipment will no longer be able to handle the size of > the routing table (not just # of prefixes but number of > paths, not just amount of memory required, but what happens > if there are flaps) I really think the only way we are going to find this out is by trying it. We all can do theoretical studies but real life tends to throw up its own little tests... If anyone has done analysis work of BGP convergence rates versus CPU for the major platforms, it would be interesting to hear... >Any other thoughts? What info should we be gathering? (if any) > >Thanks for your help! >---Cathy Other ideas... - It might be interesting to see information or summaries about the number of BGP announcements per minute in various parts of the "default free zone". And a summary of what caused them (infrastructure/power switch/human error) - or at least an attempt. Even an attempt to correlate that BGP churning in different parts of the Internet. RIPE NCC's RIS springs to mind as a possible site which is gathering this sort of info (but I don't think they are analysing this particular aspect). - Might be worth discussing the importance of BGP flap damping, if any? Like how many providers are doing so, what parameters are they using. Comparing route processing performance on non-flap damped networks with those which have flap damping at the edges... RIPE-210 documents recommendations from RIPE Routing WG, but maybe the net needs to be widened to figure out if these are satisfactory, could be improved, &c... Can vendors to anything to improve in this arena - can BGP be improved any to improve stability... etc. - Maybe expert discussion on why appearing in Tony's CIDR Report no longer has the stigma it used to have? Does it even matter any more? (Most new ISPs have never heard of it, and even then many don't understand what it is trying to achieve...) Do we just assume that the whole routing thing will keep on working, just keep beating on the vendors to produce ever bigger faster pricier boxes to keep up? :) We started talking about this here in Brisbane last week, might be worth carrying it on...? some ideas..., philip -- From henk at ripe.net Fri Nov 3 05:05:59 2000 From: henk at ripe.net (Henk Uijterwaal (RIPE-NCC)) Date: Fri, 3 Nov 2000 11:05:59 +0100 (CET) Subject: Please send me your comments In-Reply-To: <5.0.0.25.2.20001103165350.00a64c60@lint.cisco.com> Message-ID: Philip, Cathy, others, On Fri, 3 Nov 2000, Philip Smith wrote: > At 13:18 02/11/00 -0800, CJW wrote: > >Hi everyone out there in rtma-land, > > > >I think it's time I try again to get you all involved. I'd like to > >come up with a list of agenda topics and perhaps meet as a working group > >at the next ARIN meeting. So far some topics I can think of are: > > > >ways to summarize the routing table info: > > c) how many prefixes are being assigned per ASN? > > A study of ASNs usage/assignment/profile/depletion would be good. [...] > Failing that, efforts to reclaim the ASNs assigned but unannounced? We don't have statistics on this (yet), but we do have a tool a tool to check if an ASN assigned is actually seen by one of our RIS route-collectors: http://abcoude.ripe.net/ris/asinuse.cgi This is a prototype with very little documentation. It has been used by the RIPE NCC registration service dept. for a few months to check if ASN's are actually being used before assigning new ones. Based on their experience, we'll improve the tool in the near future. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal at ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk Singel 258 Phone: +31.20.535-4414, Fax -4445 1016 AB Amsterdam Home: +31.20.4195305 The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ A man can take a train and never reach his destination. (Kerouac, well before RFC2780). From routh at us.ibm.com Fri Nov 3 10:55:02 2000 From: routh at us.ibm.com (Richard Routh/Tampa/Contr/AT&T/IJV) Date: Fri, 3 Nov 2000 10:55:02 -0500 Subject: Please send me your comments Message-ID: Hello, I apologize for not being privy to all the preceding conversations regarding routing. As I have recently joined, I thought to add my two cents worth here. ( Ok, I rely heavily on Inflation here!! ) -There are limits to the 'real-estate' network devices use in a store and forward approach to networking. -The protocols used can fill up this memory space very quickly if prudent address space or routing tables are not configured. -Network 'Flapping' can and does threaten dynamic routing protocols. -Vendor specific protocols can jeopardize network stability as they tend to be 'chatty' ( i.e. AppleTalk, Novell IPX ) -Vendor hardware must be thoroughly checked for the routing table size capabilities across the network as the smallest storage area wins If I can clarify this for anyone please respond and I will gladly review this. Mit Freundlichen Gr?ssen/Kind Regards/Met Vreundlijke Groet, Richard Routh ABS - Network Capacity, Performance and Tuning Vox: 863-965-7773 Fax: 209-882-9276 Email: rrouth at att.com In the middle of difficulty lies opportunity. - Albert Einstein CJW @arin.net on 11/02/2000 04:18:38 PM Please respond to cjw at remarque.org Sent by: rtma-request at arin.net To: rtma at arin.net cc: gih at telstra.net Subject: Please send me your comments Hi everyone out there in rtma-land, I think it's time I try again to get you all involved. I'd like to come up with a list of agenda topics and perhaps meet as a working group at the next ARIN meeting. So far some topics I can think of are: ways to summarize the routing table info: a) discuss Scott Marcus's info on AS number depletion (perhaps compare it to Geoff Huston's data presented last week at the APNIC meeting) b) how do assigned ASNs compare to the ones showing up in the routing table? c) how many prefixes are being assigned per ASN? d) perhaps compare registered prefixes and length to advertisements. For example how many advertisements are generated for each assigned prefix? e) perhaps query experts on when the existing network equipment will no longer be able to handle the size of the routing table (not just # of prefixes but number of paths, not just amount of memory required, but what happens if there are flaps) Any other thoughts? What info should we be gathering? (if any) Thanks for your help! ---Cathy From byans at ugo.com Fri Nov 3 11:23:30 2000 From: byans at ugo.com (Bryan Socha) Date: Fri, 3 Nov 2000 11:23:30 -0500 Subject: Please send me your comments Message-ID: <51B21895B6BE7745A6761CEFEC6088A8063E92@ugomail.ugo.com> I finally am at a company that welcomes me to get involved and the time to actually attend meetings so I'm happy to finally be able to get involved... I agree with some other people to attempt to figure out what the goal of the working group will be so it can be decided how to collect the data we need to analyze the situation. Something I wanted to throw out at this point... Has anyone ever looked at the ability to reclaim old asns that will never be used again? -----Original Message----- From: CJW [mailto:cjw at remarque.org] Sent: Thursday, November 02, 2000 4:19 PM To: rtma at arin.net Cc: gih at telstra.net Subject: Please send me your comments Hi everyone out there in rtma-land, I think it's time I try again to get you all involved. I'd like to come up with a list of agenda topics and perhaps meet as a working group at the next ARIN meeting. So far some topics I can think of are: ways to summarize the routing table info: a) discuss Scott Marcus's info on AS number depletion (perhaps compare it to Geoff Huston's data presented last week at the APNIC meeting) b) how do assigned ASNs compare to the ones showing up in the routing table? c) how many prefixes are being assigned per ASN? d) perhaps compare registered prefixes and length to advertisements. For example how many advertisements are generated for each assigned prefix? e) perhaps query experts on when the existing network equipment will no longer be able to handle the size of the routing table (not just # of prefixes but number of paths, not just amount of memory required, but what happens if there are flaps) Any other thoughts? What info should we be gathering? (if any) Thanks for your help! ---Cathy From byans at ugo.com Fri Nov 3 13:17:55 2000 From: byans at ugo.com (Bryan Socha) Date: Fri, 3 Nov 2000 13:17:55 -0500 Subject: Please send me your comments Message-ID: <51B21895B6BE7745A6761CEFEC6088A8063E98@ugomail.ugo.com> Maybe what 1 goal should be is defining when it is safe to reassign the number to someone else.. -----Original Message----- From: Shane Kerr [mailto:shane at ripe.net] Sent: Friday, November 03, 2000 11:58 AM To: Bryan Socha Cc: rtma at arin.net; gih at telstra.net Subject: Re: Please send me your comments On Fri, Nov 03, 2000 at 11:23:30AM -0500, Bryan Socha wrote: > I finally am at a company that welcomes me to get involved and the time to > actually attend meetings so I'm happy to finally be able to get involved... > > I agree with some other people to attempt to figure out what the goal of the > working group will be so it can be decided how to collect the data we need > to analyze the situation. > > Something I wanted to throw out at this point... Has anyone ever looked at > the ability to reclaim old asns that will never be used again? This was briefly mentioned. :) I think it's a good idea, although "will never be used again" may be hard to determine. What I wonder is whether can we get a list of ASN's that are agreeable to most everybody as a definitive list of advertised? Shane From cjw at remarque.org Fri Nov 3 14:58:18 2000 From: cjw at remarque.org (Cathy Wittbrodt) Date: Fri, 03 Nov 2000 11:58:18 -0800 Subject: Please send me your comments In-Reply-To: Message from Randy Bush of "Thu, 02 Nov 2000 22:36:23 PST." Message-ID: <200011031958.LAA17109@pox.remarque.org> Scott Marcus is going to be doing just that at IETF in a couple of weeks. Thanks! ---CJ From: Randy Bush Subject: Re: Please send me your comments > Any other thoughts? What info should we be gathering? (if any) perhaos ask idr to look at increasing the size of the asn so this discussion becomes unnecessary. randy From pfs at cisco.com Wed Nov 8 05:22:17 2000 From: pfs at cisco.com (Philip Smith) Date: Wed, 08 Nov 2000 20:22:17 +1000 Subject: Update to weekly routing analysis summary Message-ID: <5.0.0.25.2.20001108202146.00a37450@lint.cisco.com> Hi, This is to inform you of a small modification to my weekly posting to this list. The "List of Illegal ASes" in the report has been replaced with the "List of Unregistered ASes". Basically this includes the previous private AS and reserved AS announcements, but adds to it the list of ASes announced for which there is no registration information contained in APNIC, ARIN, RIPE NCC, or DDN NIC (US Military) databases. At first run there are three new ASes appearing in this list, in addition to the quantity of private ASes being leaked to the Internet. They are 1877, 2027 and 5757. Any comments or feedback welcome, best wishes! philip -- From cscora at dev.apnic.net Thu Nov 9 13:02:57 2000 From: cscora at dev.apnic.net (Routing Analysis) Date: Fri, 10 Nov 2000 04:02:57 +1000 (EST) Subject: ARIN Region Weekly Routing Report Message-ID: <200011091802.EAA17919@dev.apnic.net> This is an automated weekly mailing sent to the ARIN RTMA WG e-mail list describing the state of the Internet Routing Table in North and South America and Southern Africa. Daily listings are sent to bgp-stats at lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Americas and Southern Africa Report 10 Nov, 2000 Analysis Summary ---------------- BGP routing table entries examined: 91017 Origin ASes present in the Internet Routing Table: 9009 Origin ASes announcing only one prefix: 3116 Transit ASes present in the Internet Routing Table: 1242 Average AS path length visible in the Internet Routing Table: 5.5 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 25 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 3 Number of addresses announced to Internet: 1191386328 Equivalent to 71 /8s, 3 /16s and 28 /24s Percentage of available address space announced: 32.1 Percentage of allocated address space announced: 63.0 Percentage of available address space allocated: 51.0 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 63149 Prefixes being announced from the ARIN address blocks: 43602 ARIN Region origin ASes present in the Internet Routing Table: 5525 ARIN Region origin ASes announcing only one prefix: 1567 ARIN Region transit ASes present in the Internet Routing Table: 604 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 167447890 Equivalent to 9 /8s, 251 /16s and 13 /24s Percentage of available ARIN address space announced: 76.8 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 19455 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2148 3428 UUNET Technologies, Inc. 7018 897 3034 AT&T 1 884 4531 BBN Planet 705 719 41 UUNET Technologies, Inc. 7046 712 516 UUNET Technologies, Inc. 1239 704 1621 Sprint ICM-Inria 2914 676 1318 Verio, Inc. 174 607 2939 PSINet Inc. 816 569 157 UUNET Canada4 3561 560 1382 Cable & Wireless USA 209 537 563 Qwest 8013 515 64 PSINet Ltd. Canada 3549 483 428 Frontier GlobalCenter 271 459 300 BCnet Backbone 3908 437 289 Supernet, Inc. 4293 436 56 Cable & Wireless USA 2548 431 546 Digital Express Group, Inc. 3602 419 74 Sprint Canada 690 339 19 Merit Network Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2148 3428 UUNET Technologies, Inc. 7018 897 3034 AT&T 1 884 4531 BBN Planet 1221 754 958 Telstra 705 719 41 UUNET Technologies, Inc. 7046 712 516 UUNET Technologies, Inc. 1239 704 1621 Sprint ICM-Inria 2914 676 1318 Verio, Inc. 174 607 2939 PSINet Inc. 816 569 157 UUNET Canada4 3561 560 1382 Cable & Wireless USA 209 537 563 Qwest 8013 515 64 PSINet Ltd. Canada 3549 483 428 Frontier GlobalCenter 271 459 300 BCnet Backbone 3908 437 289 Supernet, Inc. 4293 436 56 Cable & Wireless USA 2548 431 546 Digital Express Group, Inc. 2764 425 129 connect.com.au pty ltd List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 64750 PRIVATE 63.67.32.0/24 15218 Communications 65519 PRIVATE 64.124.60.0/24 6461 AboveNet Communicati 65519 PRIVATE 64.124.61.0/24 6461 AboveNet Communicati 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 64621 PRIVATE 152.121.2.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.3.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.4.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.33.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.36.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.49.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.100.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.200.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.255.0/24 701 UUNET Technologies, 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, 57158 RESERVED 210.56.192.0/20 4628 Pacific Internet Pte Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 39.144.212.0/24 174 PSINet Inc. 50.50.50.0/30 6713 Itissalat Al-MAGHRIB 60.60.60.0/30 6713 Itissalat Al-MAGHRIB Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:22 /9:4 /10:5 /11:9 /12:32 /13:58 /14:180 /15:288 /16:6709 /17:966 /18:1915 /19:6046 /20:3970 /21:3922 /22:5872 /23:7613 /24:52791 /25:124 /26:178 /27:81 /28:58 /29:95 /30:27 /31:0 /32:52 End of report From cjw at remarque.org Fri Nov 10 13:34:02 2000 From: cjw at remarque.org (Cathy Wittbrodt) Date: Fri, 10 Nov 2000 10:34:02 -0800 Subject: Update to weekly routing analysis summary In-Reply-To: Message from Philip Smith of "Wed, 08 Nov 2000 20:22:17 +1000." <5.0.0.25.2.20001108202146.00a37450@lint.cisco.com> Message-ID: <200011101834.KAA03661@pox.remarque.org> This is cool Philip, thanks for the update!!! From: Philip Smith Subject: Update to weekly routing analysis summary Hi, This is to inform you of a small modification to my weekly posting to this list. The "List of Illegal ASes" in the report has been replaced with the "List of Unregistered ASes". Basically this includes the previous private AS and reserved AS announcements, but adds to it the list of ASes announced for which there is no registration information contained in APNIC, ARIN, RIPE NCC, or DDN NIC (US Military) databases. At first run there are three new ASes appearing in this list, in addition to the quantity of private ASes being leaked to the Internet. They are 1877, 2027 and 5757. Any comments or feedback welcome, best wishes! philip -- From pfs at cisco.com Tue Nov 14 17:10:52 2000 From: pfs at cisco.com (Philip Smith) Date: Wed, 15 Nov 2000 08:10:52 +1000 Subject: Update to weekly routing analysis summary In-Reply-To: <200011101834.KAA03661@pox.remarque.org> References: <5.0.0.25.2.20001108202146.00a37450@lint.cisco.com> Message-ID: <5.0.0.25.2.20001115080411.08001ba0@lint.cisco.com> Hi Cathy, Thanks, I had hoped it would be useful. I don't want to be ASN policeman, but I thought it would be interesting to look and compare what was being announced versus what was actually registered somewhere. I was really surprised that there were only 4 ASNs < 64511 being announced. Now to figure out why ASN 2027 and ASN 5757 are being used on the Internet without any registration information in ARIN's database, or indeed, anywhere else... Anyone any ideas, especially Interpacket and UUNET who are respectively routing these two ASes? (When I was on the ISP side of the fence we never routed anything if it wasn't registered somewhere, but maybe these "rules" don't apply anymore...? :) philip -- At 10:34 10/11/00 -0800, Cathy Wittbrodt wrote: >This is cool Philip, thanks for the update!!! > > From: Philip Smith > Subject: Update to weekly routing analysis summary > Hi, > > This is to inform you of a small modification to my weekly posting to > this > list. The "List of Illegal ASes" in the report has been replaced with > the > "List of Unregistered ASes". Basically this includes the previous > private > AS and reserved AS announcements, but adds to it the list of ASes > announced > for which there is no registration information contained in APNIC, ARIN, > RIPE NCC, or DDN NIC (US Military) databases. > > At first run there are three new ASes appearing in this list, in > addition > to the quantity of private ASes being leaked to the Internet. They are > 1877, 2027 and 5757. > > Any comments or feedback welcome, > > best wishes! > > philip > -- > From lhoward at uu.net Tue Nov 14 18:34:16 2000 From: lhoward at uu.net (Lee Howard) Date: Tue, 14 Nov 2000 18:34:16 -0500 (EST) Subject: Update to weekly routing analysis summary In-Reply-To: <5.0.0.25.2.20001115080411.08001ba0@lint.cisco.com> Message-ID: I'll look into it. Since I work in Install, I'll confess that it's never occurred to me that someone might try to announce an ASN they didn't own, or propagate an ASN that wasn't legitmately their customer. In a current thread on NANOG, somebody else pointed out that there's no benefit to it; they real owner will catch you and make the upstream stop routing. Still, it's probably fair to say that I'm too trusting. A logical question then is, if a customer is propagating a bogus ASN to me, how would I stop it? Do other folks commonly use "AS Martian" access lists? I'm not even sure how I would begin to compile such a list. for ($asn=1; $asn<65535; $asn++) { if (! &whois($asn)) {push(@martians, $asn);} } ## bleah btw, when I say "I" or "me", I mean the guy typing, not the corporate entity known as UUNET, a WorldCom Company. Lee On Wed, 15 Nov 2000, Philip Smith wrote: > Date: Wed, 15 Nov 2000 08:10:52 +1000 > From: Philip Smith > To: Cathy Wittbrodt > Cc: rtma at arin.net > Subject: Re: Update to weekly routing analysis summary > > Hi Cathy, > > Thanks, I had hoped it would be useful. I don't want to be ASN policeman, > but I thought it would be interesting to look and compare what was being > announced versus what was actually registered somewhere. I was really > surprised that there were only 4 ASNs < 64511 being announced. > > Now to figure out why ASN 2027 and ASN 5757 are being used on the Internet > without any registration information in ARIN's database, or indeed, > anywhere else... > > Anyone any ideas, especially Interpacket and UUNET who are respectively > routing these two ASes? (When I was on the ISP side of the fence we never > routed anything if it wasn't registered somewhere, but maybe these "rules" > don't apply anymore...? :) > > philip > -- > > At 10:34 10/11/00 -0800, Cathy Wittbrodt wrote: > > >This is cool Philip, thanks for the update!!! > > > > From: Philip Smith > > Subject: Update to weekly routing analysis summary > > Hi, > > > > This is to inform you of a small modification to my weekly posting to > > this > > list. The "List of Illegal ASes" in the report has been replaced with > > the > > "List of Unregistered ASes". Basically this includes the previous > > private > > AS and reserved AS announcements, but adds to it the list of ASes > > announced > > for which there is no registration information contained in APNIC, ARIN, > > RIPE NCC, or DDN NIC (US Military) databases. > > > > At first run there are three new ASes appearing in this list, in > > addition > > to the quantity of private ASes being leaked to the Internet. They are > > 1877, 2027 and 5757. > > > > Any comments or feedback welcome, > > > > best wishes! > > > > philip > > -- > > > From pfs at cisco.com Tue Nov 14 19:59:25 2000 From: pfs at cisco.com (Philip Smith) Date: Wed, 15 Nov 2000 10:59:25 +1000 Subject: Update to weekly routing analysis summary In-Reply-To: References: <5.0.0.25.2.20001115080411.08001ba0@lint.cisco.com> Message-ID: <5.0.0.25.2.20001115104617.04b92950@localhost> Hi Lee, At 18:34 14/11/00 -0500, Lee Howard wrote: >I'll look into it. Great, thanks for that! >Since I work in Install, I'll confess that it's never occurred to me that >someone might try to announce an ASN they didn't own, or propagate an ASN >that wasn't legitmately their customer. In a current thread on NANOG, >somebody else pointed out that there's no benefit to it; they real owner >will catch you and make the upstream stop routing. Yup, if you are using someone else's. But if you are using an unallocated ASN below the current range being allocated from by the three registries, or one which is just below the 64512 boundary, people aren't likely to come chasing you soon. Note the ASN57158 coming from a customer of Pacific Internet. This isn't meant to encourage people to do this (because my spare time hobby is to run this weekly report, and I'm watching now... ;-) >Still, it's probably fair to say that I'm too trusting. A logical question >then is, if a customer is propagating a bogus ASN to me, how would I stop >it? I agree, this was easier when networks were small, and it was easier to spot funny goings on. Now it is harder. >Do other folks commonly use "AS Martian" access lists? I'm not even sure >how I would begin to compile such a list. >for ($asn=1; $asn<65535; $asn++) { if (! &whois($asn)) {push(@martians, >$asn);} } ## bleah I don't think there is one, but a first cut today would be to block ASNs >32768, maybe (I know, won't scale beyond another year)? Also, some routers have an option to block ASNs >64511 which would help block some of the private ASNs appearing on the Internet... Operationally, in the past when I brought on a new customer, I'd check their announcement on connection - if their address space and/or ASN weren't registered, we'd go "fix" that... Ongoing monitoring - harder, doesn't earn money, so isn't really done. philip -- From randy at psg.com Thu Nov 16 12:33:30 2000 From: randy at psg.com (Randy Bush) Date: Thu, 16 Nov 2000 09:33:30 -0800 Subject: Please send me your comments References: <5.0.0.25.2.20001103165350.00a64c60@lint.cisco.com> Message-ID: folk in asn exhaustion panic may want to look at draft-chen-as4bytes-00.txt and comment if comment is useful. randy From cscora at dev.apnic.net Thu Nov 16 13:03:17 2000 From: cscora at dev.apnic.net (Routing Analysis) Date: Fri, 17 Nov 2000 04:03:17 +1000 (EST) Subject: ARIN Region Weekly Routing Report Message-ID: <200011161803.EAA27841@dev.apnic.net> This is an automated weekly mailing sent to the ARIN RTMA WG e-mail list describing the state of the Internet Routing Table in North and South America and Southern Africa. Daily listings are sent to bgp-stats at lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Americas and Southern Africa Report 17 Nov, 2000 Analysis Summary ---------------- BGP routing table entries examined: 95742 Origin ASes present in the Internet Routing Table: 9122 Origin ASes announcing only one prefix: 3174 Transit ASes present in the Internet Routing Table: 1231 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 29 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 4 Number of addresses announced to Internet: 1228235646 Equivalent to 73 /8s, 53 /16s and 99 /24s Percentage of available address space announced: 33.1 Percentage of allocated address space announced: 65.0 Percentage of available address space allocated: 51.0 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 66221 Prefixes being announced from the ARIN address blocks: 44891 ARIN Region origin ASes present in the Internet Routing Table: 5589 ARIN Region origin ASes announcing only one prefix: 1596 ARIN Region transit ASes present in the Internet Routing Table: 602 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 185212079 Equivalent to 11 /8s, 10 /16s and 28 /24s Percentage of available ARIN address space announced: 84.9 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 19455 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2262 3431 UUNET Technologies, Inc. 1 1004 4553 BBN Planet 705 881 46 UUNET Technologies, Inc. 7018 861 3037 AT&T 1239 716 1646 Sprint ICM-Inria 7046 702 526 UUNET Technologies, Inc. 2914 677 1323 Verio, Inc. 174 606 2963 PSINet Inc. 3561 549 1365 Cable & Wireless USA 209 543 563 Qwest 6082 530 66 Management Analysis, Incorpor 8013 510 64 PSINet Ltd. Canada 3549 489 421 Frontier GlobalCenter 816 473 135 UUNET Canada4 271 459 300 BCnet Backbone 3602 437 80 Sprint Canada 3908 437 289 Supernet, Inc. 2548 436 538 Digital Express Group, Inc. 4293 433 55 Cable & Wireless USA Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2262 3431 UUNET Technologies, Inc. 4788 1325 46 TMnet, Telekom Malaysia 1 1004 4553 BBN Planet 1221 882 983 Telstra 705 881 46 UUNET Technologies, Inc. 7018 861 3037 AT&T 1239 716 1646 Sprint ICM-Inria 7046 702 526 UUNET Technologies, Inc. 2914 677 1323 Verio, Inc. 174 606 2963 PSINet Inc. 3561 549 1365 Cable & Wireless USA 209 543 563 Qwest 6082 530 66 Management Analysis, Incorpor 8013 510 64 PSINet Ltd. Canada 3549 489 421 Frontier GlobalCenter 816 473 135 UUNET Canada4 271 459 300 BCnet Backbone 2764 457 129 connect.com.au pty ltd 3602 437 80 Sprint Canada List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 64750 PRIVATE 63.67.32.0/24 15218 Communications 64610 PRIVATE 63.150.35.0/24 209 Qwest 64602 PRIVATE 63.236.57.0/24 209 Qwest 65102 PRIVATE 63.239.14.0/24 209 Qwest 65102 PRIVATE 128.64.17.0/24 209 Qwest 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 64621 PRIVATE 152.121.2.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.3.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.4.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.33.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.49.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.100.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.200.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.255.0/24 701 UUNET Technologies, 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 65003 PRIVATE 203.126.185.0/24 3758 SingNet 65003 PRIVATE 203.127.232.0/24 3758 SingNet 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, 64605 PRIVATE 208.47.206.0/24 209 Qwest 57158 RESERVED 210.56.192.0/20 4628 Pacific Internet Pte Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 68.189.125.0/24 702 UUNET Technologies, Inc. 91.16.23.0/24 11770 Net56 100.0.0.0/8 4702 KDD Communications 201.97.98.0/24 18941 Mercurio SAP Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:24 /9:4 /10:5 /11:9 /12:32 /13:58 /14:179 /15:289 /16:6730 /17:973 /18:1930 /19:6061 /20:4043 /21:3956 /22:6058 /23:8038 /24:55204 /25:319 /26:541 /27:245 /28:135 /29:106 /30:617 /31:0 /32:186 End of report From smarcus at genuity.com Fri Nov 17 16:25:08 2000 From: smarcus at genuity.com (J. Scott Marcus) Date: Fri, 17 Nov 2000 16:25:08 -0500 Subject: Please send me your comments In-Reply-To: References: <5.0.0.25.2.20001103165350.00a64c60@lint.cisco.com> Message-ID: <3.0.5.32.20001117162508.00aa68d0@pobox3.genuity.com> At 09:33 11/16/2000 -0800, Randy Bush wrote: >folk in asn exhaustion panic may want to look at draft-chen-as4bytes-00.txt >and comment if comment is useful. At this point, I think that there are grounds for concern but not for panic... ;^D Draft looks very promising. Simple and straigtforward. Am I correct in thinking that, even if the expansion in BGP-x code is negligible, memory requirements for the expanded routing table will ultimately (when four octet ASNs are fully deployed) be about twice as great per route as what we experience today? Cheers, - Scott From randy at psg.com Fri Nov 17 17:07:10 2000 From: randy at psg.com (Randy Bush) Date: Fri, 17 Nov 2000 14:07:10 -0800 Subject: Please send me your comments References: <5.0.0.25.2.20001103165350.00a64c60@lint.cisco.com> <3.0.5.32.20001117162508.00aa68d0@pobox3.genuity.com> Message-ID: > Am I correct in thinking that, even if the expansion in BGP-x code is > negligible, memory requirements for the expanded routing table will > ultimately (when four octet ASNs are fully deployed) be about twice as > great per route as what we experience today? no, as the asns are not all that we have in a path. and memory is not an issue anyway randy From cscora at dev.apnic.net Thu Nov 23 13:06:16 2000 From: cscora at dev.apnic.net (Routing Analysis) Date: Fri, 24 Nov 2000 04:06:16 +1000 (EST) Subject: ARIN Region Weekly Routing Report Message-ID: <200011231806.EAA11957@dev.apnic.net> This is an automated weekly mailing sent to the ARIN RTMA WG e-mail list describing the state of the Internet Routing Table in North and South America and Southern Africa. Daily listings are sent to bgp-stats at lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Americas and Southern Africa Report 24 Nov, 2000 Analysis Summary ---------------- BGP routing table entries examined: 94963 Origin ASes present in the Internet Routing Table: 9195 Origin ASes announcing only one prefix: 3207 Transit ASes present in the Internet Routing Table: 1236 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 23 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1228704450 Equivalent to 73 /8s, 60 /16s and 138 /24s Percentage of available address space announced: 33.1 Percentage of allocated address space announced: 65.0 Percentage of available address space allocated: 51.0 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 65658 Prefixes being announced from the ARIN address blocks: 44648 ARIN Region origin ASes present in the Internet Routing Table: 5630 ARIN Region origin ASes announcing only one prefix: 1606 ARIN Region transit ASes present in the Internet Routing Table: 601 Average ARIN Region AS path length visible: 5.2 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 185713010 Equivalent to 11 /8s, 17 /16s and 193 /24s Percentage of available ARIN address space announced: 85.1 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 19455 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2321 3438 UUNET Technologies, Inc. 1 1000 4553 BBN Planet 705 911 47 UUNET Technologies, Inc. 7018 881 3038 AT&T 1239 720 1645 Sprint ICM-Inria 7046 684 526 UUNET Technologies, Inc. 2914 671 1291 Verio, Inc. 174 595 2733 PSINet Inc. 209 550 563 Qwest 3561 547 1342 Cable & Wireless USA 6082 532 66 Management Analysis, Incorpor 3549 487 413 Frontier GlobalCenter 816 443 141 UUNET Canada4 2548 442 546 Digital Express Group, Inc. 4293 437 55 Cable & Wireless USA 3602 436 80 Sprint Canada 3908 434 289 Supernet, Inc. 690 342 28 Merit Network 271 335 299 BCnet Backbone Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2321 3438 UUNET Technologies, Inc. 1 1000 4553 BBN Planet 1221 926 984 Telstra 705 911 47 UUNET Technologies, Inc. 7018 881 3038 AT&T 1239 720 1645 Sprint ICM-Inria 7046 684 526 UUNET Technologies, Inc. 2914 671 1291 Verio, Inc. 174 595 2733 PSINet Inc. 2563 588 82 Seoul National University 209 550 563 Qwest 3561 547 1342 Cable & Wireless USA 6082 532 66 Management Analysis, Incorpor 1309 492 133 INRIA 3549 487 413 Frontier GlobalCenter 2764 446 128 connect.com.au pty ltd 816 443 141 UUNET Canada4 2548 442 546 Digital Express Group, Inc. 4293 437 55 Cable & Wireless USA List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65318 PRIVATE 62.179.0.0/19 6830 chello broadband 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 64621 PRIVATE 152.121.2.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.3.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.4.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.33.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.49.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.100.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.200.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.255.0/24 701 UUNET Technologies, 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 65534 PRIVATE 203.177.23.0/24 4775 G-Net 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, 57158 RESERVED 210.56.192.0/20 4628 Pacific Internet Pte Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 91.16.23.0/24 11770 Net56 219.219.219.0/24 2563 Seoul National University Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:24 /9:4 /10:5 /11:9 /12:32 /13:56 /14:181 /15:289 /16:6727 /17:982 /18:1937 /19:6091 /20:4109 /21:4026 /22:6177 /23:8162 /24:55056 /25:229 /26:428 /27:95 /28:80 /29:84 /30:90 /31:0 /32:90 End of report From cscora at dev.apnic.net Thu Nov 30 13:03:00 2000 From: cscora at dev.apnic.net (Routing Analysis) Date: Fri, 1 Dec 2000 04:03:00 +1000 (EST) Subject: ARIN Region Weekly Routing Report Message-ID: <200011301803.EAA01951@dev.apnic.net> This is an automated weekly mailing sent to the ARIN RTMA WG e-mail list describing the state of the Internet Routing Table in North and South America and Southern Africa. Daily listings are sent to bgp-stats at lists.apnic.net For a graphical representation, please see http://www.apnic.net/stats/bgp. If you have any comments please contact Philip Smith . Americas and Southern Africa Report 01 Dec, 2000 Analysis Summary ---------------- BGP routing table entries examined: 94939 Origin ASes present in the Internet Routing Table: 9067 Origin ASes announcing only one prefix: 3182 Transit ASes present in the Internet Routing Table: 1227 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 18 Illegal AS announcements present in the Routing Table: 114 Non-routable prefixes present in the Routing Table: 0 Prefixes being announced from the IANA Reserved Address blocks: 2 Number of addresses announced to Internet: 1179642521 Equivalent to 70 /8s, 79 /16s and 234 /24s Percentage of available address space announced: 31.8 Percentage of allocated address space announced: 62.4 Percentage of available address space allocated: 51.0 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 66581 Prefixes being announced from the ARIN address blocks: 44957 ARIN Region origin ASes present in the Internet Routing Table: 5529 ARIN Region origin ASes announcing only one prefix: 1590 ARIN Region transit ASes present in the Internet Routing Table: 592 Average ARIN Region AS path length visible: 5.1 Max ARIN Region AS path length visible: 13 Number of ARIN addresses announced to Internet: 169409206 Equivalent to 10 /8s, 24 /16s and 250 /24s Percentage of available ARIN address space announced: 77.7 ARIN AS Blocks 1 - 1876, 1902 - 2042, 2044 - 2046, 2048 - 2106 2138 - 2584, 2615 - 2772, 2823 - 2829, 2880 - 3153 3354 - 4607, 4865 - 5119, 5632 - 6655, 6912 - 7466 7723 - 8191, 10240 - 12287, 13312 - 15359 16384 - 17407, 18432 - 19455 ARIN Address Blocks 63/8, 64/7, 66/8, 199/8, 200/8, 204/6, 208/7 and 216/8 ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /19 equiv Description 701 2413 3453 UUNET Technologies, Inc. 12050 1931 1775 MachOne Communications, Inc. 705 1008 50 UUNET Technologies, Inc. 1 999 4553 BBN Planet 7018 898 3031 AT&T 1239 713 1637 Sprint ICM-Inria 7046 684 526 UUNET Technologies, Inc. 2914 665 1275 Verio, Inc. 174 578 2729 PSINet Inc. 209 559 565 Qwest 3561 558 1360 Cable & Wireless USA 6082 530 65 Management Analysis, Incorpor 3549 492 414 Frontier GlobalCenter 2548 444 547 Digital Express Group, Inc. 3602 435 80 Sprint Canada 4293 432 55 Cable & Wireless USA 3908 431 289 Supernet, Inc. 816 415 140 UUNET Canada4 690 343 28 Merit Network Global Per AS prefix count summary ---------------------------------- ASN No of nets /19 equiv Description 701 2413 3453 UUNET Technologies, Inc. 12050 1931 1775 MachOne Communications, Inc. 705 1008 50 UUNET Technologies, Inc. 1 999 4553 BBN Planet 1221 934 985 Telstra 7018 898 3031 AT&T 1239 713 1637 Sprint ICM-Inria 7046 684 526 UUNET Technologies, Inc. 2914 665 1275 Verio, Inc. 174 578 2729 PSINet Inc. 209 559 565 Qwest 3561 558 1360 Cable & Wireless USA 6082 530 65 Management Analysis, Incorpor 2563 527 70 Seoul National University 3549 492 414 Frontier GlobalCenter 2764 449 128 connect.com.au pty ltd 2548 444 547 Digital Express Group, Inc. 3602 435 80 Sprint Canada 4293 432 55 Cable & Wireless USA List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65530 PRIVATE 63.176.0.0/24 4999 Sprint 65530 PRIVATE 63.176.2.0/24 4999 Sprint 65530 PRIVATE 63.176.3.0/24 4999 Sprint 65530 PRIVATE 63.176.5.0/24 4999 Sprint 65530 PRIVATE 63.176.6.0/24 4999 Sprint 65530 PRIVATE 63.176.32.0/24 4999 Sprint 65530 PRIVATE 63.176.37.0/24 4999 Sprint 65530 PRIVATE 63.176.38.0/24 4999 Sprint 65530 PRIVATE 63.176.39.0/24 4999 Sprint 65530 PRIVATE 63.176.40.0/24 4999 Sprint 65530 PRIVATE 63.176.41.0/24 4999 Sprint 65530 PRIVATE 63.176.42.0/24 4999 Sprint 65530 PRIVATE 63.176.53.0/24 4999 Sprint 65530 PRIVATE 63.176.57.0/24 4999 Sprint 65530 PRIVATE 63.176.59.0/24 4999 Sprint 65530 PRIVATE 63.176.60.0/24 4999 Sprint 65530 PRIVATE 63.176.62.0/24 4999 Sprint 65530 PRIVATE 63.176.63.0/24 4999 Sprint 65530 PRIVATE 63.176.65.0/24 4999 Sprint 65530 PRIVATE 63.176.66.0/24 4999 Sprint 65530 PRIVATE 63.176.72.0/24 4999 Sprint 65530 PRIVATE 63.176.74.0/24 4999 Sprint 65530 PRIVATE 63.176.77.0/24 4999 Sprint 65530 PRIVATE 63.176.78.0/24 4999 Sprint 65530 PRIVATE 63.176.79.0/24 4999 Sprint 65530 PRIVATE 63.176.80.0/24 4999 Sprint 65530 PRIVATE 63.176.83.0/24 4999 Sprint 65530 PRIVATE 63.176.84.0/24 4999 Sprint 65530 PRIVATE 63.176.86.0/24 4999 Sprint 65530 PRIVATE 63.176.89.0/24 4999 Sprint 65530 PRIVATE 63.176.90.0/24 4999 Sprint 65530 PRIVATE 63.176.92.0/24 4999 Sprint 65530 PRIVATE 63.176.93.0/24 4999 Sprint 65530 PRIVATE 63.176.94.0/24 4999 Sprint 65530 PRIVATE 63.176.96.0/24 4999 Sprint 65530 PRIVATE 63.176.97.0/24 4999 Sprint 65530 PRIVATE 63.176.98.0/24 4999 Sprint 65530 PRIVATE 63.176.106.0/24 4999 Sprint 65530 PRIVATE 63.176.107.0/24 4999 Sprint 65530 PRIVATE 63.176.109.0/24 4999 Sprint 65530 PRIVATE 63.176.110.0/24 4999 Sprint 65530 PRIVATE 63.176.112.0/24 4999 Sprint 65530 PRIVATE 63.176.113.0/24 4999 Sprint 65530 PRIVATE 63.176.115.0/24 4999 Sprint 65530 PRIVATE 63.176.119.0/24 4999 Sprint 65530 PRIVATE 63.176.120.0/24 4999 Sprint 65530 PRIVATE 63.176.121.0/24 4999 Sprint 65530 PRIVATE 63.176.122.0/24 4999 Sprint 65530 PRIVATE 63.176.131.0/24 4999 Sprint 65530 PRIVATE 63.176.159.0/24 4999 Sprint 65530 PRIVATE 63.176.166.0/24 4999 Sprint 65530 PRIVATE 63.176.168.0/24 4999 Sprint 65530 PRIVATE 63.176.169.0/24 4999 Sprint 65530 PRIVATE 63.176.170.0/24 4999 Sprint 65530 PRIVATE 63.176.172.0/24 4999 Sprint 65530 PRIVATE 63.176.208.0/24 4999 Sprint 65530 PRIVATE 63.176.210.0/24 4999 Sprint 65530 PRIVATE 63.176.211.0/24 4999 Sprint 65530 PRIVATE 63.176.213.0/24 4999 Sprint 65530 PRIVATE 63.176.214.0/24 4999 Sprint 65530 PRIVATE 63.176.228.0/24 4999 Sprint 65530 PRIVATE 63.176.229.0/24 4999 Sprint 65530 PRIVATE 63.176.231.0/24 4999 Sprint 65530 PRIVATE 63.177.0.0/24 4999 Sprint 65530 PRIVATE 63.177.1.0/24 4999 Sprint 65530 PRIVATE 63.177.14.0/24 4999 Sprint 65530 PRIVATE 63.177.38.0/24 4999 Sprint 65530 PRIVATE 63.177.48.0/24 4999 Sprint 65530 PRIVATE 63.177.50.0/24 4999 Sprint 65530 PRIVATE 63.177.78.0/24 4999 Sprint 65530 PRIVATE 63.177.80.0/24 4999 Sprint 65530 PRIVATE 63.177.83.0/24 4999 Sprint 65530 PRIVATE 63.177.86.0/24 4999 Sprint 65530 PRIVATE 63.177.91.0/24 4999 Sprint 65530 PRIVATE 63.177.93.0/24 4999 Sprint 65530 PRIVATE 63.177.99.0/24 4999 Sprint 65530 PRIVATE 63.177.101.0/24 4999 Sprint 65530 PRIVATE 63.177.102.0/24 4999 Sprint 65530 PRIVATE 63.177.104.0/24 4999 Sprint 65530 PRIVATE 63.177.106.0/24 4999 Sprint 65530 PRIVATE 63.177.107.0/24 4999 Sprint 65530 PRIVATE 63.177.108.0/24 4999 Sprint 65530 PRIVATE 63.177.110.0/24 4999 Sprint 65530 PRIVATE 63.177.111.0/24 4999 Sprint 65530 PRIVATE 63.177.169.0/24 4999 Sprint 65530 PRIVATE 63.177.171.0/24 4999 Sprint 65530 PRIVATE 63.177.172.0/24 4999 Sprint 65530 PRIVATE 63.177.173.0/24 4999 Sprint 65530 PRIVATE 63.177.175.0/24 4999 Sprint 65530 PRIVATE 63.177.214.0/24 4999 Sprint 65530 PRIVATE 63.177.216.0/24 4999 Sprint 65530 PRIVATE 63.177.252.0/24 4999 Sprint 65530 PRIVATE 63.177.253.0/24 4999 Sprint 2027 UNALLOCATED 150.185.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.185.128.0/18 8143 Publicom Corp. 2027 UNALLOCATED 150.186.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.187.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.188.0.0/16 10530 Interpacket Group, I 2027 UNALLOCATED 150.189.0.0/16 10530 Interpacket Group, I 64621 PRIVATE 152.121.2.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.3.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.4.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.33.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.36.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.49.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.100.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.200.0/24 701 UUNET Technologies, 64621 PRIVATE 152.121.255.0/24 701 UUNET Technologies, 1877 UNALLOCATED 192.108.196.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.209.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.210.0/24 1880 Stupi, house man's 1877 UNALLOCATED 192.108.214.0/24 1880 Stupi, house man's 5757 UNALLOCATED 192.239.13.0/24 701 UUNET Technologies, 5757 UNALLOCATED 207.19.224.0/24 701 UUNET Technologies, Advertised IANA Reserved Addresses ---------------------------------- Network Origin AS Description 91.16.23.0/24 11770 Net56 219.219.219.0/24 2563 Seoul National University Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:21 /9:4 /10:5 /11:9 /12:32 /13:56 /14:183 /15:290 /16:6724 /17:979 /18:1956 /19:6143 /20:4147 /21:4059 /22:6170 /23:8130 /24:54946 /25:234 /26:429 /27:90 /28:77 /29:80 /30:94 /31:0 /32:81 End of report