Connection to various websites dying at verizon-gni.net

[tripleg1]

As of yesterday morning, 6/21/12

I am unable to access any website with an IP in the range of 74.204.184.001 thru 74.204.187.255

As I calculated that is a total of 1020 IP addresses

7 of these IPs go to a server that I manage and visit 7 days a week.

The IPs are fully accessible from any non-verizon ISP. I have checked at a friends house 15 miles away who also has Verizon high speed internet, using their computer and there is no access there either.

I can access normally through a proxy or other ISP such as wifi at starbucks.

Traceroute shows it dying on in the verizon network:

>>>>>>>>>>

Tracing route to unknown135.184.204.74.defenderhosting.com [74.204.184.135]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter.westell.com [192.168.1.1]

  2    26 ms    25 ms    25 ms  L100.LSANCA-DSL-36.verizon-gni.net [{edited for privacy}]

  3     *        *        *     Request timed out.

  4  G0-6-0-2.LSANCA-LCR-22.verizon-gni.net [130.81.136.52]  reports: Destination net unreachable.

Trace complete.

<<<<<<<<<<

This problem occurs for IPs in the range noted above and only on Verizon ISP.

I can do a successful tracert to the IP addresses located just outside the endpoints of the range in question, 74.204.183.255 and 74.204.188.001, but anything in between (74.204.184.001 thru 74.204.187.255), 1,020 IP addresses, only 7 of which go to my server, the tracert fails at verizon-gni.net.

I have already spent 4 hours on the phone with level 1 and 2 Verizon support, a complete waste of time. They deny the problem is on their end but the facts at hand listed above indicate otherwise. Also, for example, if I tracert to the IP just outside the lower end of the range 74.204.183.255 which does work, the hop after the one that fails on the IP range that don't work is still within the Verizon network "  4    33 ms    35 ms    28 ms  so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.126] "

From this information, I would discern:

1)There is a block on the IP range at hand within the Verizon network (74.204.184.001 thru 74.204.187.255)

2)Or for some reason in the communication between my Verizon IP and this range of IPs, Verizon network is directing to a point within the Verizon network that is not working properly and thus causing the communication to fail.

Any ideas?

It is urgent that I restore access, so I will either need to have Verizon fix this or find a new ISP.

[tripleg1]

Just wanted to update this as the problem spontaneously resolved itself about an hour ago. Total downtime was about 36 hours and I am hoping this does not reoccur.

[zTAR]

We are having the same issue as the original poster (started ~30 hours ago).  Using various lookinglass servers from throughout Europe, we results similar to this:

traceroute to 71.252.193.104 (71.252.193.104), 30 hops max, 38 byte packets
 1  alan5 (193.62.xxx.xxx)  1.486 ms  0.753 ms  0.735 ms
 2  gw-fw (193.63.74.131)  0.368 ms  0.267 ms  0.253 ms
 3  c-pop (193.63.74.226)  1.165 ms  0.956 ms  2.659 ms
 4  193.62.116.18 (193.62.116.18)  1.138 ms  1.095 ms  1.106 ms
 5  ae4.leed-sbr1.ja.net (146.97.40.241)  2.076 ms  2.099 ms  2.074 ms
 6  ae12.manc-sbr1.ja.net (146.97.33.157)  3.174 ms  3.205 ms  3.186 ms
 7  ae1.man11.ip4.tinet.net (77.67.94.169)  62.037 ms  8.648 ms  8.503 ms
 8  xe-0-0-0.nyc32.ip4.tinet.net (89.149.184.182)  77.545 ms xe-0-1-0.nyc32.ip4.tinet.net (89.149.181.114)  79.130 ms  79.076 ms
 9  TenGigE0-0-1-0.GW8.NYC4.ALTER.NET (152.179.72.121)  77.979 ms  84.978 ms  79.508 ms
10  0.xe-1-1-3.XT1.NYC4.ALTER.NET (152.63.21.122)  79.379 ms  77.724 ms  80.518 ms
11  0.so-14-0-0.NY325-BB-RTR1.verizon-gni.NET (152.63.1.42)  76.496 ms  78.034 ms  102.880 ms
12  * * *
13  * * *

{Edited for privacy.}