- Test - lists.nanog.org

It worked! Huge Thanks Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
by Gordon Cook 04 Oct '13

04 Oct '13

Really glad i posted take a boqand thank you again! ============================================================= The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: http://www.cookreport.com/index.php?option=com_docman&task=cat_view&gid=37&… Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_content&view=article&id=54&I… ============================================================= On Oct 4, 2013, at 3:50 PM, "Moore, Matthew S" <mscott.moore(a)verizon.com> wrote: > Thanks eric...scott > > From: Sieg, Eric W > Sent: Friday, October 4, 2013 3:14 PM > To: Christopher Morrow > Cc: Moore, Matthew S; Gordon Cook; Young, David E > Subject: RE: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? > > Everything is complete, all associated prefix-lists for this customer have been updated. > > Thank you for choosing Verizon, > > Eric Sieg > IP Non Managed Operations Support | IP/DNS/DNE Administration > Tel: 248 728 5294 | Vnet: 443-5294 > > <image001.gif> > <image002.jpg> <image003.jpg> <image004.jpg> <image005.jpg> > > From: christopher.morrow(a)gmail.com [mailto:christopher.morrow@gmail.com] On Behalf Of Christopher Morrow > Sent: Friday, October 04, 2013 3:01 PM > To: Sieg, Eric W > Cc: Moore, Matthew S; Gordon Cook; Young, David E > Subject: Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? > > > > > On Fri, Oct 4, 2013 at 2:59 PM, Christopher Morrow <morrowc.lists(a)gmail.com> wrote: > > > > On Fri, Oct 4, 2013 at 2:54 PM, Sieg, Eric W <eric.sieg(a)verizon.com> wrote: > I’ll get it added to their other sites and follow up with them to let them know. Give me about 20. > > > sweet, thanks! > > forgot, from a fios customer perspective: > 2 G0-9-4-6.WASHDC-LCR-22.verizon-gni.net (130.81.183.118) 10.434 ms 6.308 ms 3.699 ms > 3 ae6-0.RES-BB-RTR1.verizon-gni.net (130.81.199.146) 5.45 ms ae5-0.RES-BB-RTR1.verizon-gni.net (130.81.209.222) 3.375 ms ae2-0.RES-BB-RTR1.verizon-gni.net (130.81.199.138) 4.592 ms > 4 0.ae4.XL2.IAD8.ALTER.NET (152.63.8.125) 8.32 ms 3.457 ms 5.700 ms > 5 0.xe-9-3-0.GW9.IAD8.ALTER.NET (152.63.36.34) 5.820 ms 0.xe-9-0-0.GW9.IAD8.ALTER.NET (152.63.36.18) 7.311 ms 0.xe-11-2-1.GW9.IAD8.ALTER.NET (152.63.42.2) 6.568 ms > 6 telefonica-gw.customer.alter.net (152.179.50.114) 3.767 ms 4.74 ms 5.569 ms > 7 Te0-7-0-5-grtmiana4.red.telefonica-wholesale.net (94.142.126.182) 48.345 ms 46.997 ms Xe4-1-6-0-grtmiana2.red.telefonica-wholesale.net(94.142.123.145) 46.154 ms > 8 176.52.251.197 (176.52.251.197) 44.747 ms 176.52.251.189 (176.52.251.189) 74.746 ms 176.52.249.241 (176.52.249.241) 49.805 ms > 9 176.52.252.66 (176.52.252.66) 99.787 ms 98.471 ms 97.103 ms > ^C > > looks like it works now. > > > Thank you for choosing Verizon, > > Eric Sieg > IP Non Managed Operations Support | IP/DNS/DNE Administration > Tel: 248 728 5294 | Vnet: 443-5294 > > <image001.gif> > <image002.jpg> <image003.jpg> <image004.jpg> <image005.jpg> > > From: Moore, Matthew S > Sent: Friday, October 04, 2013 2:43 PM > To: Christopher Morrow; Gordon Cook > Cc: Young, David E; Sieg, Eric W > Subject: RE: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? > > Hi Chris, > > > > Uncloaking..... ;-) > > > > It does look as though it's a matter of an un-updated prefix-filter for telefonica. The existing filter allows a bunch of /24's > > close to the address in question but 200.10.150.0/24 is not among them, whereas telefonica is announcing it to us. (shown, hidden, below) > > > > scottm(a)GW9.IAD8> show route receive-protocol bgp 152.179.50.114 hidden | match 200.10.150 > > 200.10.150.0/24 152.179.50.114 0 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 I > > > > I added the filter, and I'm cc'ng Eric in Customer Support to let him know. It will make sense to update it across all 12956 sessions, as I only did this one… no longer hidden… > > > > > scottm(a)GW9.IAD8> show route receive-protocol bgp 152.179.50.114 | match 200.10.150 > > * 200.10.150.0/24 152.179.50.114 0 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 I > > > > > > Regards...Scott > > > > -----Original Message----- > From: christopher.morrow(a)gmail.com [mailto:christopher.morrow@gmail.com] On Behalf Of Christopher Morrow > Sent: Friday, October 04, 2013 1:39 PM > To: Gordon Cook > Cc: Young, David E > Subject: Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? > > > > I always go with my standby: scott moore ... he can uncloak from bcc land if he's able/willing/etc to help in this case. > > > > -chris > > > > On Fri, Oct 4, 2013 at 1:37 PM, Gordon Cook <cook(a)cookreport.com> wrote: > > > again thank you very very much. I have to leave routes huit for root canal but i do expect to be back can anyone nominate someone at verizon who would do to checking with telefonca? > > > > > > david young is the only guy i know. > > > > > > But question now is how to rattle a cage at verizon and possible > > > telefonica - I will also send word of this trouble shooting to the > > > folk in ecuador > > > ============================================================= > > > The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: > > > http://www.cookreport.com/index.php?option=com_docman&task=cat_view&gi > > > d=37&Itemid=61 > > > Cook's Collaborative Edge Blog > > > http://www.cookreport.com/wp/ > > > Subscription info: > > > http://www.cookreport.com/index.php?option=com_content&view=article&id > > > =54&Itemid=65 > > > ============================================================= > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Oct 4, 2013, at 1:22 PM, Christopher Morrow <morrowc.lists(a)gmail.com> wrote: > > > > > >> On Fri, Oct 4, 2013 at 1:15 PM, Gordon Cook <cook(a)cookreport.com> wrote: > > >>> Hi chris > > >>> > > >>> really appreciate the help from ALL you guys > > >> > > >> sure thing. > > >> > > >>> does what you just said mean that non reachability for version customer may mean a config problem for a small bloc and not something intentional?? > > >> > > >> that's probably hard to say... I do know that: > > >> > > >> 5 0.xe-9-2-0.GW9.IAD8.ALTER.NET (152.63.36.30) 6.457 ms 6.821 ms > > >> 0.xe-11-2-1.GW9.IAD8.ALTER.NET (152.63.42.2) 5.932 ms > > >> 6 telefonica-gw.customer.alter.net (152.179.50.114) 7.182 ms 5.433 > > >> ms 5.431 ms > > >> 7 Xe4-1-6-0-grtmiana2.red.telefonica-wholesale.net (94.142.123.145) > > >> 47.271 ms 48.381 ms Te0-7-0-5-grtmiana4.red.telefonica-wholesale.net > > >> (94.142.126.182) 50.290 ms > > >> > > >> > > >> telefonica is a 'customer' not a 'peer' of 701, based on their > > >> connectivity. This means that telefonica has to tell 701: "Yo, I need > > >> you to accept routes for x, y, z, ktnxbi!' > > >> > > >> knowing the normal (well, 5yrs ago) config for customers of 701, I > > >> don't expect there'd be special handling of this prefix either... so > > >> I suspect either no one told 701 to accept this, or telefonica > > >> pouched it at the handoff :( > > >> > > >> If they didn't do that, these routes wouldn't be accepted. > > >> If telefonica botched some filter on their side (see the comment > > >> about prepending). > > >> > > >> It's fairly sure though that the prefix isn't 'blackholed'... since > > >> it's everything in the /22 not just the local /32 or /24. Bill > > >> Herrin's on target as well, it's really hard to say from here :) > > >> > > >> -chris > > >> > > >>> > > >>> On Oct 4, 2013, at 12:54 PM, Christopher Morrow <morrowc.lists(a)gmail.com> wrote: > > >>> > > >>>> err.. nothing in the /24 is reachable from 701's perspective (so it > > >>>> seems)... so I'd suspect that there's a routing problem with the > > >>>> /24, in fact the surrounding /24's also seem to be having the same problem. > > >>>> > > >>>> On Fri, Oct 4, 2013 at 12:42 PM, Miles Fidelman > > >>>> <mfidelman(a)meetinghouse.net> wrote: > > >>>>> Also inaccessible from FIOS Boston: > > >>>>> new-host-2:~ mfidelman$ traceroute floksociety.org traceroute to > > >>>>> floksociety.org (200.10.150.169), 64 hops max, 52 byte packets > > >>>>> 1 wireless_broadband_router (192.168.1.1) 1.534 ms 0.853 ms > > >>>>> 0.724 ms > > >>>>> 2 l100.bstnma-vfttp-84.verizon-gni.net (96.252.37.1) 7.619 ms > > >>>>> 6.855 ms > > >>>>> 7.304 ms > > >>>>> 3 200.10.150.169 (200.10.150.169) 10.482 ms !N *^C > > >>>>> > > >>>>> But just fine from our datacenter via xo.net. And the web server > > >>>>> is up - at least to a text browser (Lynx). > > >>>>> > > >>>>> Also via Verizion cell network (Boston area). > > >>>>> > > >>>>> Some kind of routing table glitch or peering issue, perhaps? > > >>>>> > > >>>>> > > >>>>> > > >>>>> William Herrin wrote: > > >>>>>> > > >>>>>> On Fri, Oct 4, 2013 at 12:09 PM, Gordon Cook <cook(a)cookreport.com> wrote: > > >>>>>>>> > > >>>>>>>> traceroute to floksociety.org (200.10.150.169), 64 hops max, 72 > > >>>>>>>> byte packets > > >>>>>>>> 1 192.168.1.1 (192.168.1.1) 0.759 ms 0.309 ms 0.357 ms > > >>>>>>>> 2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 36.778 > > >>>>>>>> ms > > >>>>>>>> 17.508 ms 7.316 ms > > >>>>>>>> 3 * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) > > >>>>>>>> 6.482 ms !N * > > >>>>>>>> 4 * * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) > > >>>>>>>> 7.101 ms !N > > >>>>>>>> 5 * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) > > >>>>>>>> 9.239 ms !N * > > >>>>>>>> 6 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) > > >>>>>>>> 6.823 ms !N * 8.846 ms !N > > >>>>>> > > >>>>>> Inaccessible via FIOS Washington DC too: > > >>>>>> > > >>>>>> traceroute -T -p 80 200.10.150.169 traceroute to 200.10.150.169 > > >>>>>> (200.10.150.169), 30 hops max, 40 byte packets > > >>>>>> 1 L300.WASHDC-VFTTP-91.verizon-gni.net (173.73.47.1) 1.804 ms > > >>>>>> 1.595 ms 1.562 ms > > >>>>>> 2 G0-6-4-7.WASHDC-LCR-22.verizon-gni.net (130.81.216.250) 5.321 > > >>>>>> ms !N > > >>>>>> * * > > >>>>>> > > >>>>>> Correctly accessible via Cox, Qwest, Sprint and others, but the > > >>>>>> network path is really slow and really long. > > >>>>>> > > >>>>>> The border is consistently with telefonica-wholesale.net and then > > >>>>>> telconet.net. Beyond the border there are badly behaving routers, > > >>>>>> including ones configured with RFC 1918 addresses. The > > >>>>>> addressable routers are reachable via Verizon, just not the last hop. > > >>>>>> > > >>>>>> traceroute -T -p 80 200.10.150.169 traceroute to 200.10.150.169 > > >>>>>> (200.10.150.169), 30 hops max, 60 byte packets > > >>>>>> 1 sark.dirtside.com (70.182.189.216) 0.708 ms 0.689 ms 0.569 > > >>>>>> ms > > >>>>>> 2 10.1.192.1 (10.1.192.1) 9.957 ms 9.874 ms 9.725 ms > > >>>>>> 3 ip68-100-3-49.dc.dc.cox.net (68.100.3.49) 9.631 ms 9.507 ms > > >>>>>> 9.424 ms > > >>>>>> 4 ip68-100-3-113.dc.dc.cox.net (68.100.3.113) 9.310 ms 9.226 > > >>>>>> ms > > >>>>>> 9.140 ms > > >>>>>> 5 mrfddsrj02gex070002.rd.dc.cox.net (68.100.0.145) 9.111 ms > > >>>>>> 9.019 ms 8.929 ms > > >>>>>> 6 68.1.4.139 (68.1.4.139) 8.791 ms * 5.981 ms > > >>>>>> 7 209.48.42.61 (209.48.42.61) 5.748 ms 11.361 ms 10.948 ms > > >>>>>> 8 vb2000d2.rar3.washington-dc.us.xo.net (207.88.13.66) 58.454 > > >>>>>> ms > > >>>>>> 52.415 ms 52.421 ms > > >>>>>> 9 te-3-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.9) 60.543 ms > > >>>>>> 60.397 ms 60.378 ms > > >>>>>> 10 te-3-0-0.rar3.dallas-tx.us.xo.net (207.88.12.2) 58.211 ms > > >>>>>> 58.407 ms 58.392 ms > > >>>>>> 11 * * * > > >>>>>> 12 206.111.5.226.ptr.us.xo.net (206.111.5.226) 53.378 ms > > >>>>>> 49.080 ms > > >>>>>> 47.435 ms > > >>>>>> 13 Xe-8-1-0-0-grtmiabr3.red.telefonica-wholesale.net > > >>>>>> (94.142.125.54) > > >>>>>> 76.006 ms Xe8-0-2-0-grtmiabr4.red.telefonica-wholesale.net > > >>>>>> (94.142.119.38) 60.181 ms > > >>>>>> Xe13-1-4-0-grtmiabr4.red.telefonica-wholesale.net > > >>>>>> (213.140.43.109) > > >>>>>> 125.888 ms > > >>>>>> 14 Te-0-2-0-0-grtmiana4.red.telefonica-wholesale.net > > >>>>>> (94.142.119.233) > > >>>>>> 67.105 ms Te0-1-0-0-grtmiana4.red.telefonica-wholesale.net > > >>>>>> (213.140.37.77) 63.435 ms > > >>>>>> Xe5-1-8-0-grtmiana2.red.telefonica-wholesale.net (213.140.36.89) > > >>>>>> 141.873 ms > > >>>>>> 15 Xe9-3-0-0-gramiana4.red.telefonica-wholesale.net > > >>>>>> (94.142.126.197) > > >>>>>> 62.450 ms 176.52.249.245 (176.52.249.245) 66.665 ms > > >>>>>> 176.52.249.241 > > >>>>>> (176.52.249.241) 64.668 ms > > >>>>>> 16 176.52.252.66 (176.52.252.66) 118.619 ms 118.057 ms > > >>>>>> 117.934 ms > > >>>>>> 17 * * * > > >>>>>> 18 * * * > > >>>>>> 19 * * * > > >>>>>> 20 host-186-5-116-193.telconet.net (186.5.116.193) 122.586 ms > > >>>>>> 120.967 ms 115.040 ms > > >>>>>> 21 host-186-101-89-42.telconet.net (186.101.89.42) 122.801 ms > > >>>>>> 125.164 ms 119.520 ms > > >>>>>> 22 * * * > > >>>>>> 23 200.10.150.169 (200.10.150.169) 253.710 ms 246.684 ms > > >>>>>> 244.845 ms > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>> > > >>>>> > > >>>>> -- > > >>>>> In theory, there is no difference between theory and practice. > > >>>>> In practice, there is. .... Yogi Berra > > >>>>> > > >>>>> > > >>>> > > >>> > > > > > >

1 0

Weekly Routing Table Report
by Routing Analysis Role Account 04 Oct '13

04 Oct '13

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, LacNOG, TRNOG, CaribNOG and the RIPE Routing Working Group. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 05 Oct, 2013 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 468683 Prefixes after maximum aggregation: 189054 Deaggregation factor: 2.48 Unique aggregates announced to Internet: 232434 Total ASes present in the Internet Routing Table: 45122 Prefixes per ASN: 10.39 Origin-only ASes present in the Internet Routing Table: 35242 Origin ASes announcing only one prefix: 16252 Transit ASes present in the Internet Routing Table: 5902 Transit-only ASes present in the Internet Routing Table: 166 Average AS path length visible in the Internet Routing Table: 4.6 Max AS path length visible: 30 Max AS path prepend of ASN ( 36992) 22 Prefixes from unregistered ASNs in the Routing Table: 338 Unregistered ASNs in the Routing Table: 189 Number of 32-bit ASNs allocated by the RIRs: 5144 Number of 32-bit ASNs visible in the Routing Table: 3978 Prefixes from 32-bit ASNs in the Routing Table: 12238 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 665 Number of addresses announced to Internet: 2647718900 Equivalent to 157 /8s, 208 /16s and 251 /24s Percentage of available address space announced: 71.5 Percentage of allocated address space announced: 71.5 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 95.0 Total number of prefixes smaller than registry allocations: 164010 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 111126 Total APNIC prefixes after maximum aggregation: 33829 APNIC Deaggregation factor: 3.28 Prefixes being announced from the APNIC address blocks: 113153 Unique aggregates announced from the APNIC address blocks: 46794 APNIC Region origin ASes present in the Internet Routing Table: 4872 APNIC Prefixes per ASN: 23.23 APNIC Region origin ASes announcing only one prefix: 1218 APNIC Region transit ASes present in the Internet Routing Table: 821 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 21 Number of APNIC region 32-bit ASNs visible in the Routing Table: 692 Number of APNIC addresses announced to Internet: 728412160 Equivalent to 43 /8s, 106 /16s and 176 /24s Percentage of available APNIC address space announced: 85.1 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-63999, 131072-133631 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/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, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 162812 Total ARIN prefixes after maximum aggregation: 81536 ARIN Deaggregation factor: 2.00 Prefixes being announced from the ARIN address blocks: 163305 Unique aggregates announced from the ARIN address blocks: 75874 ARIN Region origin ASes present in the Internet Routing Table: 15904 ARIN Prefixes per ASN: 10.27 ARIN Region origin ASes announcing only one prefix: 6017 ARIN Region transit ASes present in the Internet Routing Table: 1660 Average ARIN Region AS path length visible: 4.1 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 22 Number of ARIN addresses announced to Internet: 1072976640 Equivalent to 63 /8s, 244 /16s and 83 /24s Percentage of available ARIN address space announced: 56.8 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 53248-55295, 62464-63487, 393216-394239 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/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, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 118832 Total RIPE prefixes after maximum aggregation: 61246 RIPE Deaggregation factor: 1.94 Prefixes being announced from the RIPE address blocks: 122391 Unique aggregates announced from the RIPE address blocks: 78886 RIPE Region origin ASes present in the Internet Routing Table: 17455 RIPE Prefixes per ASN: 7.01 RIPE Region origin ASes announcing only one prefix: 8261 RIPE Region transit ASes present in the Internet Routing Table: 2814 Average RIPE Region AS path length visible: 5.1 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 2406 Number of RIPE addresses announced to Internet: 656682980 Equivalent to 39 /8s, 36 /16s and 47 /24s Percentage of available RIPE address space announced: 95.5 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, 56320-58367 59392-61439, 61952-62463, 196608-200191 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 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, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 51953 Total LACNIC prefixes after maximum aggregation: 9822 LACNIC Deaggregation factor: 5.29 Prefixes being announced from the LACNIC address blocks: 56961 Unique aggregates announced from the LACNIC address blocks: 26309 LACNIC Region origin ASes present in the Internet Routing Table: 2030 LACNIC Prefixes per ASN: 28.06 LACNIC Region origin ASes announcing only one prefix: 563 LACNIC Region transit ASes present in the Internet Routing Table: 385 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 852 Number of LACNIC addresses announced to Internet: 140082192 Equivalent to 8 /8s, 89 /16s and 124 /24s Percentage of available LACNIC address space announced: 83.5 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 262144-263679 plus ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 11572 Total AfriNIC prefixes after maximum aggregation: 2533 AfriNIC Deaggregation factor: 4.57 Prefixes being announced from the AfriNIC address blocks: 12208 Unique aggregates announced from the AfriNIC address blocks: 3999 AfriNIC Region origin ASes present in the Internet Routing Table: 653 AfriNIC Prefixes per ASN: 18.70 AfriNIC Region origin ASes announcing only one prefix: 193 AfriNIC Region transit ASes present in the Internet Routing Table: 137 Average AfriNIC Region AS path length visible: 4.8 Max AfriNIC Region AS path length visible: 24 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 6 Number of AfriNIC addresses announced to Internet: 47751424 Equivalent to 2 /8s, 216 /16s and 161 /24s Percentage of available AfriNIC address space announced: 47.4 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 2947 11563 946 Korea Telecom (KIX) 17974 2698 903 90 PT TELEKOMUNIKASI INDONESIA 7545 2084 321 112 TPG Internet Pty Ltd 4755 1769 391 187 TATA Communications formerly 9829 1548 1236 41 BSNL National Internet Backbo 9583 1237 93 507 Sify Limited 9498 1196 309 72 BHARTI Airtel Ltd. 4808 1191 2131 347 CNCGROUP IP network: China169 7552 1164 1080 13 Vietel Corporation 24560 1091 380 164 Bharti Airtel Ltd., Telemedia Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 3061 3689 59 BellSouth.net Inc. 18566 2066 382 184 Covad Communications 22773 2055 2943 140 Cox Communications, Inc. 1785 2019 679 125 PaeTec Communications, Inc. 20115 1682 1651 619 Charter Communications 4323 1625 1104 419 Time Warner Telecom 701 1516 11148 789 UUNET Technologies, Inc. 30036 1337 301 638 Mediacom Communications Corp 7018 1331 17499 857 AT&T WorldNet Services 6983 1294 772 579 ITC^Deltacom Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8402 1851 544 17 OJSC "Vimpelcom" 34984 1364 244 221 TELLCOM ILETISIM HIZMETLERI A 20940 1040 383 801 Akamai Technologies European 31148 992 44 19 FreeNet ISP 6830 891 2365 425 UPC Distribution Services 13188 849 99 67 TOV "Bank-Inform" 8551 750 370 41 Bezeq International 12479 680 799 49 Uni2 Autonomous System 35228 528 246 16 Avatar Broadband Limited 3320 514 8418 406 Deutsche Telekom AG Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 28573 3362 1734 88 NET Servicos de Comunicao S.A 10620 2599 423 245 TVCABLE BOGOTA 7303 1724 1135 233 Telecom Argentina Stet-France 18881 1462 844 20 Global Village Telecom 8151 1340 2805 413 UniNet S.A. de C.V. 11830 865 364 15 Instituto Costarricense de El 6503 851 434 63 AVANTEL, S.A. 27947 837 93 91 Telconet S.A 6147 799 373 27 Telefonica Del Peru 7738 780 1498 36 Telecomunicacoes da Bahia S.A Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 36998 1864 112 5 Sudanese Mobile Telephone (ZA 24863 882 306 30 LINKdotNET AS number 6713 554 633 26 Itissalat Al-MAGHRIB 8452 421 956 9 TEDATA 24835 292 80 8 RAYA Telecom - Egypt 3741 258 921 216 The Internet Solution 29571 223 17 12 Ci Telecom Autonomous system 36992 222 501 28 Etisalat MISR 15706 221 32 6 Sudatel Internet Exchange Aut 29975 192 668 21 Vodacom Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 28573 3362 1734 88 NET Servicos de Comunicao S.A 6389 3061 3689 59 BellSouth.net Inc. 4766 2947 11563 946 Korea Telecom (KIX) 17974 2698 903 90 PT TELEKOMUNIKASI INDONESIA 10620 2599 423 245 TVCABLE BOGOTA 7545 2084 321 112 TPG Internet Pty Ltd 18566 2066 382 184 Covad Communications 22773 2055 2943 140 Cox Communications, Inc. 1785 2019 679 125 PaeTec Communications, Inc. 36998 1864 112 5 Sudanese Mobile Telephone (ZA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 6389 3061 3002 BellSouth.net Inc. 17974 2698 2608 PT TELEKOMUNIKASI INDONESIA 10620 2599 2354 TVCABLE BOGOTA 4766 2947 2001 Korea Telecom (KIX) 7545 2084 1972 TPG Internet Pty Ltd 22773 2055 1915 Cox Communications, Inc. 1785 2019 1894 PaeTec Communications, Inc. 18566 2066 1882 Covad Communications 36998 1864 1859 Sudanese Mobile Telephone (ZA 8402 1851 1834 OJSC "Vimpelcom" Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 30031 UNALLOCATED 12.27.122.0/24 7018 AT&T WorldNet Servic 62719 UNALLOCATED 12.27.130.0/24 4323 Time Warner Telecom 13317 UNALLOCATED 12.44.10.0/24 7018 AT&T WorldNet Servic 23502 UNALLOCATED 12.44.44.0/24 7018 AT&T WorldNet Servic 17300 UNALLOCATED 12.45.103.0/24 209 Qwest 17300 UNALLOCATED 12.45.110.0/24 701 UUNET Technologies, 16476 UNALLOCATED 12.46.27.0/24 7018 AT&T WorldNet Servic 14764 UNALLOCATED 12.108.237.0/24 7018 AT&T WorldNet Servic 33649 UNALLOCATED 12.111.112.0/24 19029 New Edge Networks Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.100.0.0/24 4847 China Networks Inter-Exchange Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.90.128.0/18 27418 OUTOFWALL INC. 23.90.192.0/18 36086 Broad Communications Technolo 23.91.0.0/19 40676 Psychz Networks 23.91.32.0/19 36315 Servpac Inc. 23.91.96.0/20 40676 Psychz Networks 23.91.112.0/21 32475 MidPhase Inc. 23.91.160.0/22 36493 3757277 Canada Inc. (oa 295.c 23.91.160.0/19 36493 3757277 Canada Inc. (oa 295.c 23.91.164.0/22 36493 3757277 Canada Inc. (oa 295.c 23.91.168.0/22 36493 3757277 Canada Inc. (oa 295.c Complete listing at http://thyme.rand.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:16 /9:11 /10:31 /11:92 /12:251 /13:481 /14:913 /15:1625 /16:12818 /17:6700 /18:11231 /19:22971 /20:32614 /21:35281 /22:49729 /23:43015 /24:248381 /25:895 /26:994 /27:475 /28:49 /29:78 /30:18 /31:0 /32:14 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 2017 2066 Covad Communications 36998 1829 1864 Sudanese Mobile Telephone (ZA 6389 1710 3061 BellSouth.net Inc. 8402 1572 1851 OJSC "Vimpelcom" 22773 1327 2055 Cox Communications, Inc. 11492 1194 1235 Cable One 30036 1194 1337 Mediacom Communications Corp 1785 1085 2019 PaeTec Communications, Inc. 6983 1034 1294 ITC^Deltacom 22561 962 1237 Digital Teleport, Inc Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:833 2:860 3:3 4:17 5:993 6:19 8:612 12:1896 13:3 14:872 15:11 16:3 17:14 18:19 20:21 23:451 24:1719 27:1597 31:1476 32:45 33:2 34:5 36:81 37:1822 38:907 39:2 40:179 41:3253 42:249 44:14 46:2022 47:6 49:678 50:840 52:12 54:39 55:3 57:26 58:1164 59:611 60:351 61:1425 62:1185 63:1978 64:4544 65:2346 66:4179 67:2073 68:1089 69:3325 70:859 71:496 72:1994 74:2561 75:326 76:306 77:1166 78:1058 79:648 80:1328 81:1021 82:625 83:587 84:594 85:1256 86:456 87:1015 88:555 89:1723 90:157 91:5640 92:612 93:1624 94:1981 95:1628 96:511 97:343 98:1035 99:43 100:31 101:611 103:3351 105:520 106:143 107:212 108:509 109:1875 110:963 111:1127 112:582 113:787 114:730 115:1013 116:984 117:829 118:1167 119:1299 120:370 121:735 122:1884 123:1222 124:1359 125:1424 128:619 129:325 130:323 131:646 132:349 133:162 134:548 135:67 136:275 137:269 138:350 139:180 140:181 141:324 142:548 143:417 144:499 145:103 146:517 147:403 148:702 149:351 150:157 151:598 152:412 153:200 154:47 155:488 156:281 157:422 158:285 159:758 160:348 161:448 162:735 163:227 164:633 165:572 166:258 167:621 168:1044 169:126 170:1081 171:200 172:25 173:1618 174:664 175:506 176:1247 177:2332 178:1917 179:160 180:1555 181:744 182:1331 183:480 184:657 185:908 186:2606 187:1462 188:1872 189:1336 190:7178 192:7001 193:5616 194:4062 195:3335 196:1314 197:992 198:4682 199:5475 200:6061 201:2530 202:8974 203:8924 204:4504 205:2617 206:2848 207:2892 208:4006 209:3619 210:2948 211:1575 212:2262 213:2012 214:901 215:99 216:5405 217:1669 218:622 219:315 220:1279 221:566 222:326 223:504 End of report

1 0

CBL Abuse
by J. Oquendo 03 Oct '13

03 Oct '13

Does someone know of a direct contact with someone at cbl.abuse.org have a quick question/comment/concern I would like to address that WILL get lost in "forms" method of "contact us." -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM "Where ignorance is our master, there is no possibility of real peace" - Dalai Lama 42B0 5A53 6505 6638 44BB 3943 2BF7 D83F 210A 95AF http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF

2 1

IP Fragmentation - Not reliable over the Internet?
by Christopher Palmer 03 Oct '13

03 Oct '13

I am trolling for information/community wisdom. What is the probability that a random path between two Internet hosts will traverse a middlebox that drops or otherwise barfs on fragmented IPv4 packets? If anyone has any data or anecdotes, please feel free to send an off-list email or whatever. Thanks! ----------------------------------------------------------- Christopher.Palmer(a)microsoft.com Program Manager Windows Networking Core - Client Technologies

18 33

Someone from PCCW NOC here ?
by Carlos Martinez-Cagnazzo 02 Oct '13

02 Oct '13

Hi all, We'd appreciate having someone from PCCW, particularly from their operation in Panama, having contact us. Private is fine. A downstream customer from them in Panama has been observed hijacking some prefixes. regards ~Carlos -- -- ========================= Carlos M. Martinez-Cagnazzo h <http://cagnazzo.name>ttp://cagnazzo.me =========================

6 8

Final Agenda Published - NANOG 59
by David Temkin 02 Oct '13

02 Oct '13

All, The final agenda for our meeting next week has been published at http://www.nanog.org/meetings/nanog59/agenda Please note that the program begins at 10AM on Monday and the tutorials can now be found on Tuesday morning. I hope you all share the excitement that I do for this great program. For newcomers, we'll host a welcome lunch on Monday at noon. Even if you're an old timer, we'd love to have you at this lunch to help introduce this potentially record-breaking crowd (we sit at 594 registered attendees at this moment) to NANOG and help them get the most of their time at the meeting. We'll provide you with more information on-site, and as always, feel free to seek out a member of any of the committees - Program, Development, Communications, and of course, the Board of Directors, if you have any questions. I promise we're a friendly bunch! Best Regards, -Dave Temkin Chair, NANOG Program Committee

1 0

semi-ot: network monitoring tools
by John Levine 02 Oct '13

02 Oct '13

I was talking to a bunch of people who run ISPs and other networks in LDCs (yes, including Nigeria) and someone asked about monitoring tools to watch traffic on his network so he can get advance warning of dodgy customers and prevent complaints and blacklisting. These people are plenty smart, but don't have a lot of money. Suggestions welcome. R's, John

6 6

Facebook NOC Contact
by Daniel Hood 01 Oct '13

01 Oct '13

Hi, Having some issues with traffic to Facebook. Is there anyone here from Facebook lurking on the list? Or does anyone have a better contact then their help form? Regards, Daniel

2 1

Re: minimum IPv6 announcement size
by Larry Sheldon 01 Oct '13

01 Oct '13

On 9/27/2013 1:10 AM, Ryan McIntosh wrote: > I don't respond to many of these threads but I have to say I've > contested this one too only to have to beaten into my head that a /64 > is "appropriate".. it still hasn't stuck, but unfortunately rfc's for > other protocols depend on the blocks to now be a /64.. > > It's a waste, even if we're "planning for the future", no one house > needs a /64 sitting on their lan.. or at least none I can sensibly > think of o_O. Are you accounting for connections to your refrigerator, water heater, razor, vibrator, and on down to list so the gubermint can tell they when you can use power for them? -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

5 4

Re: minimum IPv6 announcement size
by Scott Weeks 01 Oct '13

01 Oct '13

--- owen(a)delong.com wrote: From: Owen DeLong <owen(a)delong.com> we will have plenty of address space to number the internet for many many years. ---------------------------------------------- You can't know the future and what addressing requirements it'll bring: "I have to say that in 1981, making those decisions, I felt like I was providing enough freedom for 10 years. That is, a move from 64k to 640k felt like something that would last a great deal of time. Well, it didn't - it took about only 6 years before people started to see that as a real problem." scott

1 0