verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
Matthew Huff
mhuff at ox.com
Fri Oct 4 16:17:51 UTC 2013
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 at 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 at newton> dig +short www.floksociety.org.
200.10.150.169
<root at 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>
<title>503 Service Unavailable</title>
</head>
<body>
<h1>Error 503 Service Unavailable</h1>
<p>Service Unavailable</p>
<h3>Guru Meditation:</h3>
<p>XID: 477990820</p>
<hr>
<p>Varnish cache server</p>
</body>
</html>
Connection to 200.10.150.169 closed by foreign host.
> -----Original Message-----
> From: Gordon Cook [mailto:cook at cookreport.com]
> Sent: Friday, October 04, 2013 12:10 PM
> To: nanog at 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 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. IN ANY
>
> ;; ANSWER SECTION:
> floksociety.org. 600 IN A 200.10.150.169
> floksociety.org. 3600 IN MX 10 mail.floksociety.org.
> floksociety.org. 3600 IN NS ns57.domaincontrol.com.
> floksociety.org. 3600 IN NS ns58.domaincontrol.com.
> floksociety.org. 3600 IN SOA ns57.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_docman&task=cat_view&gid=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
> =============================================================
>
>
>
>
>
>
>
>
>
More information about the NANOG
mailing list