High Ping on Fios - Need help.

[Tsuki]

Hi Everyone,

I have spoken to 3 verizon agents and changed my router but still experiencing issues.  Reaching out to the community for help.  Here is my frustration in detail.  Up till last week, I had good speeds (on 15/5 plan) and average around 10-20ms pings so everything was running smoothly.  I was very happy with the performance but then everything went downhill.  The speed is still good but now I’m getting 60ms pings in the early mornings, 150ms pings in the afternoon, and at night (prime time) 300-400ms ping.  The first 2 agents I spoke ran the optimizer, ran various tests, and finally sent me a new router which didn’t resolve it.  The 3rd agent I spoke - I tried explaining that it’s not an issue with speed at all.  I’m getting good speed but high ping which means (from my understanding) there is issue with the routing of the traffic?  If I do tracert to google.com, verizon.net, or any other site, the ping jumps and sometimes there is Request Timed Out.  I believe there is indeed an issue on Verizon server end but the agent kept insisting that the high ping is coming from outside their network so they can’t do anything about it.  I mean, if it’s a single site like google, then fine, maybe google is having issues but it’s EVERY single site giving me high ping.  The whole world wide web can’t be returning a slow response.  After stating that point, the agent told me 300ms ping is .3 seconds, which is still very fast and acceptable.  To me that’s NOT acceptable at all.. This is 2012 and fiber optics.  If Verizon tells me that they feel 300ms ping is acceptable on fiber optics, then I might as well get dial-up.

If anyone can offer any help, it would be really appreciated.  I’m extremely tired of speaking to agents who doesn’t seem to want to take accountability on the issue and tell me they can’t do anything.  If this doesn’t get resolved in next few days, I will need to cancel. 

I really expected more from Verizon.  They are known to have great customer service and support.  Very disappointed.

Read On for Conspiracy theory thought :

Ok, so all this happened the day after I spoke to a CSR (called in to get some of my account info – not related to connection issues) who tried to get me to upgrade to the next tier.  He kept urging me to upgrade and I told him I’m happy with my speed and don’t need to upgrade.  The next day after this call I started having issues.  Are they purposing throttling me?  Or set some kind of limitation on my connection so I’ll be like "Oh I do need higher speed and upgrade after all"? 

Thanks.

[Edit] Just for everyone's info, I work in technology (though not networking) so I have knowledge on how all this works.  I have done all the usual checks to make sure it's not an issue with my computer.  [/Edit]

[Hubrisnxs]

hi, that is an unusually high ping time,  can you do the traceroute again and post the results here?  we can take a look and see where the problem is happening and might be able to point you in the right direction. 

also if you could download MTR (it's an advanced traceroute system-Freeware) and gives more details. 

[Tsuki]

Here are tracert for 3 different times in the day.

1:00AM

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

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

1 3 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 9 ms 9 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 48 ms 38 ms 37 ms G4-3-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.8]
4 135 ms 48 ms 46 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
5 63 ms 54 ms 52 ms 0.so-7-1-0.XL3.EWR6.ALTER.NET [152.63.17.141]
6 46 ms 47 ms 38 ms 0.so-6-0-2.XT1.NYC4.ALTER.NET [152.63.10.21]
7 88 ms 40 ms 53 ms TenGigE0-4-4-0.GW8.NYC4.ALTER.NET [152.63.18.202]
8 15 ms 31 ms 17 ms google-gw.customer.alter.net [152.179.72.62]
9 11 ms 10 ms 105 ms 72.14.238.232
10 62 ms 20 ms 27 ms 209.85.252.2
11 60 ms 62 ms 55 ms 72.14.239.93
12 32 ms 55 ms 35 ms 209.85.241.222
13 70 ms 35 ms 70 ms 216.239.48.183
14 * * * Request timed out.
15 88 ms 81 ms 80 ms ve-in-f106.1e100.net [173.194.75.106]

Trace complete.

8:00AM

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

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

1 3 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 16 ms 9 ms 9 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 10 ms 9 ms 9 ms G4-3-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.8]
4 18 ms 9 ms 9 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
5 12 ms 8 ms 9 ms 0.so-7-1-0.XL3.EWR6.ALTER.NET [152.63.17.141]
6 21 ms 17 ms 28 ms 0.so-1-0-1.XT1.NYC4.ALTER.NET [152.63.0.213]
7 22 ms 16 ms 13 ms TenGigE0-4-1-0.GW8.NYC4.ALTER.NET [152.63.21.69]
8 16 ms 19 ms 18 ms google-gw.customer.alter.net [152.179.72.62]
9 11 ms 11 ms 17 ms 72.14.238.232
10 14 ms 23 ms 19 ms 209.85.252.2
11 18 ms 18 ms 20 ms 209.85.249.11
12 34 ms 28 ms 30 ms 209.85.243.114
13 36 ms 29 ms 29 ms 64.233.174.87
14 * * * Request timed out.
15 33 ms 29 ms 29 ms vb-in-f147.1e100.net [173.194.73.147]

Trace complete.

8:00PM

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

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

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 13 ms 10 ms 8 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 173 ms 167 ms 176 ms G4-3-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.8]
4 200 ms 187 ms 167 ms so-6-0-2-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.148]
5 152 ms 227 ms 176 ms 0.xe-8-1-0.XL3.NYC1.ALTER.NET [152.63.5.213]
6 170 ms 165 ms 168 ms 0.xe-8-1-0.GW13.NYC1.ALTER.NET [152.63.4.133]
7 71 ms 63 ms 66 ms google-gw.customer.alter.net [157.130.249.6]
8 43 ms 21 ms 20 ms 72.14.239.248
9 215 ms 195 ms 199 ms 209.85.252.2
10 186 ms 32 ms 26 ms 72.14.239.93
11 207 ms 59 ms 209 ms 209.85.241.222
12 199 ms 34 ms 203 ms 64.233.174.117
13 * * * Request timed out.
14 187 ms 189 ms 184 ms vb-in-f99.1e100.net [173.194.73.99]

Trace complete.

[Hubrisnxs]

well it looks like when it gets bad is at the google hops (209.85.252.2) for example.

This is kinda a long shot, but try it.  

The trick here is that you have to leave your router dead (no power no nothing) for at least 5-10 minutes.  Don't take that number lightly, because if you turn it on too fast, you run the risk of grabbing the same ip address from their head end.  

Again a long shot, but try to release your IP address, and then as soon as you release the ip address, immediately turn off your router.  and come back to it at least 5-10 minutes later.

• How do I release my DHCP lease

The goal here, to me, is to get a new ip and hopefully a new route that is good.  If it's truly a problem at googles end (which is possible because they have been chincy on bandwidth upgrades since they bought youtube) then there might not be a lot you can do in the short term.   nothing immediate comes to mind at least.  but we have a lot of experienced users here, so I would also check back and let us know if the dhcp thing helps, or at least to pick up some differing opinions.   

[Tsuki]

Thanks for the suggestion but it did not work.

Just to reiterate, I'm getting these numbers for every single server/website/company I trace route to.  It can be yahoo.com, microsoft.com, apple.com, and even verizon.net themselves.  I don't think it's plausible that every single server out there is giving back a slow response.  

[tns]

---

@Tsuki wrote:

Thanks for the suggestion but it did not work.

Just to reiterate, I'm getting these numbers for every single server/website/company I trace route to.  It can be yahoo.com, microsoft.com, apple.com, and even verizon.net themselves.  I don't think it's plausible that every single server out there is giving back a slow response.  

---

The internet is a huge complex of different servers/devices run by many different entities.  Verizon can only be held responsisble for slow responses on their part of the network.  At least the traces you provided show the problem as elsewhere in the network.  In the case you showed it looks to be in a google server.

[smith6612]

2 13 ms 10 ms 8 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 173 ms 167 ms 176 ms G4-3-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.8]

These two hops have a problematic link. Verizon needs to fix this problem, not Google/Yahoo/whoever. Let me see if I can get someone.

[tns]

---

@Smith6612 wrote:

2 13 ms 10 ms 8 ms L100.NWRKNJ-VFTTP-62.verizon-gni.net {edited for privacy}
3 173 ms 167 ms 176 ms G4-3-562.NWRKNJ-LCR-05.verizon-gni.net [130.81.97.8]

These two hops have a problematic link. Verizon needs to fix this problem, not Google/Yahoo/whoever. Let me see if I can get someone.

---

SInce the ping response time goes down on hops  after that its really not significant.  Lots of these intermediate servers have pings at the lowest priority, and some are set to never respond.

[smith6612]

They go down but they are also all over the place too. Even to hops beyond that you're seeing plenty of latency, and considering how awfully slow Windows' traceroute utility runs it's adding in additional factors not being measured. If anything an MTR should be ran.

The hop can have high latency if it's under load or is set to not respond to them with priority but everything else better spit out clean or it's no good. You can't have 3-5 Alter.net (Verizon Business) hops followed with Google hops seeing shoddy latency. ICMP/UDP Echo traffic can be de-prioritized from one router and be queued en-route to upstream routers, but that is a bad network practice and should never, ever be done in the backbone. Backbone router's job is to deliver the traffic efficently, not try to manage Tens to Hundreds of Gigabits by delaying certain types of traffic. The edge router on both ends and the client/servier device has the job of managing QoS of the connection.

Verizon's network doesn't normally pass ICMP traffic poorly after a router of theres. For example, see this trace:

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

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     6 ms     6 ms     6 ms  10.41.15.1
  3     6 ms     6 ms     6 ms  P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
  4    16 ms    16 ms    16 ms  so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
  5    16 ms    17 ms    16 ms  0.ge-0-3-0.XL3.EWR6.ALTER.NET [152.63.5.221]
  6    18 ms    18 ms    18 ms  0.so-1-0-1.XT1.NYC4.ALTER.NET [152.63.0.213]
  7    18 ms    18 ms    18 ms  TenGigE0-6-2-0.GW8.NYC4.ALTER.NET [152.63.21.117]
  8    71 ms    71 ms    70 ms  google-gw.customer.alter.net [152.179.72.62]
  9    18 ms    17 ms    17 ms  72.14.238.232
 10    19 ms    18 ms    19 ms  209.85.251.88
 11    25 ms    25 ms    25 ms  209.85.249.11
 12    37 ms    37 ms    36 ms  209.85.241.222
 13    36 ms    35 ms    35 ms  209.85.251.228
 14     *        *        *     Request timed out.
 15    36 ms    37 ms    35 ms  vb-in-f105.1e100.net [173.194.73.105]

Trace complete.

And another...

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  192.168.3.1
  2     6 ms     6 ms     6 ms  10.41.15.1
  3     7 ms     6 ms     7 ms  P1-0.BFLONY-LCR-02.verizon-gni.net [130.81.195.222]
  4    25 ms    25 ms    25 ms  P11-0-0.BFLONY-LCR-01.verizon-gni.net [130.81.27.62]
  5    17 ms    16 ms    17 ms  so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
  6    27 ms    26 ms    25 ms  xe-3-1-1-0.RES-BB-RTR1.verizon-gni.net [130.81.23.155]
  7    26 ms    27 ms    26 ms  so-6-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.90]
  8    26 ms    26 ms    26 ms  130.81.15.110
  9    25 ms    25 ms    26 ms  ae-6.pat2.dce.yahoo.com [216.115.102.176]
 10    31 ms    32 ms    32 ms  ae-4.pat2.che.yahoo.com [216.115.101.145]
 11    32 ms    34 ms    32 ms  UNKNOWN-216-115-96-X.yahoo.com [216.115.96.117]
 12    41 ms    42 ms    43 ms  ae-3.msr2.bf1.yahoo.com [216.115.100.31]
 13    42 ms    42 ms    43 ms  ae-3.msr1.bf1.yahoo.com [216.115.100.29]
 14    43 ms    42 ms    41 ms  xe-4-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.83]
 15    55 ms    57 ms    70 ms  et-18-25.fab8-1-gdc.bf1.yahoo.com [98.139.128.67]
 16    45 ms    45 ms    45 ms  ir2.fp.vip.bf1.yahoo.com [98.139.183.24]

Trace complete.

Google's Gateway router with Verizon clearly shows a sign of possible problems and it was in the past, but it has ICMP response set as low priority, since the trace is quite clean going to Google's network. The trace to Yahoo! also reflect this. I see extra latency on Verizon hops but the trace comes out clean afterwards.

Point of the matter is, if it was just ICMP traffic the user shouldn't be seeing additional latency on the programs they themselves are running which from the sounds of their post, they certainly are. Yahoo! and Google have ICMP traffic set to low priority as well and normally my trace to Yahoo! gets pretty nasty looking during the day, but it still feels 40ms even when ICMP shows 500+ms.

Speed can still arrive even with latency, so there's one factor to already keep in mind. If the user is seeing latency, it's either intentional or a problem. Intentional would not cause performance issues speed or latent wise for the user.

[Tsuki]

Thanks everyone for the input.  I will run MRT when I get home tonight.

[Matthew_VZ]

Our Network techs advse to do this "pathping www.yahoo.com this command will do a tracert to yahoo, and then ping each hop 100 times. If there is packet loss, it will tell us which segment is affected"

 

Please keep us posted, also can you please post a screenshot of a speedtest?

 

^MMP 

[Tsuki]

That is the speedtest result.  The pathping hangs so can't really post the result on that.

[Tsuki]

Pretty much going to give up on this.  Got a call around 4pm yesterday from a representative, which was very nice because they are following up but I wasn't home (clearly stated on the form saying that if there is a need to troubleshoot, please call after 7pm).  The rep told me to call back the Verzion Customer Service line when I get home.  I did so and I got a rep who couldn't even bring up my account info.  Gave him my name, address, phone number, and even the serial number on my tv box.  He goes oh, that box is showing up on someone else's name.  I asked to speak to someone else cause he clearly didn't know what he was doing.  He transferred me to a non-tech line and they told me to call back.  I called back and got a rep who did NOT know what ping or latency meant at all.  All she kept asking me was what speedtest.net was showing.  And that my issue was once again not within verizon network and they couldn't do about it.  She didn't even do the normal troubleshooting, such as logging into my computer and checking my router, etc...  All she did was read the notes back to me from all the other agents I spoke to.  I don't know how many times I have to say that it's not an issue with speed, it's on both wireless and wired, it's happening on all my connections, to every single website, company, server I try to route to.  Whether it be from my laptop or desktop.  

How does a technical support person not know what ping or latency meant?  It's as if all they know is if you have high speed it means good connection and that's it.  There is more to networking then that.  I asked for escalation as well but all I got back was the issue is outside of our servers and out of our control... I'm baffled and tired of this.

[Adam_VZ]

Tsuki,

We would certainly like to escalate this for you, we just need data to demonstrate the issue that you're experiencing.  If you're able to supply a pathping, please let us know.

-adam

[dpmalito99]

i am having this issue now too!!

OMG this is horrible! I cannot believe it! IUp until about two days ago my pings were great! Best ive ever had!

Now I get 350-250 pings and I cannot play ANY ONLINE GAMES.. What the heck Verzion?

This is obviously not mine or the other guy's fault since it now is confirmed to happen two multiple users!

I REALLY hope someone follows up with me at my email {edited for privacy}

I need to solve this or I have no choice but to cancel V FIOS for not providing the internet service they promised. Shame, too, cause its been so great till now, and i was even thinking of  going up a speed tier! NOt with 350 pings, though.

Here is my yahoo ping from tonight, 730pm, its horrible.

dans-mac-mini:~ macmini$ ping www.yahoo.com
PING ds-any-fp3-real.wa1.b.yahoo.com (98.139.183.24): 56 data bytes
64 bytes from 98.139.183.24: icmp_seq=0 ttl=50 time=245.099 ms
64 bytes from 98.139.183.24: icmp_seq=1 ttl=50 time=259.619 ms
64 bytes from 98.139.183.24: icmp_seq=2 ttl=50 time=279.811 ms
64 bytes from 98.139.183.24: icmp_seq=3 ttl=49 time=281.032 ms
64 bytes from 98.139.183.24: icmp_seq=4 ttl=50 time=336.200 ms
64 bytes from 98.139.183.24: icmp_seq=5 ttl=50 time=284.526 ms
64 bytes from 98.139.183.24: icmp_seq=6 ttl=49 time=283.881 ms
64 bytes from 98.139.183.24: icmp_seq=7 ttl=49 time=372.759 ms
64 bytes from 98.139.183.24: icmp_seq=8 ttl=49 time=407.806 ms
64 bytes from 98.139.183.24: icmp_seq=9 ttl=50 time=274.069 ms
64 bytes from 98.139.183.24: icmp_seq=10 ttl=50 time=289.648 ms
64 bytes from 98.139.183.24: icmp_seq=11 ttl=50 time=309.376 ms
64 bytes from 98.139.183.24: icmp_seq=12 ttl=50 time=305.871 ms
64 bytes from 98.139.183.24: icmp_seq=13 ttl=50 time=365.200 ms
64 bytes from 98.139.183.24: icmp_seq=14 ttl=50 time=299.311 ms
64 bytes from 98.139.183.24: icmp_seq=15 ttl=49 time=253.037 ms
64 bytes from 98.139.183.24: icmp_seq=16 ttl=49 time=101.292 ms
64 bytes from 98.139.183.24: icmp_seq=17 ttl=49 time=115.261 ms
64 bytes from 98.139.183.24: icmp_seq=18 ttl=49 time=257.085 ms
64 bytes from 98.139.183.24: icmp_seq=19 ttl=50 time=394.982 ms
64 bytes from 98.139.183.24: icmp_seq=20 ttl=49 time=455.398 ms
64 bytes from 98.139.183.24: icmp_seq=21 ttl=50 time=409.752 ms
64 bytes from 98.139.183.24: icmp_seq=22 ttl=49 time=334.450 ms
64 bytes from 98.139.183.24: icmp_seq=23 ttl=50 time=276.900 ms
64 bytes from 98.139.183.24: icmp_seq=24 ttl=49 time=292.738 ms
64 bytes from 98.139.183.24: icmp_seq=25 ttl=49 time=309.991 ms
64 bytes from 98.139.183.24: icmp_seq=26 ttl=49 time=271.132 ms
64 bytes from 98.139.183.24: icmp_seq=27 ttl=50 time=367.514 ms
64 bytes from 98.139.183.24: icmp_seq=28 ttl=50 time=338.885 ms
64 bytes from 98.139.183.24: icmp_seq=29 ttl=49 time=310.891 ms
64 bytes from 98.139.183.24: icmp_seq=30 ttl=50 time=285.998 ms
64 bytes from 98.139.183.24: icmp_seq=31 ttl=49 time=329.646 ms
64 bytes from 98.139.183.24: icmp_seq=32 ttl=49 time=256.469 ms
64 bytes from 98.139.183.24: icmp_seq=33 ttl=49 time=326.909 ms
64 bytes from 98.139.183.24: icmp_seq=34 ttl=50 time=276.332 ms
64 bytes from 98.139.183.24: icmp_seq=35 ttl=49 time=288.038 ms
64 bytes from 98.139.183.24: icmp_seq=36 ttl=50 time=274.488 ms
64 bytes from 98.139.183.24: icmp_seq=37 ttl=49 time=281.576 ms
64 bytes from 98.139.183.24: icmp_seq=38 ttl=49 time=286.445 ms
64 bytes from 98.139.183.24: icmp_seq=39 ttl=49 time=280.490 ms
64 bytes from 98.139.183.24: icmp_seq=40 ttl=49 time=283.214 ms
64 bytes from 98.139.183.24: icmp_seq=41 ttl=49 time=301.349 ms
64 bytes from 98.139.183.24: icmp_seq=42 ttl=50 time=414.717 ms
64 bytes from 98.139.183.24: icmp_seq=43 ttl=49 time=373.588 ms
64 bytes from 98.139.183.24: icmp_seq=44 ttl=49 time=273.080 ms
64 bytes from 98.139.183.24: icmp_seq=45 ttl=49 time=308.087 ms
64 bytes from 98.139.183.24: icmp_seq=46 ttl=49 time=301.121 ms
64 bytes from 98.139.183.24: icmp_seq=47 ttl=49 time=409.956 ms
64 bytes from 98.139.183.24: icmp_seq=48 ttl=49 time=357.452 ms
64 bytes from 98.139.183.24: icmp_seq=49 ttl=49 time=252.883 ms
64 bytes from 98.139.183.24: icmp_seq=50 ttl=50 time=268.957 ms
64 bytes from 98.139.183.24: icmp_seq=51 ttl=50 time=349.809 ms
64 bytes from 98.139.183.24: icmp_seq=52 ttl=49 time=263.840 ms
64 bytes from 98.139.183.24: icmp_seq=53 ttl=49 time=329.883 ms
64 bytes from 98.139.183.24: icmp_seq=54 ttl=49 time=358.976 ms
64 bytes from 98.139.183.24: icmp_seq=55 ttl=49 time=282.272 ms
64 bytes from 98.139.183.24: icmp_seq=56 ttl=50 time=301.100 ms
64 bytes from 98.139.183.24: icmp_seq=57 ttl=50 time=160.245 ms
64 bytes from 98.139.183.24: icmp_seq=58 ttl=49 time=291.471 ms
64 bytes from 98.139.183.24: icmp_seq=59 ttl=50 time=485.736 ms
64 bytes from 98.139.183.24: icmp_seq=60 ttl=50 time=442.618 ms
64 bytes from 98.139.183.24: icmp_seq=61 ttl=49 time=335.997 ms
64 bytes from 98.139.183.24: icmp_seq=62 ttl=50 time=469.311 ms
64 bytes from 98.139.183.24: icmp_seq=63 ttl=50 time=424.605 ms
64 bytes from 98.139.183.24: icmp_seq=64 ttl=49 time=474.836 ms
64 bytes from 98.139.183.24: icmp_seq=65 ttl=49 time=347.626 ms
64 bytes from 98.139.183.24: icmp_seq=66 ttl=49 time=266.602 ms
64 bytes from 98.139.183.24: icmp_seq=67 ttl=49 time=301.959 ms
64 bytes from 98.139.183.24: icmp_seq=68 ttl=49 time=310.081 ms
64 bytes from 98.139.183.24: icmp_seq=69 ttl=49 time=280.895 ms
64 bytes from 98.139.183.24: icmp_seq=70 ttl=50 time=244.854 ms
64 bytes from 98.139.183.24: icmp_seq=71 ttl=50 time=320.841 ms
64 bytes from 98.139.183.24: icmp_seq=72 ttl=49 time=376.145 ms
64 bytes from 98.139.183.24: icmp_seq=73 ttl=50 time=282.468 ms
64 bytes from 98.139.183.24: icmp_seq=74 ttl=50 time=366.929 ms
64 bytes from 98.139.183.24: icmp_seq=75 ttl=50 time=283.931 ms
64 bytes from 98.139.183.24: icmp_seq=76 ttl=49 time=342.518 ms
64 bytes from 98.139.183.24: icmp_seq=77 ttl=50 time=293.322 ms
64 bytes from 98.139.183.24: icmp_seq=78 ttl=49 time=282.632 ms
64 bytes from 98.139.183.24: icmp_seq=79 ttl=49 time=262.858 ms
64 bytes from 98.139.183.24: icmp_seq=80 ttl=49 time=358.864 ms
64 bytes from 98.139.183.24: icmp_seq=81 ttl=50 time=256.379 ms
64 bytes from 98.139.183.24: icmp_seq=82 ttl=49 time=336.988 ms

etc... etc.. etc..

i had to stop it or else it woulda gona on forever.

Ok Verizon, time to live up to that great customer service reputation of yours!

[dpmalito99]

here is my pingtest image

here is a clue, though.. if i restart my router, for the first minute or so, the ping is regular, 30 ms about.

its as if verizon fios is throttling me.. I HAVE been downloading a ton of big movies lately, but that shouldnt throttle me,, right FIOS?>

[smith6612]

Verizon doesn't throttle for a lot of data usage. Usually it's some sort of network problem that is causing issues.

Also, for Yahoo! You're pinging a server that has ICMP traffic on very low priority. Try pinging another site. See:

Tracing route to ir2.fp.vip.bf1.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     7 ms     7 ms     7 ms  10.41.15.1
  3     6 ms     7 ms     7 ms  P1-0.BFLONY-LCR-02.verizon-gni.net [130.81.195.222]
  4    25 ms    25 ms    26 ms  P11-0-0.BFLONY-LCR-01.verizon-gni.net [130.81.27.62]
  5    17 ms    17 ms    16 ms  so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
  6    31 ms    50 ms    48 ms  xe-3-1-1-0.RES-BB-RTR1.verizon-gni.net [130.81.23.155]
  7    25 ms    25 ms    25 ms  so-6-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.90]
  8    26 ms    26 ms    26 ms  130.81.15.110
  9    25 ms    25 ms    25 ms  ae-6.pat2.dce.yahoo.com [216.115.102.176]
 10    58 ms    51 ms    32 ms  ae-0.pat2.nyc.yahoo.com [216.115.100.93]
 11    57 ms    58 ms    57 ms  ae-2.pat2.bfz.yahoo.com [216.115.100.74]
 12    67 ms    43 ms    48 ms  ae-3.pat1.bfz.yahoo.com [216.115.97.199]
 13    56 ms    40 ms    41 ms  xe-8-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.91]
 14    42 ms    41 ms    54 ms  xe-8-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.91]
 15    51 ms    56 ms    52 ms  po-10.bas1-7-prd.bf1.yahoo.com [98.139.129.161]
 16    66 ms    67 ms    66 ms  po-16.bas1-7-prd.bf1.yahoo.com [98.139.130.1]
 17   196 ms   192 ms   170 ms  ir2.fp.vip.bf1.yahoo.com [98.139.183.24]

[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....