verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Dear NANOG The Ecuadoran government has via the FLOK society hired Michel Bauwens of the P2p foundation to lead a two year long efforts to revision the ecudoran economy along the lines of a commons oriented collaborative society. I am very interested in the program yet i have NEVER been able to connect to their web site. At the end of two hours of trouble shooting with apple i was advised to call verizon. I am a FiOS customer on a two year contact. The traceroute below confirmed that the fault is in verizons network. The verizon tech agreed otherwise i never would have gotten the trouble ticket my verizon trouble ticket is NJ DQ04PWR9. Can someone tell me what number to call to pursue resolution of this trouble ticket? as of 12:04 eastern time i still cannot connect 24 hours was the promise 14 of the 24 have elapsed 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 Traceroute has started… traceroute to 200.10.150.169 (200.10.150.169), 64 hops max, 72 byte packets 1 192.168.1.1 (192.168.1.1) 0.622 ms 0.305 ms 0.361 ms 2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 6.633 ms 4.892 ms 4.809 ms 3 * * * 4 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 10.441 ms !N * * 5 * * * 6 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 9.932 ms !N * * 7 * * * 8 * * * 9 * * * 10 * * * 11 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 9.765 ms !N * * 12 * * * 13 * * *= Lookup has started… Trying floksociety.org ;; -HEADER- opcode: QUERY, status: NOERROR, id: 13700 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;floksociety.org. INANY ;; ANSWER SECTION: floksociety.org. 600 INA 200.10.150.169 floksociety.org. 3600INMX 10 mail.floksociety.org. floksociety.org. 3600INNS ns57.domaincontrol.com. floksociety.org. 3600INNS ns58.domaincontrol.com. floksociety.org. 3600INSOAns57.domaincontrol.com. dns.jomax.net. 2013092400 28800 7200 604800 600 Received 174 bytes from 8.8.8.8#53 in 139 ms = The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: http://www.cookreport.com/index.php?option=com_docmantask=cat_viewgid=37Itemid=61 Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_contentview=articleid=54Itemid=65 =
RE: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
My traceroute goes through, but we don't go through Verizon. However, the web server is returning an error that it is unavailable. It's possible that the destination web server has a geo location plug in that stops access from foreign locations, or that their server is down. [root@lancaster ~]# traceroute -I 200.10.150.169 traceroute to 200.10.150.169 (200.10.150.169), 30 hops max, 40 byte packets 1 129.77.108.252 (129.77.108.252) 0.345 ms 0.384 ms 0.442 ms 2 switch-user1.ox.com (129.77.154.253) 0.408 ms 0.523 ms 0.585 ms 3 rtr-inet2.ox.com (129.77.1.252) 3.394 ms 3.437 ms 3.464 ms 4 129.77.3.254 (129.77.3.254) 0.515 ms 0.517 ms 0.541 ms 5 189d20f9.cst.lightpath.net (24.157.32.249) 4.909 ms 4.923 ms 4.922 ms 6 18267502.cst.lightpath.net (24.38.117.2) 7.318 ms 9.900 ms 9.889 ms 7 (69.74.203.201) 9.877 ms 9.444 ms 9.434 ms 8 * * * 9 adsl-065-015-003-181.sip.mia.bellsouth.net (65.15.3.181) 9.455 ms * * 10 * * * 11 xe-9-1-2.edge2.Newark1.Level3.net (4.31.45.173) 8.378 ms 14.395 ms 14.244 ms 12 ae-32-52.ebr2.Newark1.Level3.net (4.69.156.62) 39.992 ms 42.318 ms 42.303 ms 13 ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101) 42.283 ms 42.284 ms 42.280 ms 14 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 50.599 ms 50.594 ms 50.586 ms 15 ae-61-61.ebr1.washington1.level3.net (4.69.134.129) 40.769 ms 43.276 ms * 16 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 43.293 ms 39.230 ms 38.957 ms 17 ae-73-73.ebr2.Atlanta2.Level3.net (4.69.148.254) 38.942 ms 38.942 ms 38.501 ms 18 ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 39.404 ms 37.772 ms 37.487 ms 19 ae-2-52.edge1.Miami2.Level3.net (4.69.138.107) 50.685 ms 50.674 ms 50.568 ms 20 telefonica.edge1.miami2.level3.net (4.71.212.118) 62.446 ms 60.038 ms 59.416 ms 21 176.52.251.189 (176.52.251.189) 57.850 ms 58.637 ms 58.541 ms 22 176.52.252.66 (176.52.252.66) 94.381 ms 97.548 ms 99.258 ms 23 * * * 24 * * * 25 * * * 26 host-186-5-116-193.telconet.net (186.5.116.193) 118.811 ms 118.803 ms 118.808 ms 27 host-186-101-89-42.telconet.net (186.101.89.42) 98.612 ms 98.589 ms 98.605 ms 28 200.10.150.169 (200.10.150.169) 98.534 ms 98.564 ms 98.505 ms root@newton dig +short www.floksociety.org. 200.10.150.169 root@newton telnet 200.10.150.169 80 Trying 200.10.150.169... Connected to 200.10.150.169. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.1 503 Service Unavailable Server: Varnish Content-Type: text/html; charset=utf-8 Retry-After: 5 Content-Length: 418 Accept-Ranges: bytes Date: Fri, 04 Oct 2013 16:12:33 GMT Connection: close ?xml version=1.0 encoding=utf-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html head title503 Service Unavailable/title /head body h1Error 503 Service Unavailable/h1 pService Unavailable/p h3Guru Meditation:/h3 pXID: 477990820/p hr pVarnish cache server/p /body /html Connection to 200.10.150.169 closed by foreign host. -Original Message- From: Gordon Cook [mailto:c...@cookreport.com] Sent: Friday, October 04, 2013 12:10 PM To: nanog@nanog.org list Subject: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Dear NANOG The Ecuadoran government has via the FLOK society hired Michel Bauwens of the P2p foundation to lead a two year long efforts to revision the ecudoran economy along the lines of a commons oriented collaborative society. I am very interested in the program yet i have NEVER been able to connect to their web site. At the end of two hours of trouble shooting with apple i was advised to call verizon. I am a FiOS customer on a two year contact. The traceroute below confirmed that the fault is in verizons network. The verizon tech agreed otherwise i never would have gotten the trouble ticket my verizon trouble ticket is NJ DQ04PWR9. Can someone tell me what number to call to pursue resolution of this trouble ticket? as of 12:04 eastern time i still cannot connect 24 hours was the promise 14 of the 24 have elapsed 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 Traceroute has started... traceroute to 200.10.150.169 (200.10.150.169), 64 hops max, 72 byte packets 1 192.168.1.1 (192.168.1.1) 0.622 ms 0.305 ms 0.361 ms 2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 6.633 ms
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Site appears up and available, over Comcast Business fiber and Cogent from Chicago (using Chrome 28). On Fri, Oct 4, 2013 at 11:17 AM, Matthew Huff mh...@ox.com wrote: My traceroute goes through, but we don't go through Verizon. However, the web server is returning an error that it is unavailable. It's possible that the destination web server has a geo location plug in that stops access from foreign locations, or that their server is down. [root@lancaster ~]# traceroute -I 200.10.150.169 traceroute to 200.10.150.169 (200.10.150.169), 30 hops max, 40 byte packets 1 129.77.108.252 (129.77.108.252) 0.345 ms 0.384 ms 0.442 ms 2 switch-user1.ox.com (129.77.154.253) 0.408 ms 0.523 ms 0.585 ms 3 rtr-inet2.ox.com (129.77.1.252) 3.394 ms 3.437 ms 3.464 ms 4 129.77.3.254 (129.77.3.254) 0.515 ms 0.517 ms 0.541 ms 5 189d20f9.cst.lightpath.net (24.157.32.249) 4.909 ms 4.923 ms 4.922 ms 6 18267502.cst.lightpath.net (24.38.117.2) 7.318 ms 9.900 ms 9.889 ms 7 (69.74.203.201) 9.877 ms 9.444 ms 9.434 ms 8 * * * 9 adsl-065-015-003-181.sip.mia.bellsouth.net (65.15.3.181) 9.455 ms * * 10 * * * 11 xe-9-1-2.edge2.Newark1.Level3.net (4.31.45.173) 8.378 ms 14.395 ms 14.244 ms 12 ae-32-52.ebr2.Newark1.Level3.net (4.69.156.62) 39.992 ms 42.318 ms 42.303 ms 13 ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101) 42.283 ms 42.284 ms 42.280 ms 14 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 50.599 ms 50.594 ms 50.586 ms 15 ae-61-61.ebr1.washington1.level3.net (4.69.134.129) 40.769 ms 43.276 ms * 16 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 43.293 ms 39.230 ms 38.957 ms 17 ae-73-73.ebr2.Atlanta2.Level3.net (4.69.148.254) 38.942 ms 38.942 ms 38.501 ms 18 ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 39.404 ms 37.772 ms 37.487 ms 19 ae-2-52.edge1.Miami2.Level3.net (4.69.138.107) 50.685 ms 50.674 ms 50.568 ms 20 telefonica.edge1.miami2.level3.net (4.71.212.118) 62.446 ms 60.038 ms 59.416 ms 21 176.52.251.189 (176.52.251.189) 57.850 ms 58.637 ms 58.541 ms 22 176.52.252.66 (176.52.252.66) 94.381 ms 97.548 ms 99.258 ms 23 * * * 24 * * * 25 * * * 26 host-186-5-116-193.telconet.net (186.5.116.193) 118.811 ms 118.803 ms 118.808 ms 27 host-186-101-89-42.telconet.net (186.101.89.42) 98.612 ms 98.589 ms 98.605 ms 28 200.10.150.169 (200.10.150.169) 98.534 ms 98.564 ms 98.505 ms root@newton dig +short www.floksociety.org. 200.10.150.169 root@newton telnet 200.10.150.169 80 Trying 200.10.150.169... Connected to 200.10.150.169. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.1 503 Service Unavailable Server: Varnish Content-Type: text/html; charset=utf-8 Retry-After: 5 Content-Length: 418 Accept-Ranges: bytes Date: Fri, 04 Oct 2013 16:12:33 GMT Connection: close ?xml version=1.0 encoding=utf-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html head title503 Service Unavailable/title /head body h1Error 503 Service Unavailable/h1 pService Unavailable/p h3Guru Meditation:/h3 pXID: 477990820/p hr pVarnish cache server/p /body /html Connection to 200.10.150.169 closed by foreign host. -Original Message- From: Gordon Cook [mailto:c...@cookreport.com] Sent: Friday, October 04, 2013 12:10 PM To: nanog@nanog.org list Subject: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Dear NANOG The Ecuadoran government has via the FLOK society hired Michel Bauwens of the P2p foundation to lead a two year long efforts to revision the ecudoran economy along the lines of a commons oriented collaborative society. I am very interested in the program yet i have NEVER been able to connect to their web site. At the end of two hours of trouble shooting with apple i was advised to call verizon. I am a FiOS customer on a two year contact. The traceroute below confirmed that the fault is in verizons network. The verizon tech agreed otherwise i never would have gotten the trouble ticket my verizon trouble ticket is NJ DQ04PWR9. Can someone tell me what number to call to pursue resolution of this trouble ticket? as of 12:04 eastern time i still cannot connect 24 hours was the promise 14 of the 24 have elapsed 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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, Oct 4, 2013 at 12:09 PM, Gordon Cook c...@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 -- William D. Herrin her...@dirtside.com b...@herrin.us 3005 Crane Dr. .. Web: http://bill.herrin.us/ Falls Church, VA 22042-3004
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
200.10.150.169 is reachable from AS2828 and from AS20115, but not from AS22394 (Verizon Wireless) On Fri, Oct 4, 2013 at 12:28 PM, Brandon Galbraith brandon.galbra...@gmail.com wrote: Site appears up and available, over Comcast Business fiber and Cogent from Chicago (using Chrome 28). On Fri, Oct 4, 2013 at 11:17 AM, Matthew Huff mh...@ox.com wrote: My traceroute goes through, but we don't go through Verizon. However, the web server is returning an error that it is unavailable. It's possible that the destination web server has a geo location plug in that stops access from foreign locations, or that their server is down. [root@lancaster ~]# traceroute -I 200.10.150.169 traceroute to 200.10.150.169 (200.10.150.169), 30 hops max, 40 byte packets 1 129.77.108.252 (129.77.108.252) 0.345 ms 0.384 ms 0.442 ms 2 switch-user1.ox.com (129.77.154.253) 0.408 ms 0.523 ms 0.585 ms 3 rtr-inet2.ox.com (129.77.1.252) 3.394 ms 3.437 ms 3.464 ms 4 129.77.3.254 (129.77.3.254) 0.515 ms 0.517 ms 0.541 ms 5 189d20f9.cst.lightpath.net (24.157.32.249) 4.909 ms 4.923 ms 4.922 ms 6 18267502.cst.lightpath.net (24.38.117.2) 7.318 ms 9.900 ms 9.889 ms 7 (69.74.203.201) 9.877 ms 9.444 ms 9.434 ms 8 * * * 9 adsl-065-015-003-181.sip.mia.bellsouth.net (65.15.3.181) 9.455 ms * * 10 * * * 11 xe-9-1-2.edge2.Newark1.Level3.net (4.31.45.173) 8.378 ms 14.395 ms 14.244 ms 12 ae-32-52.ebr2.Newark1.Level3.net (4.69.156.62) 39.992 ms 42.318 ms 42.303 ms 13 ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101) 42.283 ms 42.284 ms 42.280 ms 14 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 50.599 ms 50.594 ms 50.586 ms 15 ae-61-61.ebr1.washington1.level3.net (4.69.134.129) 40.769 ms 43.276 ms * 16 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 43.293 ms 39.230 ms 38.957 ms 17 ae-73-73.ebr2.Atlanta2.Level3.net (4.69.148.254) 38.942 ms 38.942 ms 38.501 ms 18 ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 39.404 ms 37.772 ms 37.487 ms 19 ae-2-52.edge1.Miami2.Level3.net (4.69.138.107) 50.685 ms 50.674 ms 50.568 ms 20 telefonica.edge1.miami2.level3.net (4.71.212.118) 62.446 ms 60.038 ms 59.416 ms 21 176.52.251.189 (176.52.251.189) 57.850 ms 58.637 ms 58.541 ms 22 176.52.252.66 (176.52.252.66) 94.381 ms 97.548 ms 99.258 ms 23 * * * 24 * * * 25 * * * 26 host-186-5-116-193.telconet.net (186.5.116.193) 118.811 ms 118.803 ms 118.808 ms 27 host-186-101-89-42.telconet.net (186.101.89.42) 98.612 ms 98.589 ms 98.605 ms 28 200.10.150.169 (200.10.150.169) 98.534 ms 98.564 ms 98.505 ms root@newton dig +short www.floksociety.org. 200.10.150.169 root@newton telnet 200.10.150.169 80 Trying 200.10.150.169... Connected to 200.10.150.169. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.1 503 Service Unavailable Server: Varnish Content-Type: text/html; charset=utf-8 Retry-After: 5 Content-Length: 418 Accept-Ranges: bytes Date: Fri, 04 Oct 2013 16:12:33 GMT Connection: close ?xml version=1.0 encoding=utf-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html head title503 Service Unavailable/title /head body h1Error 503 Service Unavailable/h1 pService Unavailable/p h3Guru Meditation:/h3 pXID: 477990820/p hr pVarnish cache server/p /body /html Connection to 200.10.150.169 closed by foreign host. -Original Message- From: Gordon Cook [mailto:c...@cookreport.com] Sent: Friday, October 04, 2013 12:10 PM To: nanog@nanog.org list Subject: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Dear NANOG The Ecuadoran government has via the FLOK society hired Michel Bauwens of the P2p foundation to lead a two year long efforts to revision the ecudoran economy along the lines of a commons oriented collaborative society. I am very interested in the program yet i have NEVER been able to connect to their web site. At the end of two hours of trouble shooting with apple i was advised to call verizon. I am a FiOS customer on a two year contact. The traceroute below confirmed that the fault is in verizons network. The verizon tech agreed otherwise i never would have gotten the trouble ticket my verizon trouble ticket is NJ DQ04PWR9. Can someone tell me what number to call to pursue resolution of this trouble ticket? as of 12:04 eastern time i still cannot connect 24 hours was the promise 14 of the 24 have elapsed 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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Thank you Bill extremely helpful if via FiOS from DC you cannot get through does his look like an intentional move by verizobn to black hole this site how to determine that? would like to be sure before i start raising hell elsewhere I have tried to connect all week long never once succeeded. advise?? any verizon people here willing to help? = The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: http://www.cookreport.com/index.php?option=com_docmantask=cat_viewgid=37Itemid=61 Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_contentview=articleid=54Itemid=65 = On Oct 4, 2013, at 12:30 PM, William Herrin b...@herrin.us wrote: On Fri, Oct 4, 2013 at 12:09 PM, Gordon Cook c...@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 -- William D. Herrin her...@dirtside.com b...@herrin.us 3005 Crane Dr. .. Web: http://bill.herrin.us/ Falls Church, VA 22042-3004
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
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 c...@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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
My mistake - cell network is also blocked. Stupid autocorrect changed floksociety to folksociety. Sigh Other info is correct. Miles Fidelman 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 c...@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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
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 mfidel...@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 c...@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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
esceula seems to announce a slew of /24's... 28027 | 200.10.149.0/24 | Escuela Superior Politecnica del Litoral 28027 | 200.10.150.0/24 | Escuela Superior Politecnica del Litoral 28027 | 200.10.151.0/24 | Escuela Superior Politecnica del Litoral but not the covering /22: 200.10.148/22 looking at routeviews (who has a 701 peer): route-viewssho ip bgp summ | in 157.130 157.130.10.233 4701 12266262 1198223 96890482000 3w2d 458803 route-views route-viewssho ip bgp neighbors 157.130.10.233 paths | in 28027 0x511FB188 11 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i 0x47A5A4C02 0 701 3257 3257 19169 27947 28027 i seems that not all of 28027's routes are heard by 701... route-viewssho ip bgp neighbors 157.130.10.233 routes | in 28027 * 190.15.129.0/24 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 192.188.59.0 157.130.10.233 0 701 3257 3257 19169 27947 28027 i * 200.9.176.0 157.130.10.233 0 701 3257 3257 19169 27947 28027 i * 200.126.0.0/20 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.16.0/22 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.20.0/23 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.22.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.23.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.24.0/22 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.28.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.29.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.30.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i * 200.126.31.0 157.130.10.233 0 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 i route-views this doesn't include the 200.10.148.0/22 networks at all though. I'd look suspiciously at: aut-num:as12956 as-name:Telefonica descr: Telefonica Backbone Autonomous System descr: Telefonica Wholesale Network remarks:=== remarks:http://www.telefonica-wholesale.com remarks:= who seems to be prepending like crazy... On Fri, Oct 4, 2013 at 12:54 PM, Christopher Morrow morrowc.li...@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 mfidel...@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 c...@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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Hi chris really appreciate the help from ALL you guys 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?? = The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: http://www.cookreport.com/index.php?option=com_docmantask=cat_viewgid=37Itemid=61 Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_contentview=articleid=54Itemid=65 = On Oct 4, 2013, at 12:54 PM, Christopher Morrow morrowc.li...@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 mfidel...@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 c...@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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, Oct 4, 2013 at 12:40 PM, Gordon Cook c...@cookreport.com wrote: if via FiOS from DC you cannot get through does his look like an intentional move by verizobn to black hole this site how to determine that? would like to be sure before i start raising hell elsewhere I would expect that they're just not receiving the BGP advertisement for 200.10.150.0/24 from telefonica-wholesale.net. No way to know from the endpoints whether that's because Telefonica isn't sending or because Verizon is rejecting. Either way, it doesn't seem to be black holed. Black holed is when you advertise a route to a destination and then dump the packets. Regards, Bill Herrin -- William D. Herrin her...@dirtside.com b...@herrin.us 3005 Crane Dr. .. Web: http://bill.herrin.us/ Falls Church, VA 22042-3004
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, Oct 4, 2013 at 1:15 PM, Gordon Cook c...@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.li...@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 mfidel...@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 c...@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)
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Working here on Bresnan (charter) root@hq:~# traceroute floksociety.org traceroute to floksociety.org (200.10.150.169), 30 hops max, 60 byte packets 1 * * * 2 cacco002dr9-GE-1-0-0-U0.int.bresnan.net (69.146.239.57) 38.721 ms 39.799 ms 39.899 m s 3 host-72-175-111-198.bln-mt.client.bresnan.net (72.175.111.198) 26.722 ms 27.671 ms 2 7.771 ms 4 chywyaT1cr5-XE-5-2-0-U0.int.bresnan.net (72.175.110.135) 27.791 ms 27.818 ms 27.820ms 5 seawafh2cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.166) 67.666 ms 68.616 ms 68.641ms 6 seawafh1tr5-XE-2-0-0-U0.int.bresnan.net (72.175.110.68) 51.856 ms 61.108 ms 61.768 m s 7 12.90.77.21 (12.90.77.21) 65.384 ms 66.327 ms 66.448 ms 8 cr2.st6wa.ip.att.net (12.123.46.130) 122.440 ms 112.765 ms 111.808 ms 9 cr2.dvmco.ip.att.net (12.122.1.77) 111.733 ms 102.272 ms 98.744 ms 10 cr2.dlstx.ip.att.net (12.122.31.89) 105.493 ms 106.421 ms 105.106 ms 11 dlstx02jt.ip.att.net (12.122.214.249) 104.780 ms 101.914 ms 106.405 ms 12 213.140.53.61 (213.140.53.61) 103.208 ms 192.205.35.250 (192.205.35.250) 100.279 ms 2 13.140.53.61 (213.140.53.61) 121.303 ms 13 Te0-5-0-6-grtmiabr5.red.telefonica-wholesale.net (94.142.125.58) 144.127 ms Xe8-0-2-0- grtmiabr4.red.telefonica-wholesale.net(94.142.119.38) 159.790 ms Xe3-1-2-0-grtmiabr4.red. telefonica-wholesale.net (94.142.126.134) 139.640 ms 14 Te0-2-0-4-grtmiana4.red.telefonica-wholesale.net (94.142.123.5) 138.665 ms Te0-1-0-0-g rtmiana4.red.telefonica-wholesale.net(213.140.37.77) 139.681 ms Xe7-1-6-0-grtmiana2.red.t elefonica-wholesale.net (94.142.125.154) 145.648 ms 15 176.52.249.245 (176.52.249.245) 163.222 ms 176.52.251.201 (176.52.251.201) 143.164 ms176.52.249.241 (176.52.249.241) 140.896 ms 16 176.52.252.66 (176.52.252.66) 184.038 ms 188.723 ms 181.953 ms 17 * * * 18 * * * 19 * * * 20 host-186-5-116-193.telconet.net (186.5.116.193) 189.490 ms 188.537 ms 188.500 ms 21 host-186-101-89-42.telconet.net (186.101.89.42) 190.366 ms 188.294 ms 192.845 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Traceroute black holes but the site works. Site works on VZW in Colorado. Cheers On Fri, Oct 4, 2013 at 11:22 AM, Christopher Morrow morrowc.li...@gmail.com wrote: On Fri, Oct 4, 2013 at 1:15 PM, Gordon Cook c...@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.li...@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 mfidel...@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 c...@cookreport.com wrote: traceroute to
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, Oct 4, 2013 at 1:35 PM, Bryan Tong cont...@nullivex.com wrote: Site works on VZW in Colorado. vzw gets transit from places OTHER than 701 in a bunch of places...
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
http://www.downforeveryoneorjustme.com/floksociety.org says it's up. My VZ dsl says no. On Fri, Oct 4, 2013 at 1:38 PM, Christopher Morrow morrowc.li...@gmail.comwrote: On Fri, Oct 4, 2013 at 1:35 PM, Bryan Tong cont...@nullivex.com wrote: Site works on VZW in Colorado. vzw gets transit from places OTHER than 701 in a bunch of places... -- --- Joly MacFie 218 565 9365 Skype:punkcast WWWhatsup NYC - http://wwwhatsup.com http://pinstand.com - http://punkcast.com VP (Admin) - ISOC-NY - http://isoc-ny.org -- -
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, 4 Oct 2013, Joly MacFie wrote: http://www.downforeveryoneorjustme.com/floksociety.org says it's up. My VZ dsl says no. I'm guessing either VZ is not carrying a default inside their network, or they are propagating whatever blackhole might exist. From my FIOS connection at home, I never reach anything that looks like a router that I would expect to have a complete view of the Internet routing table. streiner@whammy ~ $ traceroute www.floksociety.org traceroute to www.floksociety.org (200.10.150.169), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.815 ms 0.800 ms 0.789 ms 2 L300.PITBPA-VFTTP-29.verizon-gni.net (173.75.39.1) 4.095 ms 4.094 ms 4.720 ms 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * G0-6-0-6.PITBPA-LCR-22.verizon-gni.net (130.81.168.90) 11.303 ms !N
Weekly Routing Table Report
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-st...@lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith pfsi...@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: 26 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 Blocks4608-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
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
The below information is taken from an internal router directly connected to 701 == CORE-R1#show ip bgp 200.10.150.169 BGP routing table entry for 200.10.150.0/24, version 46722748 Paths: (1 available, best #1, table default) Not advertised to any peer 701 12956 12956 12956 12956 12956 12956 12956 19169 27947 28027 x.x.x.x from x.x.x.x (y.y.y.y) Origin IGP, localpref 100, valid, external, best Tracing the route to 200.10.150.169 VRF info: (vrf in name/id, vrf out name/id) 1 .. 2 0.ge-11-1-0.XT4.TOR2.ALTER.NET (152.63.4.250) [AS 701] 0 msec 0 msec 0 msec 3 0.xe-9-1-0.XL2.IAD8.ALTER.NET (152.63.35.14) [AS 701] 20 msec 20 msec 20 msec 4 0.xe-9-2-0.GW9.IAD8.ALTER.NET (152.63.36.30) [AS 701] 20 msec 0.xe-9-0-0.GW9.IAD8.ALTER.NET (152.63.36.18) [AS 701] 20 msec 0.xe-11-0-0.GW9.IAD8.ALTER.NET (152.63.33.165) [AS 701] 20 msec 5 telefonica-gw.customer.alter.net (152.179.50.114) [AS 701] 20 msec 20 msec 20 msec 6 Te0-7-0-5-grtmiana4.red.telefonica-wholesale.net (94.142.126.182) [AS 12956] 60 msec Xe4-1-6-0-grtmiana2.red.telefonica-wholesale.net (94.142.123.145) [AS 12956] 64 msec 60 msec 7 176.52.249.245 60 msec 176.52.251.193 64 msec Xe8-3-0-0-gramiana4.red.telefonica-wholesale.net (94.142.126.185) [AS 12956] 60 msec 8 176.52.252.66 104 msec 104 msec 104 msec 9 * * * 10 * * * 11 * * * 12 host-186-5-116-193.telconet.net (186.5.116.193) [AS 27947] [MPLS: Label 5539 Exp 0] 104 msec 104 msec 104 msec 13 host-186-101-89-42.telconet.net (186.101.89.42) [AS 27947] 108 msec 104 msec 108 msec 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * On Fri, Oct 4, 2013 at 12:09 PM, Gordon Cook c...@cookreport.com wrote: Dear NANOG The Ecuadoran government has via the FLOK society hired Michel Bauwens of the P2p foundation to lead a two year long efforts to revision the ecudoran economy along the lines of a commons oriented collaborative society. I am very interested in the program yet i have NEVER been able to connect to their web site. At the end of two hours of trouble shooting with apple i was advised to call verizon. I am a FiOS customer on a two year contact. The traceroute below confirmed that the fault is in verizons network. The verizon tech agreed otherwise i never would have gotten the trouble ticket my verizon trouble ticket is NJ DQ04PWR9. Can someone tell me what number to call to pursue resolution of this trouble ticket? as of 12:04 eastern time i still cannot connect 24 hours was the promise 14 of the 24 have elapsed 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 Traceroute has started… traceroute to 200.10.150.169 (200.10.150.169), 64 hops max, 72 byte packets 1 192.168.1.1 (192.168.1.1) 0.622 ms 0.305 ms 0.361 ms 2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 6.633 ms 4.892 ms 4.809 ms 3 * * * 4 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 10.441 ms !N * * 5 * * * 6 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 9.932 ms !N * * 7 * * * 8 * * * 9 * * * 10 * * * 11 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 9.765 ms !N * * 12 * * * 13 * * *= Lookup has started… Trying floksociety.org ;; -HEADER- opcode: QUERY, status: NOERROR, id: 13700 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;floksociety.org. INANY ;; ANSWER SECTION: floksociety.org. 600 INA 200.10.150.169 floksociety.org. 3600INMX 10 mail.floksociety.org. floksociety.org. 3600INNS ns57.domaincontrol.com. floksociety.org. 3600INNS ns58.domaincontrol.com. floksociety.org. 3600INSOAns57.domaincontrol.com. dns.jomax.net. 2013092400 28800 7200 604800 600 Received 174 bytes from 8.8.8.8#53 in 139 ms = The COOK Report on Internet Protocol, (PSTN) 609 882-2572 Back Issues: http://www.cookreport.com/index.php?option=com_docmantask=cat_viewgid=37Itemid=61 Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info:
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
On Fri, Oct 04, 2013 at 12:30:01PM -0400, William Herrin wrote: 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 * * A little earlier, both FiOS and a uunet/701 connection yielded '!N', but as of this writing both paths are reaching that website. -- Henry Yen henry@aegis00.com Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York (800) AEGIS-00 x949 1-800-AEGIS-00 (800-234-4700)
Level3 - AS3549 US IPv6 Routing
I have noticed for the last couple of weeks that Level3 is routing IPV6
traffic to Global Crossing AS via Seattle. Seeing it from multiple
connection's we have in the US plus Level3 Looking Glass also shows the
routes learned in Seattle from DC. I can't see them only peering in
Seattle from US location's, Europe is different seems to be routing
correctly from what I see on the looking glass.
Route results for 2001:450::/32 from Washington, DC
BGP routing table entry for 2001:450::/32
Paths: (2 available, best #1)
3549, (aggregated by 3549 err41.sea1.gblx.mgmt)
AS-path translation: { GBLX }
2001:1900::3:91 (metric 7502)
Origin IGP, localpref 100, valid, internal, atomic-aggregate, best
Community: 3549:5001 3549:30840
Originator: edge1.Seattle3
3549, (aggregated by 3549 err41.sea1.gblx.mgmt)
AS-path translation: { GBLX }
2001:1900::3:91 (metric 7502)
Origin IGP, localpref 100, valid, internal, atomic-aggregate
Community: 3549:5001 3549:30840
Originator: edge1.Seattle3
Route results for 2001:450::/32 from Frankfurt, Germany
BGP routing table entry for 2001:450::/32
Paths: (2 available, best #1)
3549, (aggregated by 3549 err41.fra4.gblx.mgmt)
AS-path translation: { GBLX }
2001:1900:2::3:8 (metric 40)
Origin IGP, metric 10, localpref 86, valid, internal,
atomic-aggregate, best
Community: Europe Lclprf_86 Germany IPv6-valid Level3_Peer
Community_ERROR Frankfurt
Originator: edge4.Frankfurt1
3549, (aggregated by 3549 err41.fra4.gblx.mgmt)
AS-path translation: { GBLX }
2001:1900:2::3:8 (metric 40)
Origin IGP, metric 10, localpref 86, valid, internal,
atomic-aggregate
Community: Europe Lclprf_86 Germany IPv6-valid Level3_Peer
Community_ERROR Frankfurt
Originator: edge4.Frankfurt1
Traceroute from one of my connections in DC. Doesn't matter what I source
the route from. I have also seen this to customers behind AS3549 too.
4. vl-4081.edge2.washington1.level3 0.0% 71.6 1.6 1.6 1.6
0.0
5. vl-4061.car1.newyork2.level3.net 0.0% 76.9 7.5 6.9 10.6
1.4
6. vl-4081.car2.newyork2.level3.net 0.0% 77.0 41.0 7.0 158.2
61.0
7. vl-4061.car1.chicago1.level3.net 0.0% 7 27.7 27.5 27.4 27.7
0.1
8. vl-4040.edge1.chicago2.level3.ne 0.0% 7 27.7 30.0 27.6 44.3
6.3
9. vl-4042.edge6.denver1.level3.net 0.0% 7 51.9 51.9 51.8 52.0
0.1
10. vl-4060.car2.seattle1.level3.net 0.0% 6 186.2 119.0 78.5 186.2
51.6
11. 2001:1900:1b:1::9 0.0% 6 78.4 78.4 78.3 78.6
0.1
12. 2001:450:2008:100::1350.0% 6 86.4 87.2 86.4 90.0
1.4
13. 2001:450:2002:288::2 0.0% 6 85.2 85.3 85.1 85.5
0.1
If I route this traffic via Telia it goes direct to Global Crossing's with
a much lower latency. Has anyone else seen this issue with Level3?
Thanks,
Adam
It worked! Huge Thanks Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
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_docmantask=cat_viewgid=37Itemid=61 Cook's Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_contentview=articleid=54Itemid=65 = On Oct 4, 2013, at 3:50 PM, Moore, Matthew S mscott.mo...@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.mor...@gmail.com [mailto:christopher.mor...@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.li...@gmail.com wrote: On Fri, Oct 4, 2013 at 2:54 PM, Sieg, Eric W eric.s...@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@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@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.mor...@gmail.com [mailto:christopher.mor...@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 c...@cookreport.com wrote: again thank you very very much. I have to leave
web site bug report
as i get bounces from act...@nanog.org and all other similar contacts, here we go https://www.nanog.org/archives/presentations?k=0s=Douglas%20Maughanm=0a=search gives me clickables to the 56 agenda. but those clickables lead me to https://www.nanog.org/meetings/56/agenda which gives me Page not found The requested page /meetings/56/agenda could not be found. sigh randhy
Re: web site bug report
Hi Randy: We look into the situation now.. Very sorry for the error. All best. Betty On Fri, Oct 4, 2013 at 5:48 PM, Randy Bush ra...@psg.com wrote: as i get bounces from act...@nanog.org and all other similar contacts, here we go https://www.nanog.org/archives/presentations?k=0s=Douglas%20Maughanm=0a=search gives me clickables to the 56 agenda. but those clickables lead me to https://www.nanog.org/meetings/56/agenda which gives me Page not found The requested page /meetings/56/agenda could not be found. sigh randhy -- Betty Burke NANOG Executive Director 48377 Fremont Boulevard, Suite 117 Fremont, CA 94538 Tel: +1 510 492 4030
Re: web site bug report
We look into the situation now.. Very sorry for the error. i demand a full refund! :)
The Cidr Report
This report has been generated at Fri Oct 4 21:13:31 2013 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org for a current version of this report.
Recent Table History
Date PrefixesCIDR Agg
27-09-13480420 271008
28-09-13480526 271503
29-09-13480781 271509
30-09-13480357 271325
01-10-13479734 271628
02-10-13480438 271524
03-10-13480524 271615
04-10-13479970 272934
AS Summary
45275 Number of ASes in routing system
18585 Number of ASes announcing only one prefix
4174 Largest number of prefixes announced by an AS
AS7029 : WINDSTREAM - Windstream Communications Inc
118190016 Largest address span announced by an AS (/32s)
AS4134 : CHINANET-BACKBONE No.31,Jin-rong Street
Aggregation Summary
The algorithm used in this report proposes aggregation only
when there is a precise match using the AS path, so as
to preserve traffic transit policies. Aggregation is also
proposed across non-advertised address space ('holes').
--- 04Oct13 ---
ASnumNetsNow NetsAggr NetGain % Gain Description
Table 480818 273005 20781343.2% All ASes
AS6389 3060 62 299898.0% BELLSOUTH-NET-BLK -
BellSouth.net Inc.
AS17974 2697 120 257795.6% TELKOMNET-AS2-AP PT
Telekomunikasi Indonesia
AS28573 3361 867 249474.2% NET Serviços de Comunicação
S.A.
AS7029 4174 1867 230755.3% WINDSTREAM - Windstream
Communications Inc
AS4766 2945 954 199167.6% KIXS-AS-KR Korea Telecom
AS10620 2598 1030 156860.4% Telmex Colombia S.A.
AS18566 2066 572 149472.3% COVAD - Covad Communications
Co.
AS36998 1864 375 148979.9% SDN-MOBITEL
AS4323 2961 1538 142348.1% TWTC - tw telecom holdings,
inc.
AS7303 1724 466 125873.0% Telecom Argentina S.A.
AS1785 2019 810 120959.9% AS-PAETEC-NET - PaeTec
Communications, Inc.
AS4755 1769 585 118466.9% TATACOMM-AS TATA
Communications formerly VSNL
is Leading ISP
AS7552 1195 145 105087.9% VIETEL-AS-AP Vietel
Corporation
AS18881 1463 438 102570.1% Global Village Telecom
AS22561 1237 216 102182.5% DIGITAL-TELEPORT - Digital
Teleport Inc.
AS7545 2085 1222 86341.4% TPG-INTERNET-AP TPG Telecom
Limited
AS22773 2058 1241 81739.7% ASN-CXA-ALL-CCI-22773-RDC -
Cox Communications Inc.
AS18101 979 178 80181.8% RELIANCE-COMMUNICATIONS-IN
Reliance Communications
Ltd.DAKC MUMBAI
AS4808 1191 403 78866.2% CHINA169-BJ CNCGROUP IP
network China169 Beijing
Province Network
AS8402 1816 1040 77642.7% CORBINA-AS OJSC Vimpelcom
AS11830 866 118 74886.4% Instituto Costarricense de
Electricidad y Telecom.
AS701 1517 793 72447.7% UUNET - MCI Communications
Services, Inc. d/b/a Verizon
Business
AS24560 1091 373 71865.8% AIRTELBROADBAND-AS-AP Bharti
Airtel Ltd., Telemedia
Services
AS8151 1345 633 71252.9% Uninet S.A. de C.V.
AS6983 1294 585 70954.8% ITCDELTA - ITC^Deltacom
AS13977 851 146 70582.8% CTELCO - FAIRPOINT
COMMUNICATIONS, INC.
AS6147 799 108 69186.5% Telefonica del Peru S.A.A.
AS855737 55 68292.5% CANET-ASN-4 - Bell Aliant
Regional Communications, Inc.
AS7738 780 138 64282.3% Telemar Norte Leste S.A.
AS17676
BGP Update Report
BGP Update Report Interval: 26-Sep-13 -to- 03-Oct-13 (7 days) Observation Point: BGP Peering with AS131072 TOP 20 Unstable Origin AS Rank ASNUpds % Upds/PfxAS-Name 1 - AS18881 69543 2.7% 47.6 -- Global Village Telecom 2 - AS816368857 2.7% 177.5 -- METROTEL REDES S.A. 3 - AS36998 47541 1.9% 25.5 -- SDN-MOBITEL 4 - AS453847379 1.9% 18.9 -- ERX-CERNET-BKB China Education and Research Network Center 5 - AS840245065 1.8% 22.5 -- CORBINA-AS OJSC Vimpelcom 6 - AS982938289 1.5% 36.0 -- BSNL-NIB National Internet Backbone 7 - AS10620 29732 1.2% 14.5 -- Telmex Colombia S.A. 8 - AS381628564 1.1% 47.4 -- COLOMBIA TELECOMUNICACIONES S.A. ESP 9 - AS28573 23905 0.9% 8.1 -- NET Serviços de Comunicação S.A. 10 - AS13118 22526 0.9% 479.3 -- ASN-YARTELECOM OJSC Rostelecom 11 - AS31148 22155 0.9% 22.4 -- FREENET-AS Freenet Ltd. 12 - AS27738 18931 0.7% 32.8 -- Ecuadortelecom S.A. 13 - AS19886 17274 0.7%2879.0 -- BOFABROKERDEALERSVCS - Bank of America 14 - AS20473 16646 0.7% 110.2 -- AS-CHOOPA - Choopa, LLC 15 - AS815116096 0.6% 14.1 -- Uninet S.A. de C.V. 16 - AS477515943 0.6% 613.2 -- GLOBE-TELECOM-AS Globe Telecoms 17 - AS28509 15244 0.6% 73.6 -- Cablemas Telecomunicaciones SA de CV 18 - AS31252 13271 0.5% 53.9 -- STARNET-AS StarNet Moldova 19 - AS17974 11386 0.5% 4.9 -- TELKOMNET-AS2-AP PT Telekomunikasi Indonesia 20 - AS11976 11291 0.4% 171.1 -- FIDN - Fidelity Communication International Inc. TOP 20 Unstable Origin AS (Updates per announced prefix) Rank ASNUpds % Upds/PfxAS-Name 1 - AS6629 8937 0.3%8937.0 -- NOAA-AS - NOAA 2 - AS6174 7057 0.3%3528.5 -- SPRINTLINK8 - Sprint 3 - AS324453006 0.1%3006.0 -- XHOP - XHOP LLC 4 - AS373672990 0.1%2990.0 -- CALLKEY 5 - AS19886 17274 0.7%2879.0 -- BOFABROKERDEALERSVCS - Bank of America 6 - AS166085186 0.2%2593.0 -- KENTEC - Kentec Communications, Inc. 7 - AS7202 8508 0.3%1701.6 -- FAMU - Florida A M University 8 - AS197792629 0.1%1314.5 -- 9 - AS335401071 0.0%1071.0 -- ALZHEI-ASN - Alzheimers Assoc. 10 - AS458081066 0.0%1066.0 -- UTP-MY Bandar Seri Iskandar 11 - AS22688 989 0.0% 989.0 -- DOLGENCORP - Dollar General Corporation 12 - AS23295 735 0.0% 735.0 -- EA-01 - Extend America 13 - AS325285861 0.2% 732.6 -- ABBOTT Abbot Labs 14 - AS486129554 0.4% 682.4 -- RTC-ORENBURG-AS CJSC Comstar-Regions 15 - AS477515943 0.6% 613.2 -- GLOBE-TELECOM-AS Globe Telecoms 16 - AS322447321 0.3% 610.1 -- LIQUID-WEB-INC - Liquid Web, Inc. 17 - AS584521194 0.1% 597.0 -- ANTAMEDIAKOM-ID PT. Anta Mediakom 18 - AS22124 0.1% 657.0 -- CONTROLVM-MY ControlVM Technology 19 - AS558974680 0.2% 520.0 -- NIPPON-RAD Nippon RAD Inc. 20 - AS29052 506 0.0% 506.0 -- LYCOS-AS INFORM P. LYKOS A.E TOP 20 Unstable Prefixes Rank Prefix Upds % Origin AS -- AS Name 1 - 109.161.64.0/20 21880 0.8% AS13118 -- ASN-YARTELECOM OJSC Rostelecom 2 - 108.61.128.0/18 16207 0.6% AS20473 -- AS-CHOOPA - Choopa, LLC 3 - 92.246.207.0/249404 0.3% AS48612 -- RTC-ORENBURG-AS CJSC Comstar-Regions 4 - 192.58.232.0/248937 0.3% AS6629 -- NOAA-AS - NOAA 5 - 120.28.62.0/24 7831 0.3% AS4775 -- GLOBE-TELECOM-AS Globe Telecoms 7 - 67.210.190.0/235896 0.2% AS11976 -- FIDN - Fidelity Communication International Inc. 8 - 115.170.128.0/17 5612 0.2% AS4847 -- CNIX-AP China Networks Inter-Exchange 9 - 67.210.188.0/234994 0.2% AS11976 -- FIDN - Fidelity Communication International Inc. 10 - 69.38.178.0/24 4342 0.2% AS19406 -- TWRS-MA - Towerstream I, Inc. 11 - 171.181.112.0/22 4318 0.2% AS19886 -- BOFABROKERDEALERSVCS - Bank of America 12 - 171.181.116.0/23 4318 0.2% AS19886 -- BOFABROKERDEALERSVCS - Bank of America 13 - 171.181.118.0/24 4318 0.2% AS19886 -- BOFABROKERDEALERSVCS - Bank of America 14 - 171.181.120.0/24 4296 0.2% AS19886 -- BOFABROKERDEALERSVCS - Bank of America 15 - 168.223.200.0/22 4251 0.2% AS7202 -- FAMU - Florida A M University 16 - 168.223.206.0/23 4245 0.2% AS7202 -- FAMU - Florida A M University 17 - 62.84.76.0/24 4215 0.2% AS42334 -- BBP-AS Broadband Plus s.a.l. 18 - 2.93.235.0/24 3970 0.1% AS8402 -- CORBINA-AS OJSC Vimpelcom 19 - 201.33.145.0/243561 0.1% AS11993 -- BANCO DO BRASIL S.A. 20 - 206.105.75.0/243529 0.1% AS6174 --
Re: web site bug report
Thanks very much for alerting us to this issue, and apologies for the inconvenience. When search was done by name it was throwing an error on the agenda path omitting 'nanog' from the path, hence the 404 page. This is now fixed. Kindly let us know if you run into any more issues with this. no biggie. bugs happen. of course, i never have any :) randy
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Seems to be working now from Verizon FIOS in Boston area. Henry Yen wrote: On Fri, Oct 04, 2013 at 12:30:01PM -0400, William Herrin wrote: 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 * * A little earlier, both FiOS and a uunet/701 connection yielded '!N', but as of this writing both paths are reaching that website. -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
