How to Fix Game Lag Spikes

Step 1: Confirm it is the network with a continuous ping

Before changing anything, prove the spikes are coming from the network and not from the game, GPU, or CPU. Open a terminal and run a continuous ping to a public IP while you play: ping -t 1.1.1.1 on Windows, ping 1.1.1.1 on macOS/Linux. When you feel a spike in-game, glance at the ping window. If the ping jumped to a high number or showed a timeout at that instant, the network is the cause — continue below. If the ping stayed flat and low during the spike, the stutter is local to your machine, and network fixes will not help.

Step 2: Switch to a wired connection

Wi-Fi is the most common source of spikes, and going wired is the fastest way to either fix or rule it out. A momentary burst of interference, a weak-signal moment, or a band-steering handoff between 2.4 GHz and 5 GHz drops a few packets, and the game rubber-bands while it recovers. Plug into the router with Ethernet and play. If the spikes disappear, the problem is on the Wi-Fi side and the cleanest fix is to stay wired for gaming — see Ethernet vs Wi-Fi for gaming.

Step 3: Kill background traffic and test for bufferbloat

If spikes happen on Ethernet too, the next suspect is something else using the line. A game or OS update downloading, a cloud backup uploading, or another household member streaming 4K can saturate the connection in bursts and add latency to your game traffic. Stop background transfers — and check whether another device is the culprit using what is using your bandwidth. Then run a bufferbloat test: if your latency under load jumps from ~20 ms idle to 200 ms or more, bufferbloat is generating your spikes. The fix is enabling QoS or SQM on the router so the queue stays short under load.

Step 4: Reduce Wi-Fi interference if you must stay wireless

When Ethernet is not an option, attack the Wi-Fi causes directly. Move closer to the router or remove obstructions between you and it. Use the 5 GHz band, which is less congested and less prone to interference than 2.4 GHz. Switch to a less crowded channel — see the best Wi-Fi channel. And keep distance from interference sources like microwaves, cordless phones, and Bluetooth devices, which cause the brief packet loss that surfaces as spikes.

Step 5: Check for packet loss on the path

If the connection is wired, idle, and bufferbloat is clean, look at the route to the server. Run MTR for a few hundred cycles to a public IP or the game server's address. Loss that appears at a hop and persists all the way to the destination is real packet loss; a hop where the average latency suddenly balloons and stays high marks where delay is being added. Loss that appears at one middle hop but clears afterward is just that router de-prioritising pings — ignore it.

Step 6: Escalate to your ISP with evidence

When spikes persist on a wired connection with nothing else using the line and your local tests are clean, the problem is upstream. Capture an MTR report and a timestamped continuous-ping log during a spike, then contact your ISP. Recurring loss or latency at their first couple of hops is a line or node fault they are responsible for — and the logs make the ticket hard to brush off. The procedure in documenting the problem for your ISP walks through exactly what to send.

Frequently Asked Questions

Why do I get lag spikes when my ping is low?

Average ping being low does not prevent spikes. A spike is a brief moment when latency jumps or packets are lost — caused by Wi-Fi interference, bufferbloat from a background download, or loss on the path — and it disappears before a speed test or an averaged ping would notice. Run a continuous ping while playing to catch the spike as it happens.

Does a wired connection stop lag spikes?

It eliminates the most common cause. Wi-Fi is vulnerable to momentary interference and band-steering handoffs that drop a few packets and cause rubber-banding. Ethernet removes that entire category of spike. If you still spike on Ethernet, the cause is bufferbloat, background traffic, or an upstream ISP/routing issue.

What is bufferbloat and why does it cause spikes?

Bufferbloat is excessive buffering in your router or modem that piles up when the connection is busy, adding large, variable delay. When a download or upload saturates the line, latency can jump from 20 ms to several hundred milliseconds in bursts — felt in-game as sudden lag spikes. Enabling QoS or SQM on the router caps the queue and keeps latency stable under load.

Could the lag spikes be the game server, not me?

Yes. If everyone in a match spikes at the same moment, or only one game spikes while others are smooth, the server or its routing is the likely cause — nothing on your end will fix it. Your continuous ping to a neutral public IP staying flat during an in-game spike is the clearest sign the problem is the server, not your connection.