Really bad ping

Toggle sidebar Toggle sidebar
S

ShadowClax1_1

Commendable
Sep 23, 2016
7
0
1,510
Hey guys, so I recently upgraded my internet thinking that it would help, and it definitely has. My original ping range before i upgraded speeds was 200-300ms but now its ranging from 50-90ms. Which is tons better, but i have no idea as to why its fluctuating so badly other than the fact that I have a secondary router that's acting as an access point for the isp's router? But i need it to boost the internet. (if this matters, I did the speedtest thing and got 15ms ping, so... kinda confused)
 
Solution
BadActor
Did you contact your ISP's support to see if they might have a problem on their end? It's doubtful since you say it will work after a restart, but may be worth a try. I'm thinking your wifi adapter might be the problem at this point. You might go into Control Panel\Network and Internet\Network Connections then right click properties of the adapter. Click Configure then the Power Management tab. Uncheck to turn off the device to save power. Click the Power Icon in the tray, then More Power Options, and click on Hide Additional Plans, then select High performance.

Make sure your adapter driver is up to date, too. If these don't do the trick, you might want to pick up a cheap USB wifi adapter...
Sort by date Sort by votes
BadActor

BadActor

Expert
Ambassador
Oct 31, 2015
8,749
1
54,965
Ping is mostly related to your ISP and the distance from the server your trying to reach. You can run Traceroute to get a better idea of where the latency is occurring.

http://www.howtogeek.com/134132/how-to-use-traceroute-to-identify-network-problems/
 
Upvote 0 Downvote
S

ShadowClax1_1

Commendable
Sep 23, 2016
7
0
1,510
I did try it, and i was super confused. it changed alot so i really can't tell...
3 153 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 26 ms 25 ms 26 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 73 ms 94 ms 73 ms 67.134.166.226
6 204 ms 26 ms 26 ms 216.239.42.247
7 28 ms 26 ms 26 ms 216.239.50.179
8 277 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 355 ms 1 ms 1 ms 192.168.0.1
2 19 ms 95 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 26 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 64 ms 64 ms 65 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 98 ms 26 ms 26 ms 216.239.50.179
8 26 ms 26 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 446 ms 1 ms 1 ms 192.168.0.1
2 16 ms 15 ms 17 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 15 ms 15 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 25 ms 25 ms 34 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 36 ms 33 ms 33 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 229 ms 27 ms 26 ms 216.239.50.179
8 26 ms 26 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 60 ms 16 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 357 ms 16 ms 17 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 308 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 25 ms 26 ms 25 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 26 ms 26 ms 27 ms 216.239.50.179
8 27 ms 27 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 36 ms 15 ms 17 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 381 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 322 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 25 ms 25 ms 26 ms 67.134.166.226
6 29 ms 26 ms 26 ms 216.239.42.247
7 28 ms 26 ms 26 ms 216.239.50.179
8 226 ms 25 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 31 ms 1 ms 1 ms 192.168.0.1
2 17 ms 19 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 16 ms 25 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 25 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 25 ms 27 ms 26 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 227 ms 25 ms 26 ms 216.239.50.179
8 26 ms 25 ms 28 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 160 ms 1 ms 1 ms 192.168.0.1
2 17 ms 16 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 17 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 325 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 357 ms 30 ms 27 ms 67.134.166.226
6 25 ms 26 ms 26 ms 216.239.42.247
7 278 ms 26 ms 26 ms 216.239.50.179
8 26 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 16 ms 16 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 16 ms 18 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 25 ms 26 ms 28 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 76 ms 68 ms 70 ms 67.134.166.226
6 327 ms 30 ms 31 ms 216.239.42.247
7 26 ms 26 ms 26 ms 216.239.50.179
8 28 ms 26 ms 25 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 2 ms 3 ms 1 ms 192.168.0.1
2 16 ms 20 ms 15 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 376 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 388 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 354 ms 68 ms 68 ms 67.134.166.226
6 27 ms 26 ms 26 ms 216.239.42.247
7 26 ms 27 ms 26 ms 216.239.50.179
8 502 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 392 ms 1 ms 1 ms 192.168.0.1
2 17 ms 17 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 308 ms 25 ms 27 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 354 ms 26 ms 26 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 217 ms 26 ms 26 ms 216.239.50.179
8 26 ms 27 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 464 ms 17 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 372 ms 16 ms 15 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 390 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 27 ms 27 ms 28 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 28 ms 26 ms 26 ms 216.239.50.179
8 160 ms 28 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 216 ms 16 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 327 ms 20 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 25 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 26 ms 25 ms 25 ms 67.134.166.226
6 227 ms 31 ms 26 ms 216.239.42.247
7 30 ms 27 ms 26 ms 216.239.50.179
8 271 ms 26 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 381 ms 16 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 79 ms 19 ms 15 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 26 ms 25 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 41 ms 39 ms 40 ms 67.134.166.226
6 30 ms 26 ms 28 ms 216.239.42.247
7 26 ms 26 ms 26 ms 216.239.50.179
8 186 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 402 ms 1 ms 1 ms 192.168.0.1
2 16 ms 18 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 15 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 335 ms 26 ms 26 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 370 ms 29 ms 29 ms 67.134.166.226
6 26 ms 26 ms 30 ms 216.239.42.247
7 217 ms 27 ms 25 ms 216.239.50.179
8 26 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 17 ms 17 ms 16 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 17 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 26 ms 25 ms 26 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 67 ms 66 ms 63 ms 67.134.166.226
6 31 ms 26 ms 28 ms 216.239.42.247
7 27 ms 25 ms 26 ms 216.239.50.179
8 26 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 59 ms 17 ms 17 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 362 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 365 ms 27 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 74 ms 76 ms 76 ms 67.134.166.226
6 496 ms 26 ms 26 ms 216.239.42.247
7 26 ms 26 ms 26 ms 216.239.50.179
8 160 ms 26 ms 29 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 259 ms 1 ms 1 ms 192.168.0.1
2 16 ms 18 ms 19 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 17 ms 17 ms 15 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 321 ms 25 ms 26 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 399 ms 64 ms 64 ms 67.134.166.226
6 26 ms 26 ms 26 ms 216.239.42.247
7 188 ms 26 ms 26 ms 216.239.50.179
8 28 ms 26 ms 27 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 17 ms 21 ms 21 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 16 ms 16 ms 17 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 25 ms 28 ms 25 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 67 ms 68 ms 63 ms 67.134.166.226
6 385 ms 26 ms 29 ms 216.239.42.247
7 26 ms 26 ms 26 ms 216.239.50.179
8 26 ms 26 ms 26 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>

C:\WINDOWS\system32>tracert 8.8.8.8

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 192.168.0.1
2 16 ms 16 ms 19 ms 207-108-176-14.slkc.qwest.net [207.108.176.14]
3 397 ms 16 ms 16 ms 207-108-177-105.slkc.qwest.net [207.108.177.105]
4 387 ms 39 ms 30 ms dvr-edge-13.inet.qwest.net [67.14.24.93]
5 324 ms 59 ms 59 ms 67.134.166.226
6 26 ms 27 ms 26 ms 216.239.42.249
7 26 ms 26 ms 26 ms 209.85.242.211
8 364 ms 28 ms 33 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
Upvote 0 Downvote
S

ShadowClax1_1

Commendable
Sep 23, 2016
7
0
1,510
I'm connecting wirelessly from my wifi card. and then through what i said on my original post. I thought i fixed it this morning, since it worked well for a while. but then i got home now and it didnt work.
 
Upvote 0 Downvote
BadActor

BadActor

Expert
Ambassador
Oct 31, 2015
8,749
1
54,965
Try changing the channel on your router. You can also try changing your DNS server to one with lower latency. One other thing you can do is to check your MTU and adjust it if necessary. I've provided some links on how to do those things. If these steps fail to help, you probably need to contact your ISP about the problem and see if they can offer any help on their end. It's possible your adapter or router may be the cause, but I would do these things first to see if you have any improvement.

http://www.extremetech.com/computing/179344-how-to-boost-your-wifi-speed-by-choosing-the-right-channel

http://www.tomshardware.com/faq/id-1890089/find-fastest-dns-server-configure-windows.html

http://www.richard-slater.co.uk/archives/2009/10/23/change-your-mtu-under-vista-windows-7-or-windows-8/
 
Upvote 0 Downvote
BadActor

BadActor

Expert
Ambassador
Oct 31, 2015
8,749
1
54,965
Did you contact your ISP's support to see if they might have a problem on their end? It's doubtful since you say it will work after a restart, but may be worth a try. I'm thinking your wifi adapter might be the problem at this point. You might go into Control Panel\Network and Internet\Network Connections then right click properties of the adapter. Click Configure then the Power Management tab. Uncheck to turn off the device to save power. Click the Power Icon in the tray, then More Power Options, and click on Hide Additional Plans, then select High performance.

Make sure your adapter driver is up to date, too. If these don't do the trick, you might want to pick up a cheap USB wifi adapter.

https://uk.pcpartpicker.com/product/2sdqqs/tp-link-wireless-network-card-tlwn821n
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom