Why ping spikes and how to find the cause

What a ping spike is

A ping spike is a packet that arrived noticeably later than its neighbors. The game survives one such packet, but a series of spikes breaks its timing: the server and the client stop agreeing on the clock, models jerk, and your key press reaches the server sometimes on time and sometimes late. The technical name for this is jitter — the spread of latency.

Spikes are sneaky because the average ping hides them. So turn on the full network stats in the game, not just the ping number: in CS2 the telemetry counts how often ticks are lost to packet loss or jitter, and Rocket League lights up a “!” next to the ping on the scoreboard with a separate mark for latency spikes.^1,2

Where spikes come from

Wi-Fi

The air is shared, and packets wait their turn or get resent after interference. This is the most common source of spikes for home players, and it is checked with one match over a cable.

Background downloads

While an update downloads or a cloud syncs, game packets queue behind the big download packets. The spikes come in waves and line up with the start and end of the download.

An overloaded ISP node

In the evening the interconnects between networks are at their busiest. The spikes show up at the same time of day and do not depend on what is happening at home.

A route change

The path to the server can change in the middle of a match: one of the carriers switched the traffic, and the packets took another road with a different latency. From the outside it looks like a step in the ping.

The server itself

An overloaded server answers everyone late at once. If ping spikes for the whole team at the same time, the cause is on that side.

Your PC

A frame rate dip also looks like a jerk, but the ping stays steady. It is not the network, and it is fixed with graphics settings and load, not with the router.

Finding the cause in three matches

1. Match one: as usual, but with the network stats on. Write down when it spikes — all the time, in firefights, in waves.
2. Match two: a cable instead of Wi-Fi, every download, stream and cloud sync paused — on the PC and on the phones and the TV. If the spikes are gone, the cause was at home.
3. Match three: the same server, but at a different time of day. Spikes only in the evening — that is your ISP's busy nodes.
4. In parallel keep the ping -t command running in the background to your router and to a stable host on the internet: if the spikes are already visible to the router, it is your home network; if only beyond it, it is the route. How to do that is in the guide on ping and pathping.
5. Compare with your team: if everyone spikes at the same time, it is the game server, and there is nothing to fix at home.

Where to turn on the network stats in the game: Counter-Strike 2 · Rocket League · Apex Legends · Fortnite · Dota 2 · Battlefield 6

What helps

• A cable. Or at least the 5 GHz band in the same room as the router with no walls in between.
• Pausing downloads for the match: the Steam and Epic Games clients have settings for downloads during gameplay, and Windows has active hours for updates.
• Game priority in the router (QoS) helps when several devices share the line; on a free line it makes no difference.
• A closer region in the game itself: a distant server means not only high ping but also more nodes on the way where queues can form.
• Your ISP's route cannot be changed from home — that is SLARP's part: it routes the game's traffic through its own network, picks the route to the server and optimizes ping and jitter for the whole match, and if the connection drops it finds a fallback route.
• An overloaded game server and frame rate dips are fixed by neither a router nor an accelerator: for the first, wait or change servers; for the second, adjust the graphics settings.