Ping is getting really high after a new Windows 10 setup.
Ping is getting really high after a new Windows 10 setup.
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 don't think the issue is a Windows install. Once your traffic leaves your house, you can't control it. So even if you wanted to make things better or worse, you cannot. If there was a problem with the windows software, I would see slow ping times when pinging your router. Maybe something on your machine is uploading or downloading and using too much bandwidth on your internet connection, causing ping spikes. In any case, if you want to ping the first ISP router, just call them. They will tell you that the Google server is having issues. Run a tracert command for 8.8.8.8 and then try pinging hop2. It should respond. I noticed that you are using mobile broadband. The latency spikes you see sound normal for that type of connection. Any mobile broadband setup is hit or miss depending on whether it runs well for games.
Hop2 was a timeout, so I didn't know what that meant when I started looking up the address for dns.google. My trace to that DNS server took too long. The request hit its limit after 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
They have a gadget that doesn't reply to ping or trace calls. It really doesn't matter. Just try pinging 10.98.24.33 from three different places. Your tracert is already showing little spikes in traffic, not enough to worry about but this happens often when you run on mobile broadband internet. The tracert test isn't great because it sends too much data for a quick check. Usually, the right way is to ping your router (192.168.32.1) and see if hops 3 or 4 work well there. Then you call their support team to tell them your router works fine but things break the moment you use their network. In general, no ISP will fix a high latency problem easily; they mostly promise some amount of bandwidth speed. If they found packet loss, maybe that could be fixed, but when you're on mobile broadband, it's likely they can't fix much because most of the issues come from other people sharing the same tower.