Unstable/High ping during peak hours, any advice welcome.

[Canadian_Anders]

I've recently moved into a new house this month (university student starting another term) and one thing that has been bothering me to no end is the latency issues I've been having, especially at peak hours for any and all games (all steam games) that I've been playing on my desktop.

Download/upload speed does not seem to be the problem, just the ping. I am connected via ethernet cord to the router which is connected to the modem. Internet is provided through cable.

I've been reading about doing ping and tracerts in the command prompt and have noticed the ping will spike somewhat frequently and often very high (300-500). Here is an example:

Pinging google.com [172.217.0.174] with 32 bytes of data:
Reply from 172.217.0.174: bytes=32 time=21ms TTL=57
Reply from 172.217.0.174: bytes=32 time=16ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=27ms TTL=57
Reply from 172.217.0.174: bytes=32 time=20ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=19ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=23ms TTL=57
Reply from 172.217.0.174: bytes=32 time=69ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=43ms TTL=57
Reply from 172.217.0.174: bytes=32 time=48ms TTL=57
Reply from 172.217.0.174: bytes=32 time=15ms TTL=57
Reply from 172.217.0.174: bytes=32 time=29ms TTL=57
Reply from 172.217.0.174: bytes=32 time=459ms TTL=57
Reply from 172.217.0.174: bytes=32 time=252ms TTL=57
Reply from 172.217.0.174: bytes=32 time=21ms TTL=57
Reply from 172.217.0.174: bytes=32 time=234ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=737ms TTL=57
Reply from 172.217.0.174: bytes=32 time=630ms TTL=57
Reply from 172.217.0.174: bytes=32 time=15ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=15ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=76ms TTL=57
Reply from 172.217.0.174: bytes=32 time=17ms TTL=57
Reply from 172.217.0.174: bytes=32 time=12ms TTL=57
Reply from 172.217.0.174: bytes=32 time=72ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=11ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=17ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=15ms TTL=57
Reply from 172.217.0.174: bytes=32 time=18ms TTL=57
Reply from 172.217.0.174: bytes=32 time=8ms TTL=57
Reply from 172.217.0.174: bytes=32 time=26ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=12ms TTL=57
Reply from 172.217.0.174: bytes=32 time=9ms TTL=57
Reply from 172.217.0.174: bytes=32 time=11ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=13ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57
Reply from 172.217.0.174: bytes=32 time=41ms TTL=57
Reply from 172.217.0.174: bytes=32 time=14ms TTL=57


Any tips for helping out a fellow computer user? I'm happy to answer any questions that might help solve the issue.

Thanks!

 

[bill001g]

You need to run tracert and then ping each hop in the trace to find where the problem starts. When you ping the end device it can be anything from your router, your isp, the remote device's isp.

 

[Canadian_Anders]

Hi Bill,

So this is my tracert results:


C:\WINDOWS\system32>tracert google.com

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

1 747 ms 323 ms 289 ms 67.231.221.202
2 * * * Request timed out.
3 291 ms 459 ms 770 ms xe-1-1-1-1112-agg01-tor.teksavvy.com [198.48.250.57]
4 615 ms 736 ms 709 ms ae1-2170-bdr01-tor.teksavvy.com [192.171.59.101]
5 686 ms 769 ms 540 ms 72.14.212.134
6 263 ms 425 ms 483 ms 216.239.47.114
7 173 ms 188 ms 150 ms 209.85.250.207
8 666 ms 351 ms 206 ms yyz08s13-in-f142.1e100.net [172.217.3.142]

Trace complete.


First I tried pinging my own router which was <1 ms and then tried out the hops above:
C:\WINDOWS\system32>ping -n 15 67.231.221.202

Pinging 67.231.221.202 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 67.231.221.202:
Packets: Sent = 15, Received = 0, Lost = 15 (100% loss),


Pinging 198.48.250.57 with 32 bytes of data:
Reply from 198.48.250.57: bytes=32 time=126ms TTL=62
Reply from 198.48.250.57: bytes=32 time=171ms TTL=62
Reply from 198.48.250.57: bytes=32 time=153ms TTL=62
Reply from 198.48.250.57: bytes=32 time=338ms TTL=62
Reply from 198.48.250.57: bytes=32 time=255ms TTL=62
Reply from 198.48.250.57: bytes=32 time=174ms TTL=62
Reply from 198.48.250.57: bytes=32 time=346ms TTL=62
Reply from 198.48.250.57: bytes=32 time=234ms TTL=62
Reply from 198.48.250.57: bytes=32 time=166ms TTL=62
Reply from 198.48.250.57: bytes=32 time=225ms TTL=62
Reply from 198.48.250.57: bytes=32 time=361ms TTL=62
Reply from 198.48.250.57: bytes=32 time=259ms TTL=62
Reply from 198.48.250.57: bytes=32 time=316ms TTL=62
Reply from 198.48.250.57: bytes=32 time=128ms TTL=62
Reply from 198.48.250.57: bytes=32 time=312ms TTL=62

Ping statistics for 198.48.250.57:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 361ms, Average = 237ms

Pinging 192.171.59.101 with 32 bytes of data:
Reply from 192.171.59.101: bytes=32 time=311ms TTL=61
Reply from 192.171.59.101: bytes=32 time=290ms TTL=61
Reply from 192.171.59.101: bytes=32 time=340ms TTL=61
Reply from 192.171.59.101: bytes=32 time=224ms TTL=61
Reply from 192.171.59.101: bytes=32 time=190ms TTL=61
Reply from 192.171.59.101: bytes=32 time=460ms TTL=61
Reply from 192.171.59.101: bytes=32 time=353ms TTL=61
Reply from 192.171.59.101: bytes=32 time=311ms TTL=61
Reply from 192.171.59.101: bytes=32 time=233ms TTL=61
Reply from 192.171.59.101: bytes=32 time=353ms TTL=61
Reply from 192.171.59.101: bytes=32 time=470ms TTL=61
Reply from 192.171.59.101: bytes=32 time=348ms TTL=61
Reply from 192.171.59.101: bytes=32 time=164ms TTL=61
Reply from 192.171.59.101: bytes=32 time=195ms TTL=61
Reply from 192.171.59.101: bytes=32 time=436ms TTL=61

Ping statistics for 192.171.59.101:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 470ms, Average = 311ms

Pinging 72.14.212.134 with 32 bytes of data:
Reply from 72.14.212.134: bytes=32 time=823ms TTL=60
Reply from 72.14.212.134: bytes=32 time=819ms TTL=60
Reply from 72.14.212.134: bytes=32 time=795ms TTL=60
Reply from 72.14.212.134: bytes=32 time=950ms TTL=60
Reply from 72.14.212.134: bytes=32 time=835ms TTL=60
Reply from 72.14.212.134: bytes=32 time=742ms TTL=60
Reply from 72.14.212.134: bytes=32 time=746ms TTL=60
Reply from 72.14.212.134: bytes=32 time=777ms TTL=60
Reply from 72.14.212.134: bytes=32 time=790ms TTL=60
Reply from 72.14.212.134: bytes=32 time=813ms TTL=60
Reply from 72.14.212.134: bytes=32 time=908ms TTL=60
Reply from 72.14.212.134: bytes=32 time=866ms TTL=60
Reply from 72.14.212.134: bytes=32 time=917ms TTL=60
Reply from 72.14.212.134: bytes=32 time=807ms TTL=60
Reply from 72.14.212.134: bytes=32 time=750ms TTL=60

Ping statistics for 72.14.212.134:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 742ms, Maximum = 950ms, Average = 822ms

Pinging 216.239.47.114 with 32 bytes of data:
Reply from 216.239.47.114: bytes=32 time=873ms TTL=59
Reply from 216.239.47.114: bytes=32 time=739ms TTL=59
Reply from 216.239.47.114: bytes=32 time=732ms TTL=59
Reply from 216.239.47.114: bytes=32 time=758ms TTL=59
Reply from 216.239.47.114: bytes=32 time=683ms TTL=59
Reply from 216.239.47.114: bytes=32 time=753ms TTL=59
Reply from 216.239.47.114: bytes=32 time=656ms TTL=59
Reply from 216.239.47.114: bytes=32 time=337ms TTL=59
Reply from 216.239.47.114: bytes=32 time=784ms TTL=59
Reply from 216.239.47.114: bytes=32 time=750ms TTL=59
Reply from 216.239.47.114: bytes=32 time=733ms TTL=59
Reply from 216.239.47.114: bytes=32 time=498ms TTL=59
Reply from 216.239.47.114: bytes=32 time=359ms TTL=59
Reply from 216.239.47.114: bytes=32 time=205ms TTL=59
Reply from 216.239.47.114: bytes=32 time=545ms TTL=59

Ping statistics for 216.239.47.114:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 205ms, Maximum = 873ms, Average = 627ms

Pinging 209.85.250.207 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.85.250.207:
Packets: Sent = 11, Received = 0, Lost = 11 (100% loss),
Control-C
^C

Pinging 172.217.3.142 with 32 bytes of data:
Reply from 172.217.3.142: bytes=32 time=790ms TTL=57
Reply from 172.217.3.142: bytes=32 time=653ms TTL=57
Reply from 172.217.3.142: bytes=32 time=577ms TTL=57
Reply from 172.217.3.142: bytes=32 time=202ms TTL=57
Reply from 172.217.3.142: bytes=32 time=135ms TTL=57
Reply from 172.217.3.142: bytes=32 time=500ms TTL=57
Reply from 172.217.3.142: bytes=32 time=233ms TTL=57
Reply from 172.217.3.142: bytes=32 time=146ms TTL=57
Reply from 172.217.3.142: bytes=32 time=639ms TTL=57
Reply from 172.217.3.142: bytes=32 time=193ms TTL=57
Reply from 172.217.3.142: bytes=32 time=99ms TTL=57
Reply from 172.217.3.142: bytes=32 time=569ms TTL=57
Reply from 172.217.3.142: bytes=32 time=269ms TTL=57
Reply from 172.217.3.142: bytes=32 time=153ms TTL=57
Reply from 172.217.3.142: bytes=32 time=398ms TTL=57

Ping statistics for 172.217.3.142:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 790ms, Average = 370ms




Extra note: I had today off and played games from around 2-5 pm but around 5, my ping started increasing drastically so I'm not sure if this problem has something to do with traffic and if so, is there a way around it?

Thanks!

 

[bill001g]

That is strange. Hop 1 has huge delays. I though you said you had a router. Normally your router would have private IP. Hop 1 is public ip. This is normally what a tracert looks like with only a modem.

Hard to say. If the device is located on your premise then it could have a problem. If it is remote at the ISP office you may want to ask them why you see such high delays. It could be a issue with the actual connection or it could be too many people on some shared connection.

 

[Canadian_Anders]

I am connected to a router (D-Link DIR-880L) via ethernet cable which is connected to a modem through another cable.

The default D-Link IP is 192.168.0.1 and when I ping that, I get <1 ms. Is the first hop something other than the router in that case?

 

[bill001g]

When you run tracert you should see 192.168.0.1 as hop1 but you do not. It is extremely strange.