- NANOG - lists.nanog.org

Re: Re: What is the most standard subnet length on internet
by ChiYoung Joung 23 Dec '08

23 Dec '08

I would like to ask question more specifically. I know most of tier1 providers accept their customer prefixes smaller than /24. it means smaller than /24 routes always routable in that Tier1 provider. What about between Tier1 and another Tier1 ? Do they exchange their full customer's routes without any limitation of prefixes length ? or do they refer to some DB information like Regional Internet Registry and apply another filter on neighbor configuration with another Tier1 ? Chiyoung ============================================= Chi-Young Joung SAMSUNG NETWORKS Inc. Email: lionair(a)samsung.com Tel +82 70 7015 0623, Mobile +82 17 520 9193 Fax +82 70 7016 0031 ============================================= ------- Original Message ------- Sender : Nathan Ward<nanog(a)daork.net> Date : 2008-12-23 10:44 (GMT+09:00) Title : Re: What is the most standard subnet length on internet On 23/12/2008, at 2:39 PM, Joe Provo wrote: > On Tue, Dec 23, 2008 at 02:34:39PM +1300, Nathan Ward wrote: > [snip] >> Let me rephrase; Are there people who are filtering /24s received >> from >> eBGP peers who do not have a default route? > > of course. Curiously, it was really meant as a rhetorical question where the answer was "no". Why are people doing this? Are they lacking clue, or, is there some reasonable purpose? -- Nathan Ward

1 0

[USN-698-1] Nagios vulnerability (fwd)
by Gadi Evron 22 Dec '08

22 Dec '08

---------- Forwarded message ---------- Date: Mon, 22 Dec 2008 09:35:54 -0500 From: Marc Deslauriers <marc.deslauriers(a)canonical.com> To: ubuntu-security-announce(a)lists.ubuntu.com Cc: bugtraq(a)securityfocus.com, full-disclosure(a)lists.grok.org.uk Subject: [USN-698-1] Nagios vulnerability =========================================================== Ubuntu Security Notice USN-698-1 December 22, 2008 nagios vulnerability CVE-2008-5027 =========================================================== A security issue affects the following Ubuntu releases: Ubuntu 6.06 LTS This advisory also applies to the corresponding versions of Kubuntu, Edubuntu, and Xubuntu. The problem can be corrected by upgrading your system to the following package versions: Ubuntu 6.06 LTS: nagios-common 2:1.3-cvs.20050402-8ubuntu8 After a standard system upgrade you need to restart Nagios to effect the necessary changes. Details follow: It was discovered that Nagios did not properly parse commands submitted using the web interface. An authenticated user could use a custom form or a browser addon to bypass security restrictions and submit unauthorized commands. Updated packages for Ubuntu 6.06 LTS: Source archives: http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios_1.3-cvs.2005040… Size/MD5: 70914 96d8036bdb33aadd3141715039c91b24 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios_1.3-cvs.2005040… Size/MD5: 959 0393336015bf452f5dfeb74d75245311 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios_1.3-cvs.2005040… Size/MD5: 1621251 0f92b7b8e705411b7881d3650cbb5d56 Architecture independent packages: http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-common_1.3-cvs.… Size/MD5: 1218132 d18e298ee16f4c6c6b7c5969c46044e6 amd64 architecture (Athlon64, Opteron, EM64T Xeon): http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-mysql_1.3-cvs.2… Size/MD5: 1030206 085483fdefd0d7bc43e55dbc5be2bcd6 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-pgsql_1.3-cvs.2… Size/MD5: 1041656 09fc7bb2ff11062603680d09e290909b http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-text_1.3-cvs.20… Size/MD5: 1025618 61619d13effd9a4970486abf5933c756 i386 architecture (x86 compatible Intel/AMD): http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-mysql_1.3-cvs.2… Size/MD5: 877846 544afaebec24e7e94d2ce1da3a89346c http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-pgsql_1.3-cvs.2… Size/MD5: 886544 411d3ca5a204aa41a4a42ef6e5f56453 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-text_1.3-cvs.20… Size/MD5: 872936 aa31f6d1fb8a081a206eae3d6bfb3dd6 powerpc architecture (Apple Macintosh G3/G4/G5): http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-mysql_1.3-cvs.2… Size/MD5: 1015630 540a27062c7f8612b7f460b2bcfd93b9 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-pgsql_1.3-cvs.2… Size/MD5: 1024374 47e0480006df0b20a83f67b56da7a9f8 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-text_1.3-cvs.20… Size/MD5: 993324 03a67a7675075050a672a4c515e8e0c3 sparc architecture (Sun SPARC/UltraSPARC): http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-mysql_1.3-cvs.2… Size/MD5: 918810 7340348f043dd884c88bd016ee30e41d http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-pgsql_1.3-cvs.2… Size/MD5: 926172 e9ccf388b828a17e868807aa39cb5b51 http://security.ubuntu.com/ubuntu/pool/main/n/nagios/nagios-text_1.3-cvs.20… Size/MD5: 917374 c88dec0d93f590f8a93ebbc701696f68

1 0

Re: ICANN/Dotster emergency contacts? (hopefully not too OT)
by Edward B. DREGER 22 Dec '08

22 Dec '08

Thanks, all. I have several responses, and finally got through. Again, sorry for the OT noise. Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: davidc(a)brics.com -*- jfconmaapaq(a)intc.net -*- sam(a)everquick.net Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter.

1 0

ICANN/Dotster emergency contacts? (hopefully not too OT)
by Edward B. DREGER 22 Dec '08

22 Dec '08

Greetings, Does anyone have any "emergency" contacts at ICANN? Dotster? I have a couple domains that were erroneously expired this year instead of next. (I have the CC statement and ref # in front of me, to be certain that I'm not hallucinating.) Automated web form failed to send (to different domain) account info, and hold time is getting annoying. I've already filed the ICANN complaint, but that doesn't restore service. I'd buy an extra year and worry about the dispute later, but see note about automated web form. Please CC me @brotsman.com, and I can't currently receive email via the address by which I'm subscribed. And off-list, please. I don't want to drag things even farther OT than I already have. Thanks, and sorry for the panicked OT noise, Eddy (please remember to s/noc.everquick.net/brotsman.com/) -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: davidc(a)brics.com -*- jfconmaapaq(a)intc.net -*- sam(a)everquick.net Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter.

1 0

Managing CE eBGP details & common/accepted CE-facing BGP practices
by Justin Shore 22 Dec '08

22 Dec '08

Does anyone have any preferred ways to manage their customer-facing BGP details? I'm thinking about the customer's ASN (SP assigned private ASN or RIR assigned ASN), permitted prefixes, etc? While I'm sure this could be easily stored in a spreadsheet I'm not sure if there is any merit to storing some of these details outside of the configuration on the PE (assuming of course that the PE's config is regularly archived). Now if the PE's BGP config was auto-generated via a script then it would make sense for all the details to be stored off in a DB in the NOC. Beyond that is there a good reason to do archive it in a textual format off of the PE and if there is a sound reason to do it, is therea good or preferred way to do accomplish this? We're moving beyond our typical residential and very small SMB service to larger customers over the next few months. These areas have larger, more advanced customers and I'm sure we'll run into multi-homed environments and customer who will expect BGP peering options. I would like to be prepared with sound practices before we get our first customer that wants to get a default route via BGP, wants full tables, or has their own ASN and is bringing their own PI space with them. Some of this of course implies multiple processes to confirm that the ASN belongs to the customer in question, that the PI space belongs to the customer in question, notifying our upstreams to accept the customer's PI space, etc. It's hammering out the scalable and best practice config details that I'm concerned with at the moment. When assigning private ASNs to customers, are there any gotchas to be aware of? Is it possible to use the same private ASN for more than one customer on the same PE? What are common and accepted CE-facing BGP practices? MD5 AUTH, GTSM, max prefix limits? Which is preferred, route-maps or prefix-lists for controlling advertised and/or received routes? Do any SPs utilize AS-Path ACLs to check that prefixes from an customer's ASN are claimed to originate from there? Are there any SPs out there offering BFD support for BGP or CE-facing peering sessions? Should we have the customer announce their PA space to us or do we advertise it for them (redist a static)? Do SPs restrict access to tcp/179 on the CE from the Internet in the CE-facing ACL? Do SPs block access to the PE-CE subnet from the outside world like what was described in the Router Security Strategies book (pages 189-193)? What about dropping incoming traffic to everything but the CE IP? While I don't predict our CE-facing BGP load to be terribly significant at this point, I would like to establish sound practices now rather than down the road once we're neck deep in temporarily production workarounds. Is there any consensus on what's best practice for CE-facing BGP? I imagine most SP engineer's BGP practices could be better equated to a religious holy war on par with Chevy vs Ford or Mac vs PC. I would be interested in hearing what they are though and learning from the group's expertise. Thanks Justin

7 10

Gigabit Linux Routers
by Chris 22 Dec '08

22 Dec '08

Hi All, Sorry if this is a repeat topic. I've done a fair bit of trawling but can't find anything concrete to base decisions on. I'm hoping someone can offer some advice on suitable hardware and kernel tweaks for using Linux as a router running bgpd via Quagga. We do this at the moment and our box manages under the 100Mbps level very effectively. Over the next year however we expect to push about 250Mbps outbound traffic with very little inbound (50Mbps simultaneously) and I'm seeing differing suggestions of what to do in order to move up to the 1Gbps level. It seems even a dual core box with expensive NICs and some kernel tweaks will accomplish this but we can't afford to get the hardware purchases wrong. We'd be looking to buy one live and one standby box within the next month or so. They will only run Quagga primarily with 'tc' for shaping. We're in the UK if it makes any difference. Any help massively appreciated, ideally from those doing the same in production environments. Thanks, Chris

36 60

open source alternative to Internap's FCP?
by matthew zeier 22 Dec '08

22 Dec '08

Perhaps I just can't google right - does anyone know of any open source alternatives to Internap's FCP or the Avaya/RouteScience PathControl?

1 0

Security Intelligence [Was: Re: Netblock reassigned from Chile to US ISP...]
by Paul Ferguson 21 Dec '08

21 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Dec 13, 2008 at 12:22 AM, James Hess <mysidia(a)gmail.com> wrote: > > An in-depth strategy with hundreds or thousands of factors examined > results in a smaller > (but still present) possibility of the filter/detector being fooled. > > IP-based methods can be combined with the other stronger analysis of > transaction details and other info that can be gathered about a > submitter for detection of attempted abuse. > Personally, I don;t NANOG is the proper forum for this discussion. There are other forums, however, which do follow these issues -- some public, some private. If folks think that people are not "doing" massive correlation of criminal activity on the Internet, they would be mistaken. - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.3 (Build 3017) wj8DBQFJQ3JBq1pz9mNUZTMRAjqTAKD30/yrEYWu1ep4v7cOH2q3++aKRQCg2Sad wwap7dwpUiOv6r/w5st04KQ= =AZDw -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/

13 19

Peering Personals BoF NANOG45, Attention Peering Coordinators
by Aaron Hughes 19 Dec '08

19 Dec '08

Peering Coordinators, Reminder: The deadline is approaching quickly and thus far, I have 4 companies that would like to introduce themselves. Please be sure to send me your info if you are interested in introducing yourself or your network to the greater peering community. For those of you who may be thinking . o O ("I've got until the end of the month"), please keep in mind that for many of you, today is that day with vacation time / the holidays. So please spend 30 seconds sending the form to me today. :) Thank you fellow peers! Cheers, Aaron > Attention Peering Coordinators, > > NANOG45 is approaching quickly and it's time to get our Peering Personals participants lined up for the Peering BoF. > > Peering Personals is part of the Peering BoF (Birds Of a Feather) session and provides a forum for Peering Coordinators to meet each other with the goal of establishing peering relationships. > > Participating Peering Coordinators will complete and email the form below to the Peering BOF moderator in advance of the BOF. > > Peering Coordinators will have ~two minutes at the BOF to introduce themselves, their networks, where they currently peer and where they intend to be peering in the next several months, a little bit about what they require of potential peers and what they are looking for in a peering candidate. Peering Coordinators who would like to participate in Peering Introductions should e-mail the following information to aaronh(a)bind.com with the subject of "NANOG 45 Peering BOF" no later than Dec 31, 2008.: > > Name: _____________________ > Company:__________________ > AS#: _____________________ > Email Address: ________________ > Peering Locations Today: __________________ > Peering Locations in the next 3-6 months: ________________ > Is your network more Content-Heavy or Access-Heavy ? > Do you source/sink more than 5Gbps of traffic? > Do you require Contracts for Peering? > Do you have an "Open Peering Policy (meaning you will peer with anyone in any single location), "Selective Peering Policy (meaning you will peer but have some prerequisites that must be met first)�, or "Restrictive Peering Policy (meaning you generally will not peer with anybody else)?" > > If you have any questions, don't hesitate to send me an e-mail. > > Cheers, > > Aaron > > -- > > Aaron Hughes > aaronh(a)bind.com > (703) 244-0427 > Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 > http://www.bind.com/ -- Aaron Hughes aaronh(a)bind.com (703) 244-0427 Key fingerprint = AD 67 37 60 7D 73 C5 B7 33 18 3F 36 C3 1C C6 B8 http://www.bind.com/

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 19 Dec '08

19 Dec '08

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 20 Dec, 2008 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 275380 Prefixes after maximum aggregation: 131356 Deaggregation factor: 2.10 Unique aggregates announced to Internet: 132855 Total ASes present in the Internet Routing Table: 30108 Prefixes per ASN: 9.15 Origin-only ASes present in the Internet Routing Table: 26219 Origin ASes announcing only one prefix: 12782 Transit ASes present in the Internet Routing Table: 3889 Transit-only ASes present in the Internet Routing Table: 94 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 20 Max AS path prepend of ASN ( 3816) 15 Prefixes from unregistered ASNs in the Routing Table: 522 Unregistered ASNs in the Routing Table: 187 Number of 32-bit ASNs allocated by the RIRs: 68 Prefixes from 32-bit ASNs in the Routing Table: 12 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 259 Number of addresses announced to Internet: 1976219264 Equivalent to 117 /8s, 202 /16s and 182 /24s Percentage of available address space announced: 53.3 Percentage of allocated address space announced: 63.7 Percentage of available address space allocated: 83.7 Percentage of address space in use by end-sites: 75.0 Total number of prefixes smaller than registry allocations: 135179 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 63202 Total APNIC prefixes after maximum aggregation: 22693 APNIC Deaggregation factor: 2.79 Prefixes being announced from the APNIC address blocks: 60116 Unique aggregates announced from the APNIC address blocks: 25952 APNIC Region origin ASes present in the Internet Routing Table: 3494 APNIC Prefixes per ASN: 17.21 APNIC Region origin ASes announcing only one prefix: 952 APNIC Region transit ASes present in the Internet Routing Table: 535 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 17 Number of APNIC addresses announced to Internet: 393369248 Equivalent to 23 /8s, 114 /16s and 86 /24s Percentage of available APNIC address space announced: 78.2 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 APNIC Address Blocks 58/8, 59/8, 60/8, 61/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 122949 Total ARIN prefixes after maximum aggregation: 64542 ARIN Deaggregation factor: 1.90 Prefixes being announced from the ARIN address blocks: 92199 Unique aggregates announced from the ARIN address blocks: 35045 ARIN Region origin ASes present in the Internet Routing Table: 12660 ARIN Prefixes per ASN: 7.28 ARIN Region origin ASes announcing only one prefix: 4896 ARIN Region transit ASes present in the Internet Routing Table: 1212 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 20 Number of ARIN addresses announced to Internet: 405197088 Equivalent to 24 /8s, 38 /16s and 209 /24s Percentage of available ARIN address space announced: 83.3 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 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-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 ARIN Address Blocks 24/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 173/8, 174/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 62209 Total RIPE prefixes after maximum aggregation: 36644 RIPE Deaggregation factor: 1.70 Prefixes being announced from the RIPE address blocks: 56377 Unique aggregates announced from the RIPE address blocks: 37798 RIPE Region origin ASes present in the Internet Routing Table: 12375 RIPE Prefixes per ASN: 4.56 RIPE Region origin ASes announcing only one prefix: 6516 RIPE Region transit ASes present in the Internet Routing Table: 1866 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 17 Number of RIPE addresses announced to Internet: 382814560 Equivalent to 22 /8s, 209 /16s and 73 /24s Percentage of available RIPE address space announced: 87.8 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-49151 RIPE Address Blocks 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 22976 Total LACNIC prefixes after maximum aggregation: 5628 LACNIC Deaggregation factor: 4.08 Prefixes being announced from the LACNIC address blocks: 21001 Unique aggregates announced from the LACNIC address blocks: 11591 LACNIC Region origin ASes present in the Internet Routing Table: 1042 LACNIC Prefixes per ASN: 20.15 LACNIC Region origin ASes announcing only one prefix: 337 LACNIC Region transit ASes present in the Internet Routing Table: 169 Average LACNIC Region AS path length visible: 4.0 Max LACNIC Region AS path length visible: 18 Number of LACNIC addresses announced to Internet: 59214848 Equivalent to 3 /8s, 135 /16s and 140 /24s Percentage of available LACNIC address space announced: 58.8 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 3541 Total AfriNIC prefixes after maximum aggregation: 1429 AfriNIC Deaggregation factor: 2.48 Prefixes being announced from the AfriNIC address blocks: 5159 Unique aggregates announced from the AfriNIC address blocks: 1961 AfriNIC Region origin ASes present in the Internet Routing Table: 262 AfriNIC Prefixes per ASN: 19.69 AfriNIC Region origin ASes announcing only one prefix: 81 AfriNIC Region transit ASes present in the Internet Routing Table: 54 Average AfriNIC Region AS path length visible: 4.2 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 12454656 Equivalent to 0 /8s, 190 /16s and 11 /24s Percentage of available AfriNIC address space announced: 24.7 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 1557 6409 364 Korea Telecom (KIX) 17488 1442 101 99 Hathway IP Over Cable Interne 4755 1174 475 153 TATA Communications formerly 4134 898 15543 356 CHINANET-BACKBONE 9583 871 133 81 Sify Limited 18101 786 168 33 Reliance Infocom Ltd Internet 4780 727 358 64 Digital United Inc. 9498 688 310 48 BHARTI BT INTERNET LTD. 7545 656 152 81 TPG Internet Pty Ltd 24560 635 210 164 Bharti Airtel Ltd. Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4383 3435 344 bellsouth.net, inc. 209 2847 4033 626 Qwest 20115 1849 1472 742 Charter Communications 1785 1706 717 155 PaeTec Communications, Inc. 4323 1611 1067 382 Time Warner Telecom 6478 1601 368 289 AT&T Worldnet Services 2386 1578 705 891 AT&T Data Communications Serv 7018 1436 5873 994 AT&T WorldNet Services 11492 1230 192 12 Cable One 3356 1104 10994 430 Level 3 Communications, LLC Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8452 1632 188 11 TEDATA 3292 434 1764 383 TDC Tele Danmark 30890 391 80 203 SC Kappa Invexim SRL 12479 377 578 6 Uni2 Autonomous System 3301 336 1413 303 TeliaNet Sweden 3320 333 7065 282 Deutsche Telekom AG 8866 331 109 22 Bulgarian Telecommunication C 29049 330 26 3 AzerSat LLC. 3215 321 2856 95 France Telecom Transpac 8551 303 287 35 Bezeq International Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1406 2833 222 UniNet S.A. de C.V. 11830 667 299 9 Instituto Costarricense de El 10620 631 135 55 TVCABLE BOGOTA 22047 565 302 14 VTR PUNTO NET S.A. 7303 503 249 74 Telecom Argentina Stet-France 6471 429 86 43 ENTEL CHILE S.A. 16814 426 27 10 NSS, S.A. 11172 400 118 72 Servicios Alestra S.A de C.V 28573 365 491 24 NET Servicos de Comunicao S.A 7738 343 730 27 Telecomunicacoes da Bahia S.A Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 280 48 128 LINKdotNET AS number 3741 270 857 227 The Internet Solution 2018 239 215 140 Tertiary Education Network 6713 144 135 11 Itissalat Al-MAGHRIB 33783 143 10 17 EEPAD TISP TELECOM & INTERNET 29571 121 15 8 Ci Telecom Autonomous system 5536 120 8 17 Internet Egypt Network 5713 119 555 68 Telkom SA Ltd 33776 116 6 3 Starcomms Nigeria Limited 2905 80 177 76 Verizon South Africa Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4383 3435 344 bellsouth.net, inc. 209 2847 4033 626 Qwest 20115 1849 1472 742 Charter Communications 1785 1706 717 155 PaeTec Communications, Inc. 8452 1632 188 11 TEDATA 4323 1611 1067 382 Time Warner Telecom 6478 1601 368 289 AT&T Worldnet Services 2386 1578 705 891 AT&T Data Communications Serv 4766 1557 6409 364 Korea Telecom (KIX) 17488 1442 101 99 Hathway IP Over Cable Interne Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 209 2847 2221 Qwest 8452 1632 1621 TEDATA 1785 1706 1551 PaeTec Communications, Inc. 17488 1442 1343 Hathway IP Over Cable Interne 6478 1601 1312 AT&T Worldnet Services 4323 1611 1229 Time Warner Telecom 11492 1230 1218 Cable One 4766 1557 1193 Korea Telecom (KIX) 8151 1406 1184 UniNet S.A. de C.V. 20115 1849 1107 Charter Communications Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.154.0/23 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.159.0/24 7018 AT&T WorldNet Servic 32326 UNALLOCATED 12.40.49.0/24 7018 AT&T WorldNet Servic 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.75.116.0/22 10796 ServiceCo LLC - Road Runner 24.75.160.0/19 7843 Adelphia Corp. 24.142.40.0/21 7018 AT&T WorldNet Services 24.142.160.0/19 7018 AT&T WorldNet Services 24.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services 62.61.220.0/24 24974 Tachyon Europe BV - Wireless 62.61.221.0/24 24974 Tachyon Europe BV - Wireless 63.140.213.0/24 22555 Universal Talkware Corporatio 63.143.251.0/24 22555 Universal Talkware Corporatio Complete listing at http://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:20 /9:9 /10:20 /11:54 /12:159 /13:308 /14:559 /15:1096 /16:10268 /17:4512 /18:7750 /19:16644 /20:19464 /21:19076 /22:24169 /23:24653 /24:144536 /25:644 /26:807 /27:519 /28:97 /29:8 /30:1 /31:0 /32:7 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2866 4383 bellsouth.net, inc. 209 1594 2847 Qwest 8452 1317 1632 TEDATA 4766 1292 1557 Korea Telecom (KIX) 2386 1260 1578 AT&T Data Communications Serv 17488 1232 1442 Hathway IP Over Cable Interne 11492 1200 1230 Cable One 1785 1166 1706 PaeTec Communications, Inc. 6478 1129 1601 AT&T Worldnet Services 18566 1041 1060 Covad Communications Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:12 8:170 12:2225 13:2 15:21 16:3 17:5 20:36 24:1107 32:54 38:525 40:96 41:1772 43:1 44:2 47:9 52:3 55:3 56:3 57:26 58:518 59:595 60:456 61:1094 62:1016 63:2002 64:3406 65:2445 66:3607 67:1439 68:655 69:2374 70:530 71:173 72:1597 73:7 74:1335 75:191 76:306 77:853 78:511 79:299 80:920 81:907 82:537 83:392 84:410 85:1036 86:494 87:655 88:350 89:1363 90:45 91:1796 92:298 93:1052 94:837 95:106 96:95 97:150 98:172 99:10 100:1 110:1 111:1 113:52 114:144 115:166 116:1069 117:416 118:234 119:578 120:116 121:699 122:895 123:435 124:790 125:1273 128:359 129:219 130:135 131:408 132:72 133:9 134:193 135:33 136:225 137:131 138:144 139:91 140:412 141:110 142:389 143:296 144:309 145:53 146:371 147:143 148:610 149:219 150:140 151:209 152:149 153:131 154:10 155:249 156:167 157:304 158:164 159:300 160:274 161:131 162:254 163:146 164:515 165:500 166:364 167:348 168:669 169:159 170:459 171:38 172:10 173:128 174:11 187:16 188:1 189:356 190:2542 192:5822 193:4145 194:3298 195:2631 196:1205 198:3710 199:3315 200:5584 201:1504 202:7780 203:8068 204:3930 205:2128 206:2319 207:2761 208:3794 209:3494 210:2688 211:1132 212:1501 213:1583 214:62 215:26 216:4498 217:1201 218:379 219:405 220:1220 221:400 222:299 End of report

1 0