April 2009 - Test - lists.nanog.org

RE: Fiber cut in SF area
by Carlos Alcantar 12 Apr '09

12 Apr '09

I know as far as att/sbc/pacbell a lot of the time they run the ring within the same conduit to at least have hardware protection on the circuit I'm sure it's the same with other providers. -carlos -----Original Message----- From: Roy [mailto:r.engehausen@gmail.com] Sent: Saturday, April 11, 2009 6:02 PM To: nanog(a)nanog.org Subject: Re: Fiber cut in SF area Sean Donelan wrote: > ,,,, > Uh, not exactly. There was diversity in this case, but there was also > N+1 breaks. Outside of a few counties in the Bay Area, the rest of > the country's telecommunication system was unaffected. So in that > sense the system worked as designed. > .... About eight or ten years ago I went to PacBell (or whatever it was called at the time) and requested that two large facilities get a sonet ring between them. I was told I couldn't have it because they were both fed through a single set of conduits and one backhoe could cut both sides of the ring. It wouldn't be diverse so they wouldn't provison it unless I paid for the digging of new paths. So much for their theory of diverse. Sounds like the rules are different for them. There are one thing to also point out. That train track next to the manholes in South San Jose is the major line between the Bay Area and Southern CA. There are at least three or four fiber paths for different companies buried along those tracks. There are also connections from Gilroy to the Hollister/San Juan Bautista area and thence to Salinas. It would have been very simple for the telcos to provision a backup path southward.

1 0

RE: Fiber cut in SF area
by Roger Marquis 12 Apr '09

12 Apr '09

Jo? wrote: > I'm confussed, but please pardon the ignorance. > All the data centers we have are at minimum keys to access > data areas. Not that every area of fiber should have such, but > at least should they? Manhole covers "can" be keyed. For those of > you arguing that this is not enough, I would say at least it?s a start. That is an option, but it doesn't address the real problem. The real problem is route redundancy. This is what the original contract from DARPA to BBM, to create the Internet, was about! "The net" was created to enable communications bttn point A and point B in this exact scenario. No one should be surprised that ATT would cut-corners on critical infrastructure. The good news is that this incident will likely result in increased Federal scrutiny if not regulation. We know how spectacularly energy and banking deregulation failed. Is that mistake being repeated with telecommunications? The bad news is that some of the $16M/yr ATT spends lobbying Congress (for things like fighting number portability and getting a free pass on illegal domestic surveillance) will likely be redirected to ask for money to "fix" the problem they created. This assumes ATT is as badly managed, and the US FCC and DHS are better managed, than has been the case for the last 8 years. Time will tell. For a good "man in the street" perspective of how the outage effected things like a pharmacy's ability to fill subscriptions and a university computer's ability to boot check out a couple of shows broadcast on KUSP (Santa Cruz Public Radio) this morning: http://www.jivamedia.com/askdrdawn/askdrdawn.php http://geekspeak.org/ Roger Marquis

6 8

BGP FlowSpec support on provider networks
by Fouant, Stefan 11 Apr '09

11 Apr '09

Hi folks, I am trying to compile data on which providers are currently supporting BGP Flowspec at their edge, if there are any at all. The few providers I've reached out to have indicated they do not support this and have no intention of supporting this any time in the near future. I'm also curious why something so useful as to have the ability to advertise flow specification information in NLRI and distribute filtering information is taking so long to gain a foothold in the industry... Sorry for the repost but wanted to make sure this got it's own thread. Thanks, Stefan Fouant: NeuStar, Inc. Principal Network Engineer 46000 Center Oak Plaza Sterling, VA 20166 [ T ] +1 571 434 5656 [ M ] +1 202 210 2075 [ E ] stefan.fouant(a)neustar.biz [ W ] www.neustar.biz

5 5

Re: [OT] Re: Fiber cut in SF area
by Brandon Butterworth 11 Apr '09

11 Apr '09

> You can cut the concrete, too, for that matter, with oxyacetylene, as long as > you wear certain protective gear. We have a few vault covers here that are > concrete covering the largest vaults we have. You need more than a manhole > hook to get one of those covers up. And when you think you have it safely burried someone drives a tunnel boring machine through it - http://www.flickr.com/photos/23919135@N00/3426407496/ brandon

1 0

Re: Outside plant protection, fiber cuts, interwebz down oh noes!
by Robert Glover 11 Apr '09

11 Apr '09

*SNIP* located ten feet down a manhole on Monterey Highway, north of Blossom Hill Road in San Jose. Authorities also found two other locations where fiber optic cables were similarly cut -- near Hayes Avenue and Cottle Road in San Jose *SNIP* Just for clarification, these locations are one in the same. And as an update, the splicing operations are done at this location. (I live 3 blocks away The multitudes of crews that were at the site were gone when I drove by at 3:30PM PST today. The splice trailers were still there around 9:30AM PST working on cable. Bobby Glover Director of Information Services South Valley Internet (AS4307)

1 0

Re: BGP FlowSpec support on provider networks
by Richard A Steenbergen 11 Apr '09

11 Apr '09

> I am trying to compile data on which providers are currently > supporting BGP Flowspec at their edge, if there are any at all. The > few providers I've reached out to have indicated they do not support > this and have no intention of supporting this any time in the near > future. I'm also curious why something so useful as to have the > ability to advertise flow specification information in NLRI and > distribute filtering information is taking so long to gain a foothold > in the industry... <shamelessplug> nLayer has offered flowspec support to customers for many years now. </shamelessplug> It's really quite simple to use and support too, if you happen to have a largely Juniper based network that is. I'm not aware of any other router vendor who currently supports it, but the loss is entirely theirs. We do have a fair bit of Crisco in the network, with Juniper primarily in the core and peering/transit edge, so we use a route-server to feed the flowspec routes into the Juniper core. Customers set up an ebgp multihop session with it, and can announce flowspec routes (or standard blackhole via bgp communities) for anything in their register prefix-list. It's also quite handy for distributing internal use packet filters too. As for why something so (insanely) useful is slow to be adopted... There are a few reasons, but mostly: 1) A healthy dose of inter-vendor politics. 2) A silly religious belief that bgp shouldn't be used to carry firewall information, and that some other protocol should be invented instead. I think the counter-argument to that is the ability to do inter-provider filtering is precisely why it should be done via bgp. and the success of the current implementation proves how well it works. 3) Another large network who shall remain nameless once used a third party flowspec speaking piece of software which shall also remain nameless, and managed to blackhole their entire network for a noticeable amount of time. As with anything combining the words "network wide protocol" and "packet filter", a healthy amount of user discretion is advised. -- Richard A Steenbergen <ras(a)e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)

1 0

RE: Outside plant protection, fiber cuts, interwebz down oh noes!
by Carlos Alcantar 10 Apr '09

10 Apr '09

Your right about having the right tools whats a manhole hook cost $50 -carlos -----Original Message----- From: Daryl G. Jurbala [mailto:daryl@introspect.net] Sent: Friday, April 10, 2009 10:37 AM To: Charles Wyble Cc: nanog(a)nanog.org Subject: Re: Outside plant protection, fiber cuts, interwebz down oh noes! On Apr 9, 2009, at 6:04 PM, Charles Wyble wrote: > > 3) From what I understand it's not trivial to raise a manhole cover. > Most likely can't be done by one person. Can they be locked? Or were > the carriers simply relying on obscurity/barrier to entry? Your understanding is incorrect. I'm an average sized guy and I can pull a manhole cover with one hand on the right tool. It might take 2 hands if it hasn't been opened recently and has lots of pebbles and dirt jammed in around it. It's like everything else: if you know how to do it, and you have the right tool, it's simple. And, yes, you can get lockable manhole covers. They aren't cheap. McGuard make a popular one. (Yes, yes...why would I possibly know any of this.....I'm a fire marshal in a small town as a part time gig, so I have to deal with this kind of thing on a reasonably regular basis) Daryl

5 4

Forward Erasure Correction (FEC) and network performance
by Marshall Eubanks 10 Apr '09

10 Apr '09

Hello; I work with FEC in various ways, mostly to protect video streams against packet loss, including as co-chair of the IETF FECFRAME WG and in the Video Services Forum. Most FEC is driven by congestion in the edge, RF issues on wireless LANs, etc., but there is always the chance of loss in transit over the wider network. In many important cases, in fact, (e.g., transfer of video from a content creator to an IPTV service provider or Enterprise to Enterprise video conferencing) the loss at the edges can be controlled, leaving only network transit to worry about. This question has thus come up from time to time, and I was hoping that the assembled NANOG might be able to either answer it or provide pointers to the literature : What level of packet loss would trigger response from network operators ? How bad does a sustained packet loss need to be before it is viewed as a problem to be fixed ? Conversely, what is a typical packet loss fraction during periods of good network performance ? If there is some consensus around this, it would effectively set an upper bound for the need for FEC in network transit. I would be glad to accept replies in confidence off list if people don't want their networks to be identified. (To be clear, I am aware that many ISPs offer some sort of MPLS service with a packet loss SLA for video carriage. I am really asking about Internet transport here, although I would be pleased to learn of MPLS statistics if anyone wants to provide them.) Regards Marshall Eubanks

6 7

Re: Vandalism Likely In Big South Bay Phone Outage
by Martin Hannigan 10 Apr '09

10 Apr '09

The reward is effective and the one of the best uses of their funds in responding to this event. More outside plant spending is not effective when you are dealing with motivated individuals. I'd like to reemphasize that you can't spend enough on outside or inside plant to stop this type of thing. It is much more cost effective to stalk the executors with rewards and prosecution as a detterent. Best, Martin On 4/10/09, Bob Bradlee <Bob(a)bradlee.org> wrote: > > Sounds to me like an ongoing dispute may be close to the bottom of this. > > http://blogs.barrons.com/techtraderdaily/2009/04/06/att-union-contract-expi… > > AT&T's answer is to place a $100k bounty on the vandals. > > The other Bob > > > > > -- Martin Hannigan martin(a)theicelandguy.com p: +16178216079 Power, Network, and Costs Consulting for Iceland Datacenters and Occupants

5 5

Weekly Routing Table Report
by Routing Analysis Role Account 10 Apr '09

10 Apr '09

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 11 Apr, 2009 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 284772 Prefixes after maximum aggregation: 134860 Deaggregation factor: 2.11 Unique aggregates announced to Internet: 140279 Total ASes present in the Internet Routing Table: 30988 Prefixes per ASN: 9.19 Origin-only ASes present in the Internet Routing Table: 26974 Origin ASes announcing only one prefix: 13104 Transit ASes present in the Internet Routing Table: 4014 Transit-only ASes present in the Internet Routing Table: 96 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 28 Max AS path prepend of ASN (12445) 18 Prefixes from unregistered ASNs in the Routing Table: 466 Unregistered ASNs in the Routing Table: 154 Number of 32-bit ASNs allocated by the RIRs: 141 Prefixes from 32-bit ASNs in the Routing Table: 21 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 216 Number of addresses announced to Internet: 2028311744 Equivalent to 120 /8s, 229 /16s and 148 /24s Percentage of available address space announced: 54.7 Percentage of allocated address space announced: 64.0 Percentage of available address space allocated: 85.5 Percentage of address space in use by end-sites: 76.3 Total number of prefixes smaller than registry allocations: 140014 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 66071 Total APNIC prefixes after maximum aggregation: 23545 APNIC Deaggregation factor: 2.81 Prefixes being announced from the APNIC address blocks: 62831 Unique aggregates announced from the APNIC address blocks: 28740 APNIC Region origin ASes present in the Internet Routing Table: 3599 APNIC Prefixes per ASN: 17.46 APNIC Region origin ASes announcing only one prefix: 972 APNIC Region transit ASes present in the Internet Routing Table: 552 Average APNIC Region AS path length visible: 3.6 Max APNIC Region AS path length visible: 18 Number of APNIC addresses announced to Internet: 410009632 Equivalent to 24 /8s, 112 /16s and 64 /24s Percentage of available APNIC address space announced: 81.5 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: 124382 Total ARIN prefixes after maximum aggregation: 65792 ARIN Deaggregation factor: 1.89 Prefixes being announced from the ARIN address blocks: 93794 Unique aggregates announced from the ARIN address blocks: 36496 ARIN Region origin ASes present in the Internet Routing Table: 12905 ARIN Prefixes per ASN: 7.27 ARIN Region origin ASes announcing only one prefix: 4975 ARIN Region transit ASes present in the Internet Routing Table: 1248 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 20 Number of ARIN addresses announced to Internet: 423891200 Equivalent to 25 /8s, 68 /16s and 17 /24s Percentage of available ARIN address space announced: 81.5 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, 108/8, 173/8, 174/8, 184/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: 65290 Total RIPE prefixes after maximum aggregation: 37961 RIPE Deaggregation factor: 1.72 Prefixes being announced from the RIPE address blocks: 59837 Unique aggregates announced from the RIPE address blocks: 39912 RIPE Region origin ASes present in the Internet Routing Table: 12866 RIPE Prefixes per ASN: 4.65 RIPE Region origin ASes announcing only one prefix: 6724 RIPE Region transit ASes present in the Internet Routing Table: 1940 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 26 Number of RIPE addresses announced to Internet: 392731424 Equivalent to 23 /8s, 104 /16s and 155 /24s Percentage of available RIPE address space announced: 83.6 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-52223 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, 109/8, 178/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 23758 Total LACNIC prefixes after maximum aggregation: 5825 LACNIC Deaggregation factor: 4.08 Prefixes being announced from the LACNIC address blocks: 21967 Unique aggregates announced from the LACNIC address blocks: 11938 LACNIC Region origin ASes present in the Internet Routing Table: 1089 LACNIC Prefixes per ASN: 20.17 LACNIC Region origin ASes announcing only one prefix: 346 LACNIC Region transit ASes present in the Internet Routing Table: 174 Average LACNIC Region AS path length visible: 4.1 Max LACNIC Region AS path length visible: 28 Number of LACNIC addresses announced to Internet: 62202240 Equivalent to 3 /8s, 181 /16s and 33 /24s Percentage of available LACNIC address space announced: 61.8 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247 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: 4843 Total AfriNIC prefixes after maximum aggregation: 1393 AfriNIC Deaggregation factor: 3.48 Prefixes being announced from the AfriNIC address blocks: 4481 Unique aggregates announced from the AfriNIC address blocks: 1360 AfriNIC Region origin ASes present in the Internet Routing Table: 289 AfriNIC Prefixes per ASN: 15.51 AfriNIC Region origin ASes announcing only one prefix: 87 AfriNIC Region transit ASes present in the Internet Routing Table: 55 Average AfriNIC Region AS path length visible: 3.9 Max AfriNIC Region AS path length visible: 15 Number of AfriNIC addresses announced to Internet: 10201344 Equivalent to 0 /8s, 155 /16s and 169 /24s Percentage of available AfriNIC address space announced: 30.4 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 1691 6929 395 Korea Telecom (KIX) 17488 1537 122 96 Hathway IP Over Cable Interne 4755 1180 405 180 TATA Communications formerly 9583 1087 86 539 Sify Limited 4134 891 16388 368 CHINANET-BACKBONE 7545 785 164 106 TPG Internet Pty Ltd 18101 755 216 30 Reliance Infocom Ltd Internet 24560 681 228 174 Bharti Airtel Ltd. 9498 664 296 50 BHARTI BT INTERNET LTD. 9829 638 491 20 BSNL National Internet Backbo 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 4305 3669 345 bellsouth.net, inc. 209 2644 4151 622 Qwest 4323 1827 1049 376 Time Warner Telecom 1785 1744 717 138 PaeTec Communications, Inc. 20115 1593 1425 723 Charter Communications 7018 1445 5895 1018 AT&T WorldNet Services 6478 1317 297 483 AT&T Worldnet Services 2386 1249 681 898 AT&T Data Communications Serv 11492 1211 192 11 Cable One 3356 1193 10979 452 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 1193 188 7 TEDATA 30890 544 88 199 SC Kappa Invexim SRL 3292 450 1764 388 TDC Tele Danmark 12479 401 578 6 Uni2 Autonomous System 3320 343 7081 294 Deutsche Telekom AG 3215 340 3025 108 France Telecom Transpac 3301 340 1685 305 TeliaNet Sweden 8866 337 109 22 Bulgarian Telecommunication C 29049 320 26 3 AzerSat LLC. 35805 316 24 4 United Telecom of Georgia 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 1442 2848 232 UniNet S.A. de C.V. 10620 854 194 102 TVCABLE BOGOTA 22047 604 302 14 VTR PUNTO NET S.A. 16814 589 31 10 NSS, S.A. 7303 520 265 72 Telecom Argentina Stet-France 11830 518 294 42 Instituto Costarricense de El 6471 442 96 31 ENTEL CHILE S.A. 11172 411 102 72 Servicios Alestra S.A de C.V 28573 399 526 25 NET Servicos de Comunicao S.A 7738 397 794 28 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 852 77 36 LINKdotNET AS number 20858 296 34 4 This AS will be used to conne 3741 277 860 237 The Internet Solution 2018 242 215 142 Tertiary Education Network 6713 159 150 15 Itissalat Al-MAGHRIB 33783 148 10 8 EEPAD TISP TELECOM & INTERNET 29571 138 15 9 Ci Telecom Autonomous system 5536 123 8 9 Internet Egypt Network 5713 115 507 66 Telkom SA Ltd 33776 109 6 3 Starcomms Nigeria Limited 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 4305 3669 345 bellsouth.net, inc. 209 2644 4151 622 Qwest 4323 1827 1049 376 Time Warner Telecom 1785 1744 717 138 PaeTec Communications, Inc. 4766 1691 6929 395 Korea Telecom (KIX) 20115 1593 1425 723 Charter Communications 17488 1537 122 96 Hathway IP Over Cable Interne 7018 1445 5895 1018 AT&T WorldNet Services 8151 1442 2848 232 UniNet S.A. de C.V. 6478 1317 297 483 AT&T Worldnet Services Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 209 2644 2022 Qwest 1785 1744 1606 PaeTec Communications, Inc. 4323 1827 1451 Time Warner Telecom 17488 1537 1441 Hathway IP Over Cable Interne 4766 1691 1296 Korea Telecom (KIX) 8151 1442 1210 UniNet S.A. de C.V. 11492 1211 1200 Cable One 8452 1193 1186 TEDATA 18566 1060 1050 Covad Communications 4755 1180 1000 TATA Communications formerly 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.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services 41.220.16.0/20 8668 TelOne Zimbabwe P/L 41.223.112.0/22 5713 Telkom SA Ltd 41.223.188.0/24 22351 Intelsat 41.223.189.0/24 26452 Local Communications Networks 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 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:19 /9:10 /10:20 /11:57 /12:163 /13:334 /14:588 /15:1148 /16:10423 /17:4676 /18:8037 /19:17039 /20:20250 /21:20014 /22:25589 /23:25339 /24:149117 /25:644 /26:792 /27:341 /28:117 /29:37 /30:10 /31:0 /32:8 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2806 4305 bellsouth.net, inc. 4766 1393 1691 Korea Telecom (KIX) 209 1350 2644 Qwest 17488 1306 1537 Hathway IP Over Cable Interne 8452 1172 1193 TEDATA 11492 1160 1211 Cable One 1785 1152 1744 PaeTec Communications, Inc. 18566 1041 1060 Covad Communications 4323 953 1827 Time Warner Telecom 2386 949 1249 AT&T Data Communications Serv Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:13 8:178 12:2196 13:3 15:19 16:3 17:4 20:35 24:1100 32:51 38:549 40:97 41:1940 43:1 44:2 45:1 47:22 52:3 55:2 56:3 57:25 58:565 59:622 60:460 61:1107 62:1068 63:2023 64:3629 65:2410 66:3602 67:1490 68:706 69:2546 70:527 71:132 72:1645 73:2 74:1481 75:167 76:311 77:836 78:553 79:311 80:971 81:821 82:527 83:409 84:613 85:1020 86:393 87:634 88:358 89:1446 90:42 91:2132 92:334 93:1104 94:1191 95:1023 96:105 97:185 98:226 99:17 109:1 110:58 112:93 113:94 114:214 115:227 116:1150 117:493 118:283 119:704 120:149 121:713 122:997 123:537 124:957 125:1306 128:224 129:227 130:129 131:414 132:74 133:9 134:183 135:38 136:242 137:150 138:148 139:77 140:423 141:103 142:391 143:323 144:331 145:45 146:370 147:152 148:519 149:235 150:145 151:199 152:150 153:130 154:11 155:269 156:171 157:300 158:127 159:273 160:282 161:134 162:273 163:149 164:483 165:531 166:268 167:360 168:692 169:161 170:473 171:38 172:10 173:266 174:168 178:1 186:8 187:74 188:11 189:343 190:2746 192:5795 193:4233 194:3322 195:2682 196:1061 198:3738 199:3311 200:5504 201:1362 202:7902 203:8097 204:3796 205:2158 206:2390 207:2804 208:3902 209:3407 210:2649 211:1097 212:1521 213:1729 214:71 215:30 216:4554 217:1257 218:361 219:413 220:1210 221:452 222:289 End of report

1 0