Page 1 of 1
[HELP] ADSL High Ping, Packet Loss & Timeouts.
Posted: Mon Dec 12, 2016 12:21 pm
by Kaotik2k7
Hey guys,
Started having ping issues late last week, bought a new router to try alleviate the issue but it still exists, extremely frustrating. General browsing and downloading is all fine with roughly expected speeds but soon as I want to game, I get fluctuating pings and huge packet loss leading to disconnections. I've tried countless telnet commands and router tweaks, changed my Windows 10 drivers, used TCP optimizer, can't deal with it any longer, not been able to enjoy an online game in two weeks.
I know it's not bandwidth issues as I have kicked every device off and it's the same issue, also done ping tests from my mobile and it's the same problem.
Any advice much appreciated!
Thanks.
Posted: Tue Dec 13, 2016 9:58 am
by Philip
If you do a traceroute to the game server... Where does the ping increase noticeably ? Is it close to your location, first hop, or somewhere else along the trace ?
This can give you more info as to what is causing the ping spikes, so it can eventually be dealt with. Is it a Cable or DSL connection ? Have you looked at the signal levels to make sure they're in check ?
Posted: Tue Dec 13, 2016 6:18 pm
by Kaotik2k7
Hi Philip,
It's ADSL2+
I managed to reduce it somewhat and made more stable by changing the SNR on the router, it has reduced the latency and increased my bandwidth by a large amount but still get the random spikes however they drop off much more quickly now which equals less impact and managed to play some Battlefield 1 last night. The ping issue happens with any IP, bbc.co.uk is the usual one being from the UK and I get the same random high pings. I'm guessing this could be a line issue with too much noise since reducing it via the router has reduced this.
Here is a traceroute to the EUW League of Legends server:
Code: Select all
Tracing route to 104.160.141.3 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 25 ms 25 ms 23 ms 81.1.113.13
3 23 ms 24 ms 23 ms host-78-151-225-105.static.as13285.net [78.151.225.105]
4 28 ms 100 ms 24 ms host-78-151-229-4.as13285.net [78.151.229.4]
5 30 ms 29 ms 29 ms host-78-144-9-33.as13285.net [78.144.9.33]
6 35 ms 34 ms 34 ms host-78-144-11-235.as13285.net [78.144.11.235]
7 * * * Request timed out.
8 57 ms 66 ms 42 ms 104.160.141.3
Trace complete.
C:\Windows\system32>tracert 104.160.141.3
Tracing route to 104.160.141.3 over a maximum of 30 hops
1 15 ms 2 ms 1 ms 192.168.1.1
2 30 ms 31 ms 56 ms 81.1.113.13
3 26 ms 24 ms 23 ms host-78-151-225-105.static.as13285.net [78.151.225.105]
4 26 ms 24 ms 26 ms host-78-151-229-4.as13285.net [78.151.229.4]
5 242 ms * 30 ms host-78-144-9-33.as13285.net [78.144.9.33]
6 41 ms 35 ms 50 ms host-78-144-11-235.as13285.net [78.144.11.235]
7 38 ms 36 ms 37 ms 80.249.211.66
8 146 ms 124 ms 36 ms 104.160.141.3
Trace complete.
Thanks.
Posted: Wed Dec 14, 2016 8:39 am
by Philip
Good call on changing the SNR margin to improve stability.
20ms latency to to your ISP is average. Seems those remaining spikes are further down the line caused by their nodes (4th-5th hop).