How do I fix high ping in online games?

High ping in online games is almost always caused by a Wi-Fi connection or bufferbloat - when another device on your network is uploading or streaming and flooding your router's queue. Plug your gaming device into Ethernet and close any background downloads or video calls first. If ping drops immediately, you have found the culprit and the rest of this article will help you lock in the fix permanently.

What ping actually measures

Ping measures the round-trip time in milliseconds (ms) for a data packet to travel from your device to the game server and back. Lower is always better. As a rule of thumb, under roughly 50 ms is comfortable for most games; once you exceed 150 ms, most players notice rubber-banding, shot registration failures, or opponents teleporting. The value shown in-game reflects every hop between your device and the server - your home network, your ISP's backbone, and the last-mile connection to the data centre all contribute.

Root causes, ranked by how often they appear

1. Wi-Fi interference or distance - the single most common cause. Wireless connections add variable latency, drop packets silently, and retransmit them without warning, all of which inflate ping and jitter.
2. Bufferbloat - someone on the same network is uploading large files, streaming 4K, or on a video call. Your router's buffer fills, and game packets wait in the queue behind bulk data.
3. Congested 2.4 GHz band - only three non-overlapping channels shared with every neighbouring router, Bluetooth device, and baby monitor in range.
4. Background downloads on the gaming device itself - a console updating firmware or a PC seeding torrents can saturate your upload link and trigger bufferbloat even when nobody else is active.
5. Wrong game server region - the game is routing you to a data centre on another continent.
6. ISP routing issues - your ISP takes a suboptimal path to the game's data centre, adding unnecessary hops.

Fix 1: Switch to Ethernet

A wired Gigabit Ethernet connection eliminates the single biggest source of variable latency. Run a Cat 5e or Cat 6 cable from your router directly to your gaming device. On a laptop without a port, a USB-C to Gigabit Ethernet adapter is reliable and costs under $20. After plugging in, confirm the connection is recognised as wired in your device's network settings - consoles in particular may need you to select Wired manually.

Run a quick baseline to measure the improvement:

Look at the individual time= values. Consistent results with small variation confirm a healthy wired path. Spikes above 100 ms alongside otherwise low pings usually point to bufferbloat - continue to Fix 2.

Fix 2: Eliminate bufferbloat with SQM

Bufferbloat happens when your router uses a simple first-in-first-out (FIFO) buffer during congestion. A large upload fills that buffer and small game packets queue behind megabytes of cloud backup data. Smart Queue Management (SQM) - also called FQ-CoDel, CAKE, or Adaptive QoS depending on the router brand - solves this by isolating flows and prioritising latency-sensitive traffic.

To reach your router's admin panel, first check your default gateway. On Windows, open Command Prompt and run ipconfig /all, then read the Default Gateway line. On macOS, open Terminal and run networksetup -getinfo Wi-Fi or netstat -nr | grep default. Open that IP address in a browser. Common paths to QoS settings by brand:

• TP-Link Archer: tplinkwifi.net or 192.168.0.1 - Advanced - QoS
• ASUS: asusrouter.com - Adaptive QoS - Gaming Boost
• Netgear Nighthawk: routerlogin.net - Advanced - QoS Setup
• Orbi: orbilogin.com - Advanced - QoS Setup
• Linksys: linksyssmartwifi.com - Prioritization
• Xiaomi: miwifi.com - Advanced - QoS

Set upload and download speed limits to 80-90% of your actual line speed - run a speed test first to get accurate numbers. This headroom lets the router manage queues before your ISP's upstream buffer fills. Exact menu labels vary by firmware version; look for anything mentioning queue, FQ-CoDel, CAKE, or gaming priority.

If your router does not support SQM natively, OpenWrt and DD-WRT both include the CAKE queueing discipline. On OpenWrt, install the luci-app-sqm package via System - Software. On DD-WRT, a CAKE script is available under Administration - Scripts. Flashing third-party firmware is the most effective software fix for bufferbloat short of replacing the router entirely, though it voids most warranties.

Fix 3: Move to 5 GHz or 6 GHz Wi-Fi

If Ethernet is not possible, at minimum move off 2.4 GHz. Connect to the SSID ending in _5G or _5GHz if your router broadcasts separate names per band. The 5 GHz band offers many more non-overlapping channels and far less competition from neighbouring networks. Wi-Fi 6E routers add a 6 GHz band which is even cleaner, though it has shorter range through walls.

On Windows, open Device Manager, expand Network Adapters, right-click your Wi-Fi card, choose Properties, go to the Advanced tab, and find Preferred Band or Band Preference. Set it to 5 GHz. The exact label varies by driver version. On routers running OpenWrt, the usteer package provides band steering to nudge capable clients onto 5 GHz automatically.

Fix 4: Stop background downloads and uploads

On PlayStation 5: Settings - System - System Software - Automatic Updates - disable automatic downloads, or restrict them to rest mode. On Xbox: Settings - General - Sleep mode and startup - set updates to run only in standby. On PC: pause Windows Update, close torrent clients, and suspend cloud sync services such as OneDrive, Dropbox, or iCloud Drive before a session.

Also check other devices on the network. A smartphone backing up photos, a security camera uploading footage, or a smart TV downloading a firmware update can saturate your upload link and trigger bufferbloat for every device simultaneously. A router QoS rule that deprioritises bulk upload traffic protects the whole household without requiring you to police each device manually.

Fix 5: Select the correct game server region

Many games auto-select a server region, sometimes incorrectly. Look for a region or data centre selector in the game's settings or lobby screen. If you are in western Canada and the client is routing you to US East or Europe, physical distance alone adds 80-200 ms before any other factor. Set the region manually to the one nearest your location.

On PC launchers, also confirm the download region matches your geography. A mismatched download region does not directly affect in-game ping, but it suggests the client has misjudged your location and may be doing the same for matchmaking servers.

Fix 6: Diagnose ISP routing with traceroute

If ping remains high on a wired connection with no background traffic and SQM enabled, the problem is likely inside your ISP's network or at a peering exchange between your ISP and the game's data centre. Use traceroute to identify where latency is being added.

Read the output hop by hop. Latency that first appears within the first two or three hops is a local problem - check your own setup. Latency that jumps at a hop labelled with your ISP's AS name and stays elevated from that point onward is an ISP routing issue. Document it with screenshots and contact their technical support; routing problems sometimes require escalation to a network operations team. Hops showing * * * are configured not to respond to ICMP probes - this is normal and does not indicate packet loss.

Windows-specific steps

Open Network and Sharing Centre (search in the Start menu) and confirm your adapter type. Check that TCP/IPv4 is set to obtain IP and DNS automatically unless you have a specific reason for manual settings. A misconfigured or unreachable DNS server adds hundreds of milliseconds to connection attempts at lobby or match start.

To reduce latency from TCP acknowledgement batching, open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\. Find the sub-key that matches your gaming adapter's IP address. Add two DWORD (32-bit) values: TcpAckFrequency set to 1 and TCPNoDelay set to 1. This disables Nagle's algorithm for that interface, preventing Windows from batching small TCP acknowledgements. Back up the registry before editing.

macOS-specific steps

Open System Settings - Network. If your interface shows an address starting with 169.254, DHCP has failed and the device has self-assigned an APIPA address - it has no real network connectivity. Renew the DHCP lease by selecting the interface, clicking Details, then Renew DHCP Lease. On older macOS, this is under System Preferences - Network - Advanced - TCP/IP.

To check your default gateway and confirm routing from Terminal:

Linux-specific steps

Use resolvectl status on systemd-resolved systems (Ubuntu 20.04 and later, Fedora, Arch) to confirm which DNS servers are active. A dead upstream resolver adds latency to every new hostname lookup during gameplay. For a richer traceroute that shows per-hop packet loss over time, install and run mtr:

The mtr tool runs a continuous probe and reports packet loss per hop, making periodic congestion far more visible than a one-shot traceroute.

iOS and Android

Mobile gaming ping is almost always caused by being on cellular data rather than Wi-Fi, or by Wi-Fi sitting on the congested 2.4 GHz band. On iOS, tap Settings - Wi-Fi, then the info icon next to your network - it shows the frequency band in use. On Android the path varies by manufacturer; look under Wi-Fi - Network Details or a similar label. Switch to the 5 GHz SSID if it is available.

Disable Wi-Fi Assist on iOS (Settings - Cellular - Wi-Fi Assist) and the equivalent Adaptive Wi-Fi setting on Android. These features silently switch between Wi-Fi and cellular when signal is weak - exactly when they fire, ping spikes mid-match. For competitive sessions at home, a USB-C to Gigabit Ethernet adapter is a practical wired option on modern Android phones and iPads.

Carrier-grade NAT and NAT type issues

Check your router's WAN IP address in the admin panel. If it falls in the 100.64.0.0/10 range, your ISP is using carrier-grade NAT (CGNAT) - multiple subscribers share a single public IP. CGNAT causes strict NAT type warnings on consoles (Type 3 on PlayStation, Strict on Xbox), peer-to-peer connection failures, and higher latency because matchmaking routes you through relay servers rather than direct connections. Contact your ISP and ask for a dedicated public IPv4 address; many providers offer this free or for a small monthly fee.

How to confirm the fix worked

Run a 20-packet ping to the game's server IP while in a lobby (find the IP with netstat -n filtered to the game process), or use the in-game network stats overlay if one is available. Compare average and maximum values before and after your changes. Also run the Waveform Bufferbloat Test - a free browser-based tool - to grade your connection A through F. An A or B grade means bufferbloat is under control.

For a longer-term baseline, log continuous pings and review them for time-of-day patterns:

Spikes that appear consistently in the evening point to congestion on a shared cable segment - a problem to escalate to your ISP rather than to fix locally.

Common misdiagnoses

• My internet is fast, so ping should be fine. Download speed and ping are nearly unrelated. A 1 Gbps connection with bufferbloat can show 300 ms in-game while a 25 Mbps line with SQM enabled shows 12 ms.
• The game servers must be overloaded. Before blaming the game company, confirm your ping to a neutral target like 8.8.8.8 is normal and that traceroute shows no unexpected latency in your own network or at ISP hops.
• My router is new, so it must be fine. Consumer routers almost never ship with SQM enabled. Even a current-generation Wi-Fi 7 router exhibits severe bufferbloat under load without QoS configured.
• Changing my DNS server will lower in-game ping. DNS only affects hostname resolution time - relevant at lobby load, not during gameplay. Once a session is active, the game communicates using raw IP addresses and DNS is not involved.

IPv6, DoH, and DNSSEC in 2026

Many ISPs now provide native dual-stack IPv6. Games and matchmaking services increasingly prefer IPv6 endpoints. If your router is doing 6-to-4 tunnelling rather than native IPv6 passthrough, you may see higher latency than on a pure IPv4 or native IPv6 path. Confirm with your ISP whether native IPv6 is available on your plan and enable it in the router's WAN settings.

DNS over HTTPS (DoH) and DNS over TLS (DoT) are now enabled by default in Windows 11 23H2 and later builds, and in current Firefox and Chrome. These add a small overhead to DNS lookups but have no effect on in-game ping once a session is active. DNSSEC validation adds measurable processing overhead to DNS responses - negligible for gameplay, but worth checking if you are debugging slow lobby loads that precede otherwise normal in-game ping. For more on how DNS resolution affects connection performance, the Cloudflare DNS learning centre is a thorough reference.

Prevention checklist

1. Use Ethernet for all competitive gaming sessions.
2. Enable SQM or QoS on your router with speeds set to 80-90% of your measured line rate.
3. Schedule console and PC updates to run in standby or rest mode during off-peak hours.
4. Check your WAN IP - if it starts with 100.64, ask your ISP for a dedicated public address.
5. Run traceroute once a month if you play competitively; ISP routing paths change without notice.
6. On Wi-Fi, stay on 5 GHz or 6 GHz and keep the router in the same room or the next.