Home / Knowledge Center / Ping & Latency
Why Does My Ping Spike?
9 min read · Updated 2026-09-17
A ping spike is a sudden jump from a normal value to several hundred milliseconds, lasting a second or two. Averages hide them, which is why a connection can test perfectly and still rubber-band in games. Spikes almost always come from something that appears intermittently: a queue filling, a wireless collision or a background transfer.
Key takeaways
- Spikes are a variance problem, not an average problem — a normal speed test will not show them.
- The most common single cause is a saturated uplink filling a router queue, known as bufferbloat.
- WiFi contributes spikes through interference, retransmissions and roaming between access points.
- Background updates, cloud sync and other devices are frequent triggers.
- Measure latency while the line is deliberately loaded — that is when spikes reveal themselves.
Cause 1 — A saturated uplink filling the queue
When any device starts a large upload, packets queue at your router. Oversized buffers hold them for hundreds of milliseconds instead of dropping a few early, so every other packet waits behind them. This is bufferbloat, and it produces exactly the pattern of a fine idle ping with severe spikes under load.
The test is simple: measure latency while idle, then start a large upload and measure again. A jump from 25 ms to 300 ms points at queue management, and enabling QoS or SQM on the router usually fixes it.
Cause 2 — WiFi interference and retransmission
Wireless is a shared medium. When two devices transmit at once the frames are lost and retried, and each retry adds delay. Microwaves, neighbouring networks on the same channel and distance from the router all increase retry rates, which shows up as erratic latency rather than reduced bandwidth.
Roaming adds its own spikes: as a laptop or phone moves between access points in a mesh network, the handover briefly interrupts the path.
Cause 3 — Background traffic you forgot about
Console and PC game updates, photo sync, cloud backup, system updates and someone else's video call all compete for the same uplink. Spikes that appear on a schedule — always at night, always right after you turn a console on — are usually automatic updates.
Cause 4 — The route, the server or the provider
Congestion at a peering point or a single overloaded hop inflates latency for everyone on that path, typically during evening peak hours. Game server problems produce the same symptom but only in one title. Comparing latency to several destinations separates the two: if every destination spikes, the problem is close to you or in your provider's network.
Cause 5 — Local hardware and power saving
Wireless adapter power-saving modes, outdated drivers, overheating routers and failing cables all produce intermittent latency. A router that has been running for months without a restart, or one whose CPU is pegged by traffic inspection features, will spike under load regardless of the line quality.
A practical isolation order
Work from the inside out and change one thing at a time.
- Test on Ethernet — if spikes vanish, focus entirely on WiFi.
- Test with everything else offline, then reintroduce devices one by one.
- Test idle versus loaded to expose bufferbloat.
- Test at different times of day to identify peak-hour congestion.
- Test with the VPN off, then on, to measure its contribution.
Put this into practice with a real measurement.
Check your latency