High Ping on Fios - Need help.

[dpmalito99]

here are a few other pings..

ping www.imdb.com
PING us.dd.imdb.com (72.21.215.52): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

ping www.verizon.com
PING e2546.g.akamaiedge.net (184.50.250.120): 56 data bytes
64 bytes from 184.50.250.120: icmp_seq=0 ttl=252 time=14.009 ms
64 bytes from 184.50.250.120: icmp_seq=1 ttl=252 time=19.578 ms
64 bytes from 184.50.250.120: icmp_seq=2 ttl=252 time=22.310 ms
64 bytes from 184.50.250.120: icmp_seq=3 ttl=252 time=16.647 ms
64 bytes from 184.50.250.120: icmp_seq=4 ttl=252 time=20.930 ms
64 bytes from 184.50.250.120: icmp_seq=5 ttl=252 time=18.956 ms
64 bytes from 184.50.250.120: icmp_seq=6 ttl=252 time=20.926 ms

here is the traceroute to verizon.com with my ip removed, of course

3 g1-5-5-0.nycmny-lcr-22.verizon-gni.net (130.81.189.102) 11.435 ms 12.559 ms 10.895 ms
4 so-3-1-0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.151.234) 23.147 ms 17.590 ms 10.705 ms
5 0.xe-3-1-3.xt1.nyc9.alter.net (152.63.4.53) 40.787 ms 13.627 ms 13.843 ms
6 * * 0.xe-2-1-3.xt1.nyc4.alter.net (152.63.3.6) 50.547 ms
7 tengige0-6-4-0.gw8.nyc4.alter.net (152.63.21.121) 14.834 ms
tengige0-6-2-0.gw8.nyc4.alter.net (152.63.21.117) 17.308 ms
tengige0-4-1-0.gw8.nyc4.alter.net (152.63.21.69) 46.976 ms
8 * * *
9 * * *
10 * * *
11 * * *

(continues on like this until I stop it)

here is yahoo.com traceroute

3 g0-11-1-6.nycmny-lcr-22.verizon-gni.net (130.81.107.242) 188.375 ms 227.931 ms 189.095 ms
4 so-5-0-0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.22.18) 247.268 ms 226.652 ms 231.750 ms
5 xe-8-1-0-0.res-bb-rtr1.verizon-gni.net (130.81.23.224) 227.468 ms 159.669 ms 82.830 ms
6 so-6-0-0-0.ash-peer-rtr1-re1.verizon-gni.net (130.81.10.90) 49.592 ms 35.307 ms 28.149 ms
7 130.81.15.10 (130.81.15.10) 30.655 ms 27.998 ms 29.905 ms
8 ae-6.pat2.dcp.yahoo.com (216.115.102.178) 24.603 ms 39.344 ms 29.929 ms
9 ae-7.pat2.che.yahoo.com (216.115.100.137) 54.793 ms
ae-2-d181.pat2.da3.yahoo.com (216.115.104.115) 138.749 ms 182.780 ms
10 unknown-216-115-96-x.yahoo.com (216.115.96.117) 244.160 ms 275.580 ms 246.741 ms
11 ge-0-0-0.pat2.bfz.yahoo.com (216.115.97.209) 213.583 ms
ae-4.msr1.bf1.yahoo.com (216.115.100.25) 96.835 ms 187.387 ms
12 ae-3.msr2.bf1.yahoo.com (216.115.100.31) 176.099 ms
xe-2-0-0.clr1-a-gdc.bf1.yahoo.com (98.139.232.93) 186.612 ms
xe-10-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.232.107) 191.931 ms
13 xe-5-0-0.clr1-a-gdc.bf1.yahoo.com (98.139.128.9) 238.167 ms
et-17-1.fab1-1-gdc.bf1.yahoo.com (98.139.128.37) 219.845 ms
xe-3-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.232.99) 234.252 ms
14 et-17-1.fab1-1-gdc.bf1.yahoo.com (98.139.128.37) 231.346 ms
po-9.bas1-7-prd.bf1.yahoo.com (98.139.129.145) 223.711 ms
et-17-1.fab5-1-gdc.bf1.yahoo.com (98.139.128.45) 246.433 ms
15 * *

(continues like this until i stop it)

Here is one more, www.imdb.com

3 g0-11-1-6.nycmny-lcr-22.verizon-gni.net (130.81.107.242) 25.241 ms 21.943 ms 27.046 ms
4 so-5-0-0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.22.18) 74.679 ms 84.411 ms 62.507 ms
5 0.xe-10-1-0.br1.nyc1.alter.net (152.63.18.225) 41.590 ms 88.132 ms 77.419 ms
6 pax-brdr-01.inet.qwest.net (63.235.40.53) 90.330 ms 94.977 ms 115.475 ms
7 dca2-edge-01.inet.qwest.net (67.14.36.10) 149.077 ms 120.185 ms 125.681 ms
8 65.120.78.82 (65.120.78.82) 135.199 ms
72.165.86.74 (72.165.86.74) 128.968 ms
67.133.224.206 (67.133.224.206) 35.000 ms
9 72.21.220.127 (72.21.220.127) 37.542 ms
72.21.220.151 (72.21.220.151) 111.914 ms
72.21.220.159 (72.21.220.159) 56.123 ms
10 205.251.245.53 (205.251.245.53) 38.650 ms 38.718 ms
72.21.222.157 (72.21.222.157) 29.487 ms
11 205.251.248.85 (205.251.248.85) 43.100 ms
205.251.248.87 (205.251.248.87) 25.237 ms
205.251.248.85 (205.251.248.85) 26.182 ms
12 * * *

hope that gives you some more insight

[tns]

IMDB or its ISP appear to have disabled responding to pings completely.  Doesn't stop me from getting great response from them.  Response are stopping either in or after it reaches qwest.

In general ping and even tracert are not that reliable a tool for web response.  More troubleshooting tools.

[GentleTyphoon]

I have the Quantum 150/65 service here in Brooklyn, NYC and I get the same slow down/ping issues.

pathping

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\RhizeX>pathping www.yahoo.com

Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]
over a maximum of 30 hops:
  0  RhizeX-PC.home [192.168.*.*]
  1  uter.home [192.168.*.*]
  2  L100.NYCMNY-VFTTP-200.verizon-gni.net [108.6.48.1]
  3  G0-3-3-4.NYCMNY-LCR-21.verizon-gni.net [130.81.177.64]
  4  130.81.151.228
  5  so-9-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.19.89]
  6  so-7-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.94]
  7  130.81.14.94
  8  ae-6.pat1.dcp.yahoo.com [216.115.102.174]
  9  ae-0.pat1.nyc.yahoo.com [216.115.101.156]
 10  ae-7.pat2.che.yahoo.com [216.115.100.137]
 11  ae-3.msr2.bf1.yahoo.com [216.115.100.31]
 12  ae-4.pat1.bfz.yahoo.com [216.115.97.211]
 13  et-18-25.fab2-1-gdc.bf1.yahoo.com [98.139.128.55]
 14  po-9.bas2-7-prd.bf1.yahoo.com [98.139.129.147]
 15  et-18-25.fab1-1-gdc.bf1.yahoo.com [98.139.128.53]
 16  ir2.fp.vip.bf1.yahoo.com [98.139.183.24]

Computing statistics for 400 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           RhizeX-PC.home [192.168.*.*]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  uter.home [192.168.*.*]
                                0/ 100 =  0%   |
  2   11ms     0/ 100 =  0%     0/ 100 =  0%  L100.NYCMNY-VFTTP-200.verizon-gni.
net [108.6.48.1]
                                0/ 100 =  0%   |
  3    5ms     0/ 100 =  0%     0/ 100 =  0%  G0-3-3-4.NYCMNY-LCR-21.verizon-gni
.net [130.81.177.64]
                                0/ 100 =  0%   |
  4   11ms     0/ 100 =  0%     0/ 100 =  0%  130.81.151.228
                                0/ 100 =  0%   |
  5   19ms     0/ 100 =  0%     0/ 100 =  0%  so-9-0-0-0.RES-BB-RTR1.verizon-gni
.net [130.81.19.89]
                                0/ 100 =  0%   |
  6   18ms     0/ 100 =  0%     0/ 100 =  0%  so-7-0-0-0.ASH-PEER-RTR1-re1.veriz
on-gni.net [130.81.10.94]
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  130.81.14.94
                                0/ 100 =  0%   |
  8   20ms     0/ 100 =  0%     0/ 100 =  0%  ae-6.pat1.dcp.yahoo.com [216.115.1
02.174]
                                0/ 100 =  0%   |
  9   24ms     0/ 100 =  0%     0/ 100 =  0%  ae-0.pat1.nyc.yahoo.com [216.115.1
01.156]
                                0/ 100 =  0%   |
 10   38ms     0/ 100 =  0%     0/ 100 =  0%  ae-7.pat2.che.yahoo.com [216.115.1
00.137]
                                0/ 100 =  0%   |
 11   43ms     0/ 100 =  0%     0/ 100 =  0%  ae-3.msr2.bf1.yahoo.com [216.115.1
00.31]
                                0/ 100 =  0%   |
 12   39ms     0/ 100 =  0%     0/ 100 =  0%  ae-4.pat1.bfz.yahoo.com [216.115.9
7.211]
                                0/ 100 =  0%   |
 13   47ms     0/ 100 =  0%     0/ 100 =  0%  et-18-25.fab2-1-gdc.bf1.yahoo.com
[98.139.128.55]
                                0/ 100 =  0%   |
 14   39ms     0/ 100 =  0%     0/ 100 =  0%  po-9.bas2-7-prd.bf1.yahoo.com [98.
139.129.147]
                                0/ 100 =  0%   |
 15   49ms     0/ 100 =  0%     0/ 100 =  0%  et-18-25.fab1-1-gdc.bf1.yahoo.com
[98.139.128.53]
                               44/ 100 = 44%   |
 16   95ms    44/ 100 = 44%     0/ 100 =  0%  ir2.fp.vip.bf1.yahoo.com [98.139.1
83.24]

Trace complete.

NYC towerstream
http://www.speedtest.net/result/2183833080.png

Secaucus Jersey
http://www.speedtest.net/result/2183834468.png

VZ-NY

VZ-NJ

[dpmalito99]

TNS if its not a reliable system for measuring that's fine. Just tell me what to use, and tell me why others besides me (now three of us) are reporting the same issues.

Seems like somethign happened with Verizon service in the last month or so. My guess is there are others out there who are suffering from it but woudlnt notice it if it fell on their head cause they arent gamers.

Verizon official, please tell us what to do from here....

[tns]

Presumably something is wrong, perhaps with verizon, perhaps with the site your going and perhaps with some intermediate server belonging to some other entity.

But as clearly is shown with IMDB.com, some servers will not respond to pings or tracert.  My tracert to it also never completes.

tracert imdb.com

Tracing route to imdb.com [72.21.206.80]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     2 ms     1 ms     2 ms  hidden for privacy

  3     4 ms     4 ms     4 ms  G0-11-2-7.NYCMNY-LCR-21.verizon-gni.net [130.81.187.216]
  4     5 ms     4 ms     4 ms  130.81.151.228
  5     5 ms     5 ms     5 ms  0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
  6     5 ms     5 ms     5 ms  jfk-brdr-04.inet.qwest.net [63.235.40.53]
  7    13 ms    13 ms    12 ms  dca2-edge-01.inet.qwest.net [67.14.36.10]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.

And yet imdb.com is responding in a way less then a second with a complete page.

And other traces people are showing have shown how low a priortiy these traces are being responded with sometimes getting huge rsponse times or timing out, when the end server shows less than a 10-30 ms response time.

Other than measuring the reponse time to your normal request, there probably is nothing that will help you  when pings and tracert fail to give you any guidance.  Some tools exist to just measure that, i.e. send a normal tcpip requests to a standard port (e.g http port 80) and see how long it takes to get a response.

[Tsuki]

Update for everyone, I have not gotten a call back from Verizon after escalating the issue to tier 2 support.  BUT, the day after escalating, my latency has decreased significantly.  It's still not as good as when I first signed up but now it's actually usable.  They must have found the issue somewhere and resolved it.  They should as least contact me and let me know what is going on so if this ever happens again, it doesn't take 2 weeks of calling, troubleshooting, and frustration to get it resolved.  Makes me feel that they don't want to admit it was actually Verizon's issue the whole time.

Thanks everyone for the help.

dpmalito99, You need keep calling them.  😞  Goodluck.  

[Tsuki]

I take that all back.  It's happening again.  This is terrible.  Even worst now.

C:\Documents and Settings\Mei>tracert www.google.com

Tracing route to www.google.com [173.194.75.103]
over a maximum of 30 hops:

1 6 ms 8 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 11 ms 8 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 331 ms 312 ms 320 ms G4-3-662.NWRKNJ-LCR-06.verizon-gni.net [130.81.104.86]
4 418 ms 324 ms 309 ms so-6-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.28.150]
5 364 ms 283 ms 431 ms 0.xe-8-0-0.XL4.NYC1.ALTER.NET [152.63.5.217]
6 19 ms 17 ms 9 ms 0.xe-11-0-0.GW13.NYC1.ALTER.NET [152.63.18.114]
7 18 ms 10 ms 9 ms google-gw.customer.alter.net [157.130.249.6]
8 15 ms 20 ms 19 ms 72.14.239.46
9 326 ms 354 ms 21 ms 209.85.251.37
10 323 ms 330 ms 335 ms 209.85.249.11
11 36 ms 384 ms 29 ms 209.85.241.222
12 35 ms 314 ms 326 ms 216.239.48.59
13 * * * Request timed out.
14 335 ms 314 ms 319 ms ve-in-f103.1e100.net [173.194.75.103]

Trace complete.

C:\Documents and Settings\Mei>tracert www.yahoo.com

Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 19 ms 9 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 12 ms 12 ms 9 ms G9-0-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.48.18]
4 16 ms 8 ms 9 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
5 46 ms 105 ms 25 ms xe-3-1-1-0.RES-BB-RTR1.verizon-gni.net [130.81.23.155]
6 27 ms 25 ms 18 ms so-6-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.90]
7 350 ms 385 ms 333 ms 130.81.15.170
8 31 ms 30 ms 28 ms ae-6.pat1.dcp.yahoo.com [216.115.102.174]
9 353 ms 408 ms 409 ms ae-3.pat2.dcp.yahoo.com [216.115.102.117]
10 316 ms 315 ms 321 ms ae-7.pat2.che.yahoo.com [216.115.100.137]
11 58 ms 52 ms 51 ms ae-3.msr1.bf1.yahoo.com [216.115.100.29]
12 45 ms 48 ms 48 ms ge-0-0-0.pat2.bfz.yahoo.com [216.115.97.209]
13 356 ms 78 ms 54 ms et-17-1.fab2-1-gdc.bf1.yahoo.com [98.139.128.39]
14 340 ms 65 ms 49 ms xe-7-0-0.clr1-a-gdc.bf1.yahoo.com [98.139.128.17]
15 425 ms 127 ms 99 ms ir2.fp.vip.bf1.yahoo.com [98.139.183.24]

Trace complete.

[bagher]

I'm having the same problem, wireless is useless, even plugged in its unbearable.  They are sending me yet another router...

[TonyaD_VZ]

We sent you a message on our private support board to assist you and we did not receive a response. Please repost the issue if you are still experiencing a problem so that we may assist you. Tonya C.