For a couple of weeks now I've been dealing with high ping issues (150ms+). Before this my ping would often spike so I figured it was just network congestion (house of 4 people), but after it being so high consistently for a couple of weeks, even when my laptop is the only device connected to the network, I finally bought an ethernet cable to figure out what's going on (posted ping results below). Not surprisingly the ping results are annoying due to gaming. Playing CS on 150+ ping is unbearable. There anything I can do to try and get this fixed?
Some more details:
- Internet bandwith is fine; 10 down 1 up (I know this sucks but it's what we've got)
tracert 8.8.8.8 results (on ethernet):
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 116 ms 128 ms 126 ms 2.127.238.151
3 123 ms 147 ms 134 ms be407.pr2.enlba.isp.sky.com [2.120.9.94]
4 151 ms 126 ms 102 ms 74.125.49.150
5 163 ms 108 ms 92 ms 74.125.242.97
6 133 ms 113 ms 104 ms 216.239.54.83
7 223 ms 115 ms 72 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
tracert 8.8.8.8 (on WiFi):
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms SkyRouter.Home [192.168.0.1]
2 161 ms 121 ms 106 ms 2.127.238.151
3 132 ms 124 ms 115 ms be407.pr2.enlba.isp.sky.com [2.120.9.94]
4 162 ms 167 ms 112 ms 74.125.49.150
5 127 ms 117 ms 124 ms 74.125.242.97
6 136 ms 124 ms 189 ms 216.239.54.83
7 164 ms 135 ms 115 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Other ping results (all on ethernet):
Pinging speedtest.net [2a04:4e42::731] with 32 bytes of data:
Reply from 2a04:4e42::731: time=122ms
Reply from 2a04:4e42::731: time=104ms
Reply from 2a04:4e42::731: time=237ms
Reply from 2a04:4e42::731: time=110ms
Ping statistics for 2a04:4e42::731:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 237ms, Average = 143ms
Pinging google.co.uk [2a00:1450:4009:813::2003] with 32 bytes of data:
Reply from 2a00:1450:4009:813::2003: time=109ms
Reply from 2a00:1450:4009:813::2003: time=169ms
Reply from 2a00:1450:4009:813::2003: time=132ms
Reply from 2a00:1450:4009:813::2003: time=127ms
Ping statistics for 2a00:1450:4009:813::2003:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 169ms, Average = 134ms
Pinging jolt.co.uk [104.155.45.104] with 32 bytes of data:
Reply from 104.155.45.104: bytes=32 time=124ms TTL=58
Reply from 104.155.45.104: bytes=32 time=240ms TTL=58
Reply from 104.155.45.104: bytes=32 time=123ms TTL=58
Reply from 104.155.45.104: bytes=32 time=112ms TTL=58
Ping statistics for 104.155.45.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 240ms, Average = 149ms
Some more details:
- Internet bandwith is fine; 10 down 1 up (I know this sucks but it's what we've got)
tracert 8.8.8.8 results (on ethernet):
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 116 ms 128 ms 126 ms 2.127.238.151
3 123 ms 147 ms 134 ms be407.pr2.enlba.isp.sky.com [2.120.9.94]
4 151 ms 126 ms 102 ms 74.125.49.150
5 163 ms 108 ms 92 ms 74.125.242.97
6 133 ms 113 ms 104 ms 216.239.54.83
7 223 ms 115 ms 72 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
tracert 8.8.8.8 (on WiFi):
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms SkyRouter.Home [192.168.0.1]
2 161 ms 121 ms 106 ms 2.127.238.151
3 132 ms 124 ms 115 ms be407.pr2.enlba.isp.sky.com [2.120.9.94]
4 162 ms 167 ms 112 ms 74.125.49.150
5 127 ms 117 ms 124 ms 74.125.242.97
6 136 ms 124 ms 189 ms 216.239.54.83
7 164 ms 135 ms 115 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Other ping results (all on ethernet):
Pinging speedtest.net [2a04:4e42::731] with 32 bytes of data:
Reply from 2a04:4e42::731: time=122ms
Reply from 2a04:4e42::731: time=104ms
Reply from 2a04:4e42::731: time=237ms
Reply from 2a04:4e42::731: time=110ms
Ping statistics for 2a04:4e42::731:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 237ms, Average = 143ms
Pinging google.co.uk [2a00:1450:4009:813::2003] with 32 bytes of data:
Reply from 2a00:1450:4009:813::2003: time=109ms
Reply from 2a00:1450:4009:813::2003: time=169ms
Reply from 2a00:1450:4009:813::2003: time=132ms
Reply from 2a00:1450:4009:813::2003: time=127ms
Ping statistics for 2a00:1450:4009:813::2003:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 169ms, Average = 134ms
Pinging jolt.co.uk [104.155.45.104] with 32 bytes of data:
Reply from 104.155.45.104: bytes=32 time=124ms TTL=58
Reply from 104.155.45.104: bytes=32 time=240ms TTL=58
Reply from 104.155.45.104: bytes=32 time=123ms TTL=58
Reply from 104.155.45.104: bytes=32 time=112ms TTL=58
Ping statistics for 104.155.45.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 240ms, Average = 149ms