[SOLVED] Issues With Ping

[benjerson]

Afternoon Toms Hardware, I am in a bind. I have Frontier DSL and I have been having ping issues for the past 2 weeks where it makes it almost unplayable for anything online. My ping goes anywhere from 24 - 400 at the highest, and I havent been able to diagnose the issue. Mainly when I start lagging, I end up at 100 - 400 for at least 20 minutes before it goes down again. It usually stays at around 24, then goes right back to 100 - 400 for another 20 minutes. I have tried looking for devices on my network that are causing this issue, and I have not found my ping going any lower. On top of that, we are pretty rural, so frontier is the only ISP that comes out to us.

I called Frontier to fix the issue, and they replaced a connector. After that fix, it appears that nothing has changed whatsoever. On the contrary, I tried just unplugging everything on my network, but now I am anywhere between 24 - 300 Ping, But it seems to hang out around 23 - 100. I just dont know where to go from here, because there has been days where nobody is here, yet it is still lagging. I also have times where I play perfectly fine. I usually got around 24 ping way back when I was playing games too.

Reply from 8.8.8.8: bytes=32 time=40ms TTL=114
Reply from 8.8.8.8: bytes=32 time=58ms TTL=114
Reply from 8.8.8.8: bytes=32 time=56ms TTL=114
Reply from 8.8.8.8: bytes=32 time=46ms TTL=114
Reply from 8.8.8.8: bytes=32 time=76ms TTL=114
Reply from 8.8.8.8: bytes=32 time=49ms TTL=114
Reply from 8.8.8.8: bytes=32 time=55ms TTL=114
Reply from 8.8.8.8: bytes=32 time=24ms TTL=114
Reply from 8.8.8.8: bytes=32 time=83ms TTL=114
Reply from 8.8.8.8: bytes=32 time=55ms TTL=114
Reply from 8.8.8.8: bytes=32 time=64ms TTL=114
Reply from 8.8.8.8: bytes=32 time=275ms TTL=114
Reply from 8.8.8.8: bytes=32 time=24ms TTL=114
Reply from 8.8.8.8: bytes=32 time=31ms TTL=114
Reply from 8.8.8.8: bytes=32 time=23ms TTL=114

This is what I see when I test my latency before I try to play games. Specifically league of legends, if that makes any difference.


<1 ms <1 ms <1 ms
2 1 ms <1 ms <1 ms
3 49 ms 33 ms 27 ms
4 40 ms 41 ms 47 ms
5 * * * Request timed out.
6 44 ms 45 ms 70 ms
7 24 ms 47 ms 24 ms
8 47 ms 27 ms 31 ms
9 27 ms 40 ms 39 ms

(note that I deleted the IPs for privacy sake.)

Here is a tracert if it makes any difference.

The Question I would like to have answered is: Is there any way for me to fix this? and if there is, what steps can I take to fix this issue? Thanks!

 

[bill001g]

The Ip in the tracert are public router IP. Maybe the ip in hop 2 or hop 3 would give a idea what city you live in but trace does not give out your IP.

Your problem is ping does not tell you why and tracert does not run long enough to see the problem.

You need to run ping commands to the various hops yourself. Normally say start with hop 1 and hop 2. In your case they are both so low I suspect you have 2 routers in your house. I would do hop 1 and hop 3 in your case. Hop 3 represent the connection to your house. Hop 1 should be your router and you should never see any major variations.

Pings spikes are going to be hard to get the ISP to fix. You would much rather have random ping loss because that represent some failure. Ping spikes many times is traffic related. Some connection is overloaded. This is harder for a ISP to fix because if mean they must upgrade something in their network.

In any case your first step is to find the problem so you know what your options are.