Why Do I Have Lag Spikes?

This guide helps you validate whether lag spikes are caused by Wi‑Fi, uploads, router load, packet loss, bufferbloat or provider congestion.

Lag spike guide

Why Do I Have Lag Spikes?

This guide helps you validate whether lag spikes are caused by Wi‑Fi, uploads, router load, packet loss, bufferbloat or provider congestion.

Run speed test Broadband issue hub
Lag spikes troubleshooting illustration showing ping graph spikes, router and gaming device

Issue

Symptoms of Lag Spikes

Why these specific signs confirm a lag spike issue.

  • Ping suddenly jumps during games or calls: Ping measures the round-trip time for data to travel from your device to a server and back. A stable connection keeps this number flat, such as 20ms. Sudden jumps to 200ms or 500ms confirm that packets are getting stuck in a queue somewhere along the line.
  • Games rubber-band even when download speed is high: High download speed only measures how much data your line can pull per second. It does not guarantee that the data arrives on time. Rubber-banding occurs when your game client loses track of real-time positioning due to delayed packets, proving that bandwidth is not the same thing as connection quality.
  • Lag gets worse during local streaming or downloading: This is the classic signature of bufferbloat. When someone else on your network maxes out upload or download capacity, the router’s memory buffers fill up. Instead of transmitting your gaming or call data instantly, the router holds it or drops it, causing massive, immediate lag spikes.
  • The problem is intermittent rather than constant: Constant lag usually points to a physical line fault or a distant server. Intermittent spikes indicate a dynamic issue, usually triggered by changing conditions such as Wi‑Fi interference bursts, local network usage spikes, or peak-hour provider routing bottlenecks.
  • Ethernet feels smoother than Wi‑Fi: Wireless connections share the airwaves with other devices and are prone to sudden interference drops. If switching to a physical Ethernet cable reduces or eliminates the spikes, you have confirmed that the issue is rooted in local radio interference or Wi‑Fi congestion rather than the internet line itself.

Likely causes

Most Common Causes

The same lag spike symptom can have several different causes. Use the validation steps below to prove which one is affecting your connection.

Wi‑Fi Interference

Co-channel contention: When neighbouring routers use the same wireless channel, your router must wait for the airwaves to clear before sending data. This waiting time creates immediate, erratic jumps in ping.

Non-Wi‑Fi RF noise: Devices such as microwaves, older Bluetooth gadgets and wireless security cameras can blast noise across the 2.4GHz and 5GHz frequencies, corrupting data mid-air and forcing re-transmissions.

Dynamic environment changes: Human bodies, closed doors and moving objects constantly alter the path of wireless radio waves. These quick changes can force your device to switch connection speeds, causing brief latency spikes.

Upload Saturation

Asymmetric line limits: Most broadband connections offer much slower upload speeds than download speeds. It takes very little traffic to completely max out the upload pipe.

ACK packet stalling: To download data, your device must send back tiny acknowledgement packets. If a cloud backup or CCTV upload fills your upstream, these ACK packets get trapped and your download stream temporarily stalls.

TCP window collapses: When upload capacity is exhausted, web traffic protocols shrink the data window, creating a severe bottleneck that feels like a sudden freeze.

Bufferbloat

Over-buffered hardware: Standard routers use internal memory caches to prevent data loss. When traffic surges, the router holds packets in this queue rather than sending them instantly.

First-in, first-out queuing: Standard routers often treat all data equally. A large, non-urgent download can sit ahead of your time-sensitive gaming or call traffic, delaying those packets by hundreds of milliseconds.

Latency inflation: The longer a packet sits inside the router’s memory waiting for its turn, the higher your real-time ping climbs, leading to sudden rubber-banding.

Packet Loss

Fragmented streams: When packets fail to arrive because of a bad cable, poor signal or unstable route, the receiving application experiences a gap in information.

Position prediction failure: Online games guess where your character is moving. When a burst of packets is dropped, the server loses your true position and then snaps you back once the connection resumes.

Audio and video drops: In voice calls, dropped packets mean the app cannot stitch the audio stream together in real time, resulting in robotic voices, frozen video frames and sudden silence.

Peak-Time Congestion

Provider backhaul strain: During peak evening hours, usually 6 PM to 11 PM, heavy local demand can bottleneck the provider’s cabinet, exchange or backhaul link.

Shared media contention: Some connection types share fixed local capacity across a neighbourhood. High usage from nearby homes can directly increase latency on your line.

Transit link bottlenecks: Core peering points between your ISP and global data networks can become congested, delaying traffic before it reaches the target server.

Validate

Steps to Narrow Down the Root Cause of the Issue

Work through these checks in order. Change one thing at a time so the result tells you something useful.

  1. 1

    Run a speed test and note ping and jitter.
    What it establishes: your network baseline performance.
    The diagnostic logic: testing while the network feels stable gives you a control metric. A healthy baseline should show low ping, ideally under 30ms, and low jitter, ideally under 5ms. This proves your line and router are physically capable of stable delivery under normal conditions.

  2. 2

    Repeat while the issue is happening.
    What it isolates: baseline performance versus active degradation.
    The diagnostic logic: comparing this result to your baseline reveals the nature of the lag spike. If download speed remains high but ping or jitter skyrockets, you have confirmed a latency stability issue rather than a bandwidth restriction.

  3. 3

    Test close to the router and over Ethernet.
    What it isolates: local wireless radio noise versus the incoming internet line.
    The diagnostic logic: testing next to the router rules out distance. Switching to Ethernet rules out the wireless spectrum entirely. If lag spikes vanish on Ethernet, the root cause is Wi‑Fi interference. If they persist while wired, the issue lies in router hardware, local traffic or the provider.

  4. 4

    Pause uploads, downloads and streaming, then retest.
    What it isolates: internal device traffic overload versus external line faults.
    The diagnostic logic: cloud syncs, console updates and 4K streams force the router to queue data. If pausing all background activity instantly flattens your ping spikes, you have proven that upload saturation or local traffic is overloading your connection.

  5. 5

    Run the bufferbloat test to check loaded latency.
    What it isolates: router queue management capability.
    The diagnostic logic: a bufferbloat test maxes out download and upload while measuring ping changes. If ping jumps significantly under load, such as from 20ms to 200ms, your router is suffering from bufferbloat and cannot prioritise gaming or call traffic when the line is busy.

  6. 6

    Check whether lag affects every game/server or one service only.
    What it isolates: global network routing versus a specific external server.
    The diagnostic logic: if lag spikes happen across multiple games, websites and voice apps at the same time, the fault is local to your home or provider. If they occur only on one game server or app, your home network is likely fine and the root cause is a server or route issue at the destination.

Fix

Problem Resolution

Apply the fix that matches the cause you validated. If the issue is proven outside your home network, gather evidence before contacting your provider.

Use Ethernet where possible

Target cause: Wi‑Fi interference and wireless channel congestion.

Why it works: Physical copper cabling removes radio wave degradation completely. It eliminates the need for your device to wait for airwaves to clear or re-transmit packets corrupted by electronic noise. This lowers jitter immediately and locks ping to the lowest baseline your line can provide.

Stop upload saturation

Target cause: Upload saturation and blocked download acknowledgement packets.

Why it works: Pausing cloud backups, large uploads and continuous CCTV streams frees upstream bandwidth. This lets essential acknowledgement packets flow out instantly, preventing incoming gaming or call data streams from stalling.

Enable SQM/QoS if available

Target cause: Bufferbloat and poor router queue management.

Why it works: Standard routers often process data first-in, first-out, so large file transfers can block time-sensitive traffic. Smart Queue Management or Quality of Service changes this rule by prioritising small, time-sensitive packets such as gaming inputs and voice calls over bulk downloads, keeping latency flatter under load.

Escalate with evidence

Target cause: Peak-time congestion or external provider routing faults.

Why it works: Providers cannot easily dismiss lag complaints when you provide time-stamped logs showing spikes over wired Ethernet during quiet hours. Specific ping and jitter metrics prove the issue is on their network layer and support an investigation into local capacity or routing.

Next guides

Related broadband troubleshooting guides

If this page does not exactly match the issue, use one of these related guides from the broadband issue hub.

Bufferbloat test Packet loss High ping