High Ping on Fios - Need help.

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

[tns]

Actually I had serious problem in the past with speedtest when it picks Secaucus NY.  Do you get same results when you pick a different server.

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

[Tsuki]

Hi Adam,

Thanks for the reply.  I actually got a call back on Tuesday  and a technician came to check my ONT on Wednesday.  The technician came over, check a few things and called support to escalate the issue.  I'm waiting to hear back from tier 2 support.

Thanks again.

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