US Telco Support > Verizon > Verizon Fiber Optics > [Northeast] Higher pings tonight?

[Northeast] Higher pings tonight?

Yes, I have been experiencing what you've mentioned. The other guy on here from MA mentioned DNS requests timing out or taking a long time for him to complete. I've reset my NIC and pfSense machine but doesn't help that much.

reply to chrisb3127

reply to serge87
My home:

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
 
  2     3 ms     1 ms     2 ms
  3     4 ms     4 ms     3 ms  G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
  4     4 ms     3 ms     4 ms  so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
  5     5 ms     4 ms     3 ms  0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
  6     5 ms     4 ms     4 ms  0.ae4.BR3.NYC4.ALTER.NET [152.63.16.185]
  7     *      110 ms   122 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  8     *      112 ms   116 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
  9   122 ms     *      126 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 10   123 ms   108 ms   124 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
 11    41 ms    58 ms    28 ms  ae-14-60.car4.NewYork1.Level3.net [4.69.155.6]
 12   110 ms     *      110 ms  SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
 13   116 ms   117 ms   115 ms  resolver1.opendns.com [208.67.222.222]
 

I've noticed the same deal since Sandy hit NYC. The Alter.net hops haven't been performing too well. Perhaps aftermath storm damage or is there more to the picture that I'm missing?

C:\Users\>tracert resolver1.opendns.com
 
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     7 ms     6 ms     6 ms  10.41.15.1
  3     6 ms     7 ms     6 ms  P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
  4    19 ms    19 ms    19 ms  P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
  5    19 ms    19 ms    19 ms  so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
  6    19 ms    19 ms    18 ms  so-7-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.48]
  7    22 ms    21 ms    21 ms  0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
  8    20 ms    21 ms    21 ms  0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
  9    51 ms    52 ms    51 ms  204.255.173.54
 10    50 ms    51 ms    52 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
 11    54 ms    53 ms    53 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 12    60 ms    55 ms    59 ms  ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
 13    19 ms    19 ms    21 ms  ae-44-90.car4.NewYork1.Level3.net [4.69.155.198]
 14    54 ms    57 ms    56 ms  SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
 15    45 ms    45 ms    44 ms  resolver1.opendns.com [208.67.222.222]
 
Trace complete.
 
C:\Users\>tracert resolver1.opendns.com
 
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     7 ms     7 ms     6 ms  10.41.15.1
  3     6 ms     7 ms     6 ms  P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
  4    19 ms    19 ms    19 ms  P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
  5    19 ms    19 ms    18 ms  so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
  6    22 ms    23 ms    24 ms  so-7-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.48]
  7    74 ms   101 ms    21 ms  0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
  8    51 ms    25 ms    20 ms  0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
  9    47 ms    47 ms    47 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
 10    47 ms    48 ms    49 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
 11    45 ms    45 ms    44 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 12    67 ms    53 ms    54 ms  ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
 13    19 ms    21 ms    22 ms  ae-44-90.car4.NewYork1.Level3.net [4.69.155.198]
 14    67 ms    62 ms    62 ms  SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
 15    45 ms    45 ms    45 ms  resolver1.opendns.com [208.67.222.222]
 
Trace complete.
 
C:\Users\>
 

reply to chrisb3127
I noticed it around when Sandy hit also, but it was fine afterwards. Seems like every few days the pings trickle upward, sometimes in the 30s, but tonight it was almost 100ms. As I type this, they are back to normal (10-15ms vs the 80ms earlier) I haven't had any DNS issues since I use my own DNS servers. I constantly ping my co-location facility in Philly and noticed the high pings. I did a reverse trace from Philly--Fios and it shown a hop at verizon-gni.net causing the spike. Should we be reporting anything to VZ? I usually wait to call in since they like to blame the router or want to reboot the ONT, etc., when it's not even the issue.

I am sure no one has really noticed it yet due to the holidays and the chaos that Sandy has imposed on many people.

The fact remains that this is a 24/7 problem. Go ahead and tracert any IP address. Almost everything ends up going through the same few hops and I have seen the same issue on multiple connections at different locations around Queens.

  2     2 ms     1 ms     1 ms  
  3     3 ms     1 ms     2 ms  G0-1-1-4.NYCMNY-LCR-21.verizon-gni.net [130.81.146.230]
  4     6 ms     4 ms    10 ms  so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
  5     3 ms     4 ms     5 ms  0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
  6     5 ms     3 ms     4 ms  0.ae4.BR2.NYC4.ALTER.NET [152.63.3.118]
  7    28 ms     *       28 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  8    31 ms    30 ms    30 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
  9    29 ms    27 ms    27 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
 10    37 ms    26 ms    29 ms  ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
 11    31 ms    27 ms    28 ms  ae-1-60.edge2.NewYork1.Level3.net [4.69.155.16]
 12    29 ms    29 ms    29 ms  b.resolvers.Level3.net [4.2.2.2]
 
Trace complete.
 

Not Verizon but figured I would post my Comcast tracert in CT.

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 * * * Request timed out.
3 8 ms 9 ms 13 ms ---------
4 23 ms 19 ms 14 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
5 16 ms 15 ms 15 ms pos-3-8-0-0-ar01.needham.ma.boston.comcast.net [69.139.220.101]
6 48 ms 47 ms 47 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.93.185]
7 22 ms 19 ms 21 ms xe-8-2-0.edge1.NewYork2.Level3.net [4.71.186.17]
8 29 ms 21 ms 23 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 20 ms 19 ms 23 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 31 ms 24 ms 24 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
11 19 ms 21 ms 19 ms ae-14-60.car4.NewYork1.Level3.net [4.69.155.6]
12 42 ms 43 ms 41 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13 41 ms 41 ms 42 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

reply to chrisb3127
Pings are higher again, seems to happen as the day goes on, then will go back to normal late night. Right now I'm in the 30s. Some IPs will ping ok, others will be higher. For example, 8.8.8.8 will be 14ms, but my co-lo facility will be in the 30s.

reply to chrisb3127

Latency from 11/5/12 to 11/25/12

I've been in DM on Twitter with VZ tonight asking about the ping issue. I sent them some trace routes and am waiting to hear back. Wonder why it's so latent on pings lately?

reply to chrisb3127
The ping issues are even reflected in speedtests now. Speeds are def lower. This is the first time my speeds show less than 35/35.

»www.speedtest.net/result/2331840858.png
»www.speedtest.net/result/2331842424.png

Interesting, I did 3 tests back-to-back, same server. Now it's showing normal. Something has to be going on with their network:

»www.speedtest.net/result/2331843886.png

reply to chrisb3127
Funny thing is, I have noticed that it happens to the 4.2.2.4 ip for me...

Also, my speeds have been affected for downloads from that side of the network:

traceroute to 4.2.2.4 (4.2.2.4), 30 hops max, 60 byte packets
 1  FIOSWAN (10.0.0.1)  0.336 ms  0.850 ms  0.809 ms
 2  L100.HRBGPA-VFTTP-12.verizon-gni.net (98.117.0.1)  3.414 ms  3.567 ms  3.723 ms
 3  G9-0-4-112.HRBGPA-LCR-01.verizon-gni.net (130.81.137.120)  5.461 ms  5.934 ms  6.639 ms
 4  P12-0-0.HRBGPA-LCR-02.verizon-gni.net (130.81.27.185)  19.635 ms  20.336 ms  21.199 ms
 5  so-12-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.254)  21.051 ms  21.106 ms  21.036 ms
 6  0.ae2.BR2.IAD8.ALTER.NET (152.63.34.73)  22.476 ms  21.346 ms  21.173 ms
 7  ae16.edge1.washingtondc12.level3.net (4.68.62.133)  96.899 ms ae17.edge1.washingtondc12.level3.net (4.68.62.137)  95.516 ms ae16.edge1.washingtondc12.level3.net (4.68.62.133)  94.624 ms
 8  d.resolvers.level3.net (4.2.2.4)  112.241 ms  112.803 ms  113.517 ms
 

reply to chrisb3127
VZ on Twitter said to only use their speedtest, and of course that checked out fine. They are basically saying the issues are outside of their network. Does a reverse trace carry any weight? (From another location to my VZ IP) A reverse trace showed normal responses until it hits the verizon-gni.net hop. I'm at a loss what we could do about it.

reply to chrisb3127
I haven't noticed that or tested that, but what I have noticed in the last 3 days or so is that instead of getting 25/25 I am getting 25/4. Verizon tested my line and found nothing odd, they made me reset my router and it didn't fix the problem (as I didn't expect it to). They are sending me a new router - which I also don't think will fix the problem, I hope I am proven wrong.

Has anyone noticed that too?

Finally more people are noticing this. Something is up between Verizon/Alter and Level 3.

Not everything is being affected, but MOST destinations are.

Problem is that this slowdown and higher latency doesn't affect everyone on 35Mbit/lower connections. We on 50/75/150 are seeing it very easily every single day now.

I am on 75/35 and am seeing pings that are no different than when I had Cox cable.

reply to RolteC
Now it's back to normal, I knew it wasn't the router. What a waste of Verizon's money sending me a new router to fix the problem.

reply to chrisb3127
Pings were normal (10-15ms) late last night and into this afternoon. Now we're back to timeouts and constant 30-70ms pings again. So the issue seems to happen during "peak" hours of the afternoon and evening. VZ really wouldn't tell me much, other than that it's "outside" their network, even though it's probably occuring on a VZ peer. How should we complain about this so they at least research the issue?

reply to chrisb3127
I am in South Central NJ on a 25/5 plan and I too am experiencing high latency and slow download speeds. I've noticed on speakeasy that when I test the NY server my speeds are consistently good, but when I select virtually any other server my download speeds are awful.