Question Regular Ping Spikes to Home Router

[RainyTimes]

Hello,

I currently live in a house with 5 other people. I am connecting to the internet wirelessly from my desktop PC. The download speed from my PC is around 40-50MBPS. The ping to most websites is usually around a baseline of 5-25ms.

However, I am getting very regular ping spikes and packet loss every 10-15 seconds or so. Normally I wouldn't think too much of it and just assume that this is due to the number of people and devices connected to the router. However this is the case no matter the time of day (even when people are definitely asleep and other devices on the network are minimal).

This is what it looks like when I ping my router:

https://imgur.com/a/Qz0VdsM

This is the log from when I ping my router (spikes in bold)

Spoiler: CMD prompt pings to router

Pinging 192.168.68.1 with 32 bytes of data:
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=25ms TTL=64
Reply from 192.168.68.1: bytes=32 time=756ms TTL=64
Reply from 192.168.68.1: bytes=32 time=56ms TTL=64
Reply from 192.168.68.1: bytes=32 time=7ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=13ms TTL=64
Reply from 192.168.68.1: bytes=32 time=18ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=24ms TTL=64
Reply from 192.168.68.1: bytes=32 time=18ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=15ms TTL=64
Reply from 192.168.68.1: bytes=32 time=1640ms TTL=64
Reply from 192.168.68.1: bytes=32 time=13ms TTL=64
Reply from 192.168.68.1: bytes=32 time=23ms TTL=64
Reply from 192.168.68.1: bytes=32 time=17ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=15ms TTL=64
Reply from 192.168.68.1: bytes=32 time=18ms TTL=64
Reply from 192.168.68.1: bytes=32 time=7ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=23ms TTL=64
Reply from 192.168.68.1: bytes=32 time=907ms TTL=64
Reply from 192.168.68.1: bytes=32 time=9ms TTL=64
Reply from 192.168.68.1: bytes=32 time=9ms TTL=64
Reply from 192.168.68.1: bytes=32 time=9ms TTL=64
Reply from 192.168.68.1: bytes=32 time=18ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=4ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=18ms TTL=64
Reply from 192.168.68.1: bytes=32 time=11ms TTL=64
Reply from 192.168.68.1: bytes=32 time=14ms TTL=64
Reply from 192.168.68.1: bytes=32 time=16ms TTL=64
Reply from 192.168.68.1: bytes=32 time=854ms TTL=64
Reply from 192.168.68.1: bytes=32 time=70ms TTL=64
Reply from 192.168.68.1: bytes=32 time=15ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=43ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=9ms TTL=64
Reply from 192.168.68.1: bytes=32 time=7ms TTL=64
Reply from 192.168.68.1: bytes=32 time=15ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=11ms TTL=64
Reply from 192.168.68.1: bytes=32 time=777ms TTL=64
Reply from 192.168.68.1: bytes=32 time=31ms TTL=64
Reply from 192.168.68.1: bytes=32 time=32ms TTL=64
Reply from 192.168.68.1: bytes=32 time=15ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=17ms TTL=64
Reply from 192.168.68.1: bytes=32 time=17ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=9ms TTL=64
Reply from 192.168.68.1: bytes=32 time=16ms TTL=64
Reply from 192.168.68.1: bytes=32 time=42ms TTL=64
Reply from 192.168.68.1: bytes=32 time=1657ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=17ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=1139ms TTL=64
Reply from 192.168.68.1: bytes=32 time=19ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=5ms TTL=64
Reply from 192.168.68.1: bytes=32 time=14ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64
Reply from 192.168.68.1: bytes=32 time=13ms TTL=64
Reply from 192.168.68.1: bytes=32 time=13ms TTL=64
Reply from 192.168.68.1: bytes=32 time=3ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=1146ms TTL=64
Reply from 192.168.68.1: bytes=32 time=20ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=11ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=8ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=13ms TTL=64
Reply from 192.168.68.1: bytes=32 time=31ms TTL=64
Reply from 192.168.68.1: bytes=32 time=10ms TTL=64
Reply from 192.168.68.1: bytes=32 time=6ms TTL=64
Reply from 192.168.68.1: bytes=32 time=12ms TTL=64

Does anyone have any ideas what could be causing this?

 

[USAFRet]

Does anyone have any ideas what could be causing this?

In a word, WiFi.

Two words - WiFi congestion.

You, your roommates, your neighbors....

How to fix?
Anything that can be wired, should be wired.

 

[gggplaya]

40-50mbps for 5 people, sheesh. I would get a router with FQ_Codel or CAKE for sure, to make sure bandwidth is allocated in an equitable manner. So everyone gets what they need, but no one person is hogging it all.

But those ping spikes could be bad wifi as suggested, but it looks way to consistent for that. Perfect 1000ms spikes at even intervals. Even if people are sleeping, they could be downloading game updates on their game consoles or computers. Game consoles will typically update automatically in sleep mode overnight when set to do so. You can set the console to full off(power savings) or sleep mode where updates will happen.