[SOLVED] Ping spikes to thousands.

[alpha dodo]

Ping keeps spiking to thousands every few seconds when gaming.

My laptop is a HP da-2017nx, 64-bit operating system
My router is Nokia G-240W-B.
My other laptop barely spikes and not to the extent that it reaches thousands.
Ethernet is not available.

I tried to run a ping test to google and this is the result:

Pinging google.com [216.58.198.78] with 32 bytes of data:
Reply from 216.239.38.120: bytes=32 time=54ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=2052ms TTL=117
Reply from 216.239.38.120: bytes=32 time=52ms TTL=117
Reply from 216.239.38.120: bytes=32 time=84ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=2006ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=52ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=52ms TTL=117
Reply from 216.239.38.120: bytes=32 time=2847ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117
Reply from 216.239.38.120: bytes=32 time=53ms TTL=117

My 2 tracert results:

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

1 4 ms 3 ms 4 ms dsldevice.lan [192.168.1.1]
2 5 ms 5 ms 8 ms 84.235.68.244
3 6 ms 7 ms 28 ms 10.188.197.58
4 7 ms 5 ms 5 ms 10.188.197.45
5 33 ms 7 ms 6 ms 10.188.199.38
6 1676 ms 53 ms 52 ms 74.125.147.190
7 53 ms 53 ms 53 ms 74.125.244.225
8 53 ms 53 ms 53 ms 172.253.67.157
9 52 ms 52 ms 52 ms mrs09s08-in-f14.1e100.net

Trace complete.

Tracing route to forcesafesearch.google.com
over a maximum of 30 hops:

1 4 ms 6 ms 3 ms dsldevice.lan [192.168.1.1]
2 2554 ms 5 ms 5 ms 84.235.68.244
3 5 ms 5 ms 5 ms 10.188.197.58
4 5 ms 5 ms 7 ms 10.188.197.45
5 7 ms 6 ms 6 ms 10.188.199.34
6 223 ms 112 ms 51 ms 74.125.147.0
7 173 ms 113 ms 291 ms 74.125.244.209
8 364 ms 290 ms 112 ms 72.14.232.157
9 53 ms 52 ms 56 ms any-in-2678.1e100.net

If you need more information just tell me.

 

[bill001g]

You need to do more detailed testing. The problem with tracert is it tests one node at a time. Even if it is say testing hop 4 if any hop before it has intermittent problems it will report it for the one it is currently doing the test not the previous ones.

You are better off opening a bunch of cmd windows and leave ping run to a couple different hops.

The most imporant ones are hop 1 and hop 2. Hop1 would represent some issue with the wifi in your case. If hop 1 is good but hop 2 is bad that generally means you have over utilization on your internet connection.

You can test other hops past that but it will be very hard to get the ISP to do anything and in some cases they can't if it is far into another ISP network.

 

[alpha dodo]

Thanks for responding. So I 'm guessing that hop1 is my device and hop 2 is my internet? I'm not really familiar with these things, the hops and stuff haha. If you could tell me what sites I can ping to I'll appreciate it. I'll keep you updated later.

Ran a ping test to 8.8.8.8 last night for like 10 mins or so. My current laptop is the only one lagging to 2000+ and it happens every several seconds, just like the info I sent above.
My old laptop's ping also lags but only to 100+s. Could it be my current device that's faulty?
I'm running a ping test to 8.8.8.8 again on both of my laptops and everything has been stable so far for 10 mins or so.
So I'm thinking that the spikes happen mostly at midnight.

I'll do more testing later tonight. Thanks again for responding.

 

[bill001g]

Hop 1 is your router and hop 2 is the ISP first router. Ping to 8.8.8.8 tells you little that you don't already know. There is some issue in the path between you and the 8.8.8.8 server.

If you machine is the only one affected it is likely some issue with the wifi in your machine. Hard to say if it is some issue with your wifi nic or maybe it is some issue with the placement of your machine in relationship to the router.

Really the only thing that you can try is to make sure you have the current wifi device drivers. You could try on ethernet to be sure it is not something else in the machine.

You could try a linux usb boot image that would allow you to test a different OS without damaging your windows install. It might show if there is a hardware nic problem.

 

[alpha dodo]

I see. I did another tracert to 8.8.8.8 and this time hop9 has the 2000 ping:

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

1 4 ms 3 ms 3 ms dsldevice.lan [192.168.1.1]
2 5 ms 6 ms 5 ms 84.235.68.244
3 7 ms 6 ms 5 ms 10.188.197.58
4 7 ms 11 ms 11 ms 10.188.197.43
5 6 ms 6 ms 5 ms 10.188.199.91
6 76 ms 76 ms 76 ms 72.14.213.158
7 71 ms 71 ms 71 ms 108.170.244.193
8 84 ms 77 ms 70 ms 142.250.224.197
9 2239 ms 73 ms 74 ms dns.google [8.8.8.8]

Trace complete.

I also remember I did a tracert like a few days ago and the first hop got the 2000 ping but I forgot to ss it.
As for the wifi device drivers. I did check and what confused me is how there are a lot of options, like WAN miniports and stuff. I expected it to be a bit simpler for my case. Idk I'm not really good at reading these.

And btw, my older laptop really barely spikes but it often gets "request timed out", like 2 times in a row.

 

[alpha dodo]

Do you think resetting my windows can solve the problem? or format it?

 

[alpha dodo]

Okay so I dug up my ethernet cable inside my closet, it was inside the wifi box the entire time. I'll test the ethernet out and see what I get.

 

[alpha dodo]

Okay so I tested out my ethernet cable and my ping is now stable.
I also noticed the 2k spikes only happen more frequently when I'm inside my room (at the other side of the house), maybe it could be a distance thing. It could be just a coincidence tho.

I guess I'll temporarily use my ethernet for gaming in the meantime while I figure this out.