Ping Spikes
A ping spike is a sudden, temporary increase in latency — your connection goes from 20 ms to 200 ms for a fraction of a second. In games this causes rubber-banding and teleporting enemies. In video calls it causes brief audio freeze. Even infrequent spikes are highly disruptive to real-time applications.
Ping spikes vs high ping — the difference
High ping means your average latency is consistently elevated — for example, 120 ms on every packet. This is usually a routing or distance issue. Ping spikes means your latency is normally low but intermittently jumps — 15 ms most of the time, but 300 ms every few seconds. Spikes are often harder to diagnose because they don't show up on average latency metrics; you need to look at max latency and jitter. What is latency? →
Jitter is the measure of latency variation. A connection with 15 ms average but 200 ms max has high jitter, and this is what causes the perceptible lag in gaming and calls. What is jitter and what's a good value? →
Common causes of ping spikes
| Cause | Typical spike pattern | Fix |
|---|---|---|
| Wi-Fi interference / channel contention | Random, frequent, 50–300 ms | Switch to Ethernet or 5 GHz Wi-Fi |
| Background downloads / uploads saturating connection | Sustained spikes while download/upload is active | Enable QoS; pause background transfers; enable bufferbloat mitigation |
| Bufferbloat | Latency balloons when upload or download is saturated | Enable SQM/FQ-CoDel on router; update firmware |
| ISP line quality issues | Regular spikes at specific times or persistent | Contact ISP for line test; replace coax/phone cable |
| Routing issues (ISP or internet backbone) | Spikes to specific servers only; other destinations fine | Limited control — report to ISP; check if VPN improves routing |
| DNS lookup delays | Spikes only on initial page load / connection to new server | Switch to Cloudflare 1.1.1.1 or Google 8.8.8.8 |
| CPU/memory overload on device or router | Spikes correlate with system activity | Close background processes; restart router; upgrade hardware |
Bufferbloat: the hidden cause of gaming lag
Bufferbloat is one of the most common causes of ping spikes that people don't know about. When your connection becomes saturated — a large download or upload fills all available bandwidth — your router queues excess packets in a large buffer rather than dropping them. This causes latency to spike by hundreds of milliseconds while the buffer drains.
A practical example: you're gaming with 20 ms ping. Someone in the household starts a Steam game download. Your latency spikes to 300–400 ms. The download is saturating your download bandwidth, and the router's large buffer is introducing hundreds of milliseconds of queuing delay.
The solution is Smart Queue Management (SQM) — specifically algorithms like FQ-CoDel and CAKE that actively manage queue depth and prevent bufferbloat. Many modern routers include SQM in their QoS settings. OpenWrt and DD-WRT firmware also support FQ-CoDel on compatible hardware. Bufferbloat explained in detail →
How to diagnose ping spikes precisely
A one-time speed test won't reveal ping spikes. You need a continuous latency monitor:
- Ping plotter (Windows/macOS) — sends continuous ICMP pings to a target and graphs latency over time, including per-hop latency in traceroute mode
- WinMTR (Windows) — running traceroute combined with continuous ping to identify which router hop introduces the spike
- Terminal (macOS/Linux):
ping -i 0.2 8.8.8.8— rapid ping to Google's DNS showing real-time latency
Run the monitor while actively gaming or on a call, and reproduce the spike. Then identify where in the traceroute the spike first appears — that's the device or segment causing it.
Wi-Fi-induced ping spikes
Wi-Fi is the most common cause of ping spikes for home users. Wi-Fi uses shared medium access (CSMA/CA — Carrier Sense Multiple Access with Collision Avoidance). Every device on the same Wi-Fi channel competes for airtime. When multiple devices transmit simultaneously, collisions occur, packets are discarded, and retransmissions cause latency spikes.
Switching from Wi-Fi to Ethernet eliminates this class of spike entirely. If Ethernet is not possible, using the 5 GHz band (lower occupancy, more channels, shorter range = less interference from neighbours) significantly reduces Wi-Fi-induced jitter compared to 2.4 GHz. Ethernet vs Wi-Fi for low latency →
ISP line quality and ping spikes
On cable (DOCSIS) and DSL connections, line quality issues — noise, attenuation, micro-interruptions — cause periodic spikes that aren't caused by anything in your home network. These typically appear as regular spikes (every few minutes) or spikes that correlate with weather or time of day.
Diagnosis: connect your computer directly to the modem via Ethernet (bypassing your router and all Wi-Fi). If spikes persist, the problem is the line, not your home network. Request a line quality test from your ISP — they can check downstream/upstream signal levels and error rates remotely. ISP congestion vs line fault — how to tell the difference →