Very High Latency

[macbrian97]

I am frequently getting ping spikes. When the latency is normal, I have amazing ping, but it usually doesn't last very long. This is my ping currently..

Pinging google.com [173.194.40.41] with 32 bytes of Reply from 173.194.40.41: bytes=32 time=408ms TTL=52Reply from 173.194.40.41: bytes=32 time=397ms TTL=52Reply from 173.194.40.41: bytes=32 time=442ms TTL=52Reply from 173.194.40.41: bytes=32 time=459ms TTL=52Reply from 173.194.40.41: bytes=32 time=496ms TTL=52Reply from 173.194.40.41: bytes=32 time=508ms TTL=52Reply from 173.194.40.41: bytes=32 time=505ms TTL=52Reply from 173.194.40.41: bytes=32 time=298ms TTL=52Reply from 173.194.40.41: bytes=32 time=540ms TTL=52Reply from 173.194.40.41: bytes=32 time=579ms TTL=52Reply from 173.194.40.41: bytes=32 time=598ms TTL=52Reply from 173.194.40.41: bytes=32 time=618ms TTL=52Reply from 173.194.40.41: bytes=32 time=480ms TTL=52Reply from 173.194.40.41: bytes=32 time=615ms TTL=52Reply from 173.194.40.41: bytes=32 time=643ms TTL=52Reply from 173.194.40.41: bytes=32 time=674ms TTL=52Reply from 173.194.40.41: bytes=32 time=676ms TTL=52Reply from 173.194.40.41: bytes=32 time=679ms TTL=52Reply from 173.194.40.41: bytes=32 time=432ms TTL=52

Pinging 192.168.1.1 with 32 bytes of data&colon; Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

I have an Actiontec GT784WNV Modem on Interleaved with

Broadband Mode Setting:	ADSL
Broadband Negotiated Mode:	G.DMT
Connection Status:	CONNECTED
Downstream Speed:	3360 Kbps
Upstream Speed:	864 Kbps

SNR Downstream :	27 dB
SNR Upstream :	16 dB
Attenuation Downstream :	24 dB
Attenuation Upstream :	15 dB
Power Downstream	5.8 dBm
Power Upstream	11.9 dBm

Please help because this is extremely annoying for gaming.

[smith6612]

Just to be sure, have you validated that this latency is present with no program or device on your network generating additional traffic? Latency like this could be caused by saturating the download or the upload, or both.

Do you know of any neighbors with Verizon DSL seeing the same issue?

Finally, let's get you on FastPath for lower latency. A line like that should be at a higher speed and not be sitting on Interleaved mode. It should be on 7.1Mbps + FastPath (FastPath drops your latency to around 6ms).

[macbrian97]

Yes.

And I'm not sure if any of my neighbors with DSL have this issue.

This is what it's looking light right now:

Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=42ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=56ms TTL=46 Reply from 74.125.21.100: bytes=32 time=989ms TTL=46 Reply from 74.125.21.100: bytes=32 time=978ms TTL=46 Reply from 74.125.21.100: bytes=32 time=1247ms TTL=46 Reply from 74.125.21.100: bytes=32 time=1295ms TTL=46 Reply from 74.125.21.100: bytes=32 time=1300ms TTL=46 Reply from 74.125.21.100: bytes=32 time=1308ms TTL=46 Reply from 74.125.21.100: bytes=32 time=1033ms TTL=46 Reply from 74.125.21.100: bytes=32 time=751ms TTL=46 Reply from 74.125.21.100: bytes=32 time=722ms TTL=46 Reply from 74.125.21.100: bytes=32 time=508ms TTL=46 Reply from 74.125.21.100: bytes=32 time=521ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=42ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46 Reply from 74.125.21.100: bytes=32 time=43ms TTL=46

[macbrian97]

 How can I go about changing to FastPath?

[smith6612 · Accepted solution]

To get FastPath, I recommend asking the Verizon Direct forum over at DSLReports. They've been pretty good at giving this mode to you. Or, you could consider giving Verizon a call and asking. Sometimes you'll need to mention "Gaming" or "Low latency" or "No Error correction" for the agent to know about what you're looking to do with the line. 

Assuming your connection is not being used when you're seeing latency like that, we should have Verizon ensure that there isn't a congestion problem taking place. Temporary congestion at the DSLAM, or at the edge router can cause the high latency you're seeing.

Lastly, please ask Verizon to increase your connection speed to 7.1Mbps. It is free of charge, and if anything only requires the qualification database for your home to be updated to reflect 7.1Mbps.

Verizon Direct fourm: https://secure.dslreports.com/forum/vzdirect

[macbrian97]

Thank you very much for your help!

I was able to get FastPath, but they said they wouldn't be able to increase my connection speed to 7.1 Mbps

[smith6612]

That happens. I would find out why. In some areas it's a capacity issue (For example, your DSLAM is fed by a DS3 rather than OC-3 or better). In other areas there's just no reason for the limit.

Has the latency been any better? Did Verizon find any signs of congestion?