Question Ping spikes Windows 10 fresh install

Nov 11, 2022
2
0
10
0
Hey,
I'm having some weird ping spikes when trying to ping google for example. These spikes cause noticable rubberbanding on games.
Below you can see my ping to google.com is not stable at all going from low 15s to 85+ randomly. All this is happening when no programs are running.
The ping spikes started when I formatted my PC and did a fresh clean Windows 10 install.

I've tried the following:
Reinstall Windows 10
Updated Mobo LAN drivers
Flushed DNS

I'm using cable to router (5g) wireless connection:
Download 150-200mb/s
Upload 80mb/s

See the copy+paste of my cmd shared below:

PC to Router network ping(cable):

C:\Users\Joonas>ping -n 20 192.168.32.1

Pinging 192.168.32.1 with 32 bytes of data:
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=4ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=1ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64
Reply from 192.168.32.1: bytes=32 time=2ms TTL=64
Reply from 192.168.32.1: bytes=32 time=1ms TTL=64
Reply from 192.168.32.1: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.32.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms

Ping to google.com:

C:\Users\Joonas>ping -n 20 google.com

Pinging google.com [216.58.209.174] with 32 bytes of data:
Reply from 216.58.209.174: bytes=32 time=23ms TTL=59
Reply from 216.58.209.174: bytes=32 time=53ms TTL=59
Reply from 216.58.209.174: bytes=32 time=19ms TTL=59
Reply from 216.58.209.174: bytes=32 time=18ms TTL=59
Reply from 216.58.209.174: bytes=32 time=40ms TTL=59
Reply from 216.58.209.174: bytes=32 time=16ms TTL=59
Reply from 216.58.209.174: bytes=32 time=17ms TTL=59
Reply from 216.58.209.174: bytes=32 time=20ms TTL=59
Reply from 216.58.209.174: bytes=32 time=17ms TTL=59
Reply from 216.58.209.174: bytes=32 time=15ms TTL=59
Reply from 216.58.209.174: bytes=32 time=85ms TTL=59
Reply from 216.58.209.174: bytes=32 time=18ms TTL=59
Reply from 216.58.209.174: bytes=32 time=33ms TTL=59
Reply from 216.58.209.174: bytes=32 time=28ms TTL=59
Reply from 216.58.209.174: bytes=32 time=63ms TTL=59
Reply from 216.58.209.174: bytes=32 time=29ms TTL=59
Reply from 216.58.209.174: bytes=32 time=17ms TTL=59
Reply from 216.58.209.174: bytes=32 time=44ms TTL=59
Reply from 216.58.209.174: bytes=32 time=33ms TTL=59
Reply from 216.58.209.174: bytes=32 time=17ms TTL=59

Ping statistics for 216.58.209.174:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 85ms, Average = 30ms

Ping to my network adapter:

C:\Users\Joonas>ping -n 20 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
I doubt it is actually windows install related.

You have no control over traffic once it leaves you house. So even if you wanted to you can not make it worse or better.

If there was a problem with windows you would see in in the ping time to your router. Now I suppose it could be something on your machine is uploading or downloading and using bandwidth on your internet connection which will cause ping spikes.

In any case you want to ping the first ISP router......if you call the ISP they will just tell you it the google server having issues. Run a tracert 8.8.8.8. Then try to ping hop2 if it will respond.

I did notice that you are using mobile broadband. The latency spikes you see are about what you would expect on that type of connection. Any mobile broadband will be hit or miss if it runs well for games
 
Nov 11, 2022
2
0
10
0
I doubt it is actually windows install related.

You have no control over traffic once it leaves you house. So even if you wanted to you can not make it worse or better.

If there was a problem with windows you would see in in the ping time to your router. Now I suppose it could be something on your machine is uploading or downloading and using bandwidth on your internet connection which will cause ping spikes.

In any case you want to ping the first ISP router......if you call the ISP they will just tell you it the google server having issues. Run a tracert 8.8.8.8. Then try to ping hop2 if it will respond.

I did notice that you are using mobile broadband. The latency spikes you see are about what you would expect on that type of connection. Any mobile broadband will be hit or miss if it runs well for games
Hop2 was a timeout, no clue what that means

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

1 2 ms 1 ms 1 ms 192.168.32.1
2 * * * Request timed out.
3 38 ms 18 ms 18 ms 10.98.24.33
4 * 17 ms 15 ms 141.208.27.78
5 28 ms 16 ms 17 ms hls-b3-link.ip.twelve99.net [62.115.44.164]
6 35 ms 17 ms 17 ms 142.250.167.74
7 21 ms 25 ms 17 ms 142.251.53.61
8 28 ms 17 ms 17 ms 142.250.227.81
9 34 ms 16 ms 16 ms dns.google [8.8.8.8]

Trace complete.
 
Means they have the device designed to not respond to ping and trace.

Doesn't matter a real lot. Just ping hop 3 10.98.24.33

Your tracert is already showing small ping spikes. Not enough to matter but this is expected when you run a mobile broadband ISP. Tracert though does not send enough data to be of much value.

The normal test would run constant ping to your router 192.168.32.1 and in this case hop 3. 10.98.24.33. You would normally then call the ISP and show them there is no problem to your router but you get issues as soon as you use their network.

In general no ISP will fix latency issue, they barely promise some bandwidth amount. If you saw packet loss that they might fix but when you are on a mobile broadband it is likely they will not be able to do much because most the problems with mobile are other users sharing the same tower
 

ASK THE COMMUNITY