How to Fix Gaming Lag: From Ping and Bufferbloat to NAT Type
Suffering from lag while gaming? Learn why ping matters more than Mbps and how to fix jitter, packet loss, bufferbloat, NAT problems and Wi-Fi lag step by step.
You fire first, yet you’re the one who goes down. Opponents jump around the screen, your character snaps back to where it was a second ago, or you get a poor connection warning mid-match. Lag is frustrating, and it’s often tackled the wrong way: with a more expensive plan. In most cases the fix lies elsewhere. This article explains what really causes lag and how to solve it step by step.
Lag is about delay, not speed
An online game constantly sends small packets with your actions and receives updates about the game world. That uses little bandwidth: most games use a few Mbps at most while you play. A 50 Mbps connection is therefore plenty for gameplay itself. Bandwidth only matters for downloading games and updates.
What does matter are four other values:
- Ping (latency): how long a packet takes to reach the server and come back. Below 20 ms is excellent, up to 50 ms good, above 100 ms clearly noticeable.
- Jitter: the variation in ping. A steady 40 ms ping plays better than one swinging between 15 and 90 ms. Keep jitter below 10 ms for competitive gaming.
- Packet loss: packets that never arrive. From as little as 1% you’ll notice actions that don’t register and opponents that teleport.
- Bufferbloat: how much your ping rises when your connection is fully loaded, for example by a download elsewhere in the house.
For more background on these terms, see ping, jitter and packet loss explained.
Step 1: measure where the problem is
Start with a speed test on the device you game on, or on a laptop in the same spot. Ignore download speed and look at ping, jitter, packet loss and bufferbloat. Lag that only appears now and then is better caught with the stability test: it measures for five minutes and shows spikes and brief drop-outs. Run both tests over Wi-Fi and over a cable, and you’ll immediately know whether Wi-Fi is the culprit.
Step 2: use a cable
The biggest win for most gamers: connect your console or PC with an Ethernet cable. Wi-Fi is a shared medium where devices take turns to transmit and suffer interference from neighbours, walls and other devices. That mainly produces jitter and occasional packet loss, which is exactly what causes lag. A cable eliminates almost all of it.
Can’t run a cable? Try these in order: a mesh system or access point with wired backhaul nearby, coax (MoCA), or powerline (test it first). If it has to be Wi-Fi, use 5 or 6 GHz, make sure the signal is strong and don’t put the console inside a closed TV cabinet.
Step 3: tackle bufferbloat
Does your game run fine until a housemate streams a film, someone downloads a game update or a phone runs a backup? Then bufferbloat is the cause. As soon as your connection is full, long queues build up in your router or modem. Your game packets end up at the back of the queue and your ping shoots up.
The fix is Smart Queue Management (SQM) with algorithms such as fq_codel or CAKE. These keep queues short and make sure small, time-sensitive packets don’t get stuck behind large downloads. Set the bandwidth in SQM slightly below your measured line speed, for example 85 to 95 per cent, so that the queue forms in your own router rather than in the modem. If your router doesn’t support SQM, look for QoS or a “gaming” option that limits bandwidth. More in what is bufferbloat.
Step 4: choose the right server
Distance to the game server is a hard limit. Light in optical fibre travels roughly 200 kilometres per millisecond, and real routes are longer than a straight line. If you play from the Netherlands on a US server, you’ll always be above 80 to 100 ms, however good your connection. Check your game’s settings to see whether you can choose a region, and pick the nearest, usually Western Europe. Note that matchmaking sometimes puts you on another server when few players are online.
Step 5: check your NAT type
NAT (Network Address Translation) lets all the devices in your home share a single public IP address. For gaming this can cause problems, especially with peer-to-peer connections and voice chat. Consoles show your NAT type: on Xbox as Open, Moderate or Strict, on PlayStation as Type 1, 2 or 3. A strict NAT type leads to trouble connecting, being unable to host or not hearing teammates. It usually doesn’t raise your ping, but it can pair you with a less favourable server or host.
To improve your NAT type:
- Enable UPnP on your router so the console can open ports itself. This is the simplest solution.
- Set up port forwarding if UPnP doesn’t work: give your console a fixed IP address on your network and forward the ports specified by the game or console maker to that address.
- Avoid double NAT: if you use your own router behind your provider’s modem, put the modem in bridge mode or make sure only one device acts as router.
- Check for CGNAT or DS-Lite: some providers share one public IPv4 address between customers, in which case port forwarding won’t work. Ask your provider for your own public IPv4 address; many providers offer this.
With the port check in the network tools, you can verify whether a forwarded port is actually reachable from outside.
Step 6: the other suspects
- Background traffic: downloads, updates and cloud sync on your PC or console itself. Pause them while playing.
- VPN: a VPN usually adds latency. Switch it off while gaming unless you have a specific reason not to.
- Outdated router or firmware: an old router may not keep up with heavy traffic. Update the firmware or consider replacing it.
- Problems at your provider: if packet loss or extreme jitter persists on a cable, even with no other traffic in the house, collect measurements at different times and report it to your provider.
- It’s not always you: server problems on the game’s side happen too. Check the game’s status page or social channels.
Checklist
- Look at ping, jitter, packet loss and bufferbloat, not Mbps.
- Connect your console or PC with an Ethernet cable.
- Enable SQM (fq_codel or CAKE) or QoS, slightly below your line speed.
- Choose the nearest server or region.
- Get an open NAT type with UPnP or port forwarding, and avoid double NAT.
- Pause background downloads and switch off your VPN.
- Use the stability test if lag comes and goes.
Measure it yourself
Speed test with bufferbloat, jitter and AI explanation. Free and ad-free.