"Ping is 15 on a cable and jumps between 15 and 80 on Wi-Fi." "It's fine in the morning and bad every evening." "Every so often the game freezes for a second and everyone teleports." What these have in common is variation rather than a high average, and on a wireless link variation has causes you can check one at a time.
Why a wireless link wobbles
- Shared airtime. Devices on the same channel take turns to transmit, and that includes your neighbours' networks. Cisco's 802.11ax white paper calls sharing one channel in one space a challenge for "any wireless system including 802.11 CSMA-based networks", and says achievable throughput falls as contention rises, from clients on your own access point or on a neighbouring network that overlaps it (Cisco). While your packet waits for its turn, the wait is jitter.
- Interference on 2.4 GHz. Microsoft notes that household devices such as microwaves and cordless phones, and Bluetooth devices, use the 2.4 GHz band too (Microsoft Support).
- Resent frames. Wi-Fi expects an acknowledgement for the frames it sends; when none comes, the frame is sent again, and past a retry limit it is dropped. Windows' own Wi-Fi statistics count all three: frames that needed retransmission, acknowledgements that never arrived, and frames that failed after the retry limit (Microsoft Learn). A retried packet arrives late; a dropped one never arrives.
- The adapter's own scans. While you are connected, Windows leaves background scanning on unless a program asks for it to stop, and Microsoft's Wi-Fi driver rules for media streaming give a scan as the example of something that "can negatively affect the latency or bandwidth" of the connection. High ping and lag spikes covers what that does to ping, along with w0a's Wi-Fi quiet: part of the Game Mode switch on the Process Manager page, off until you turn it on, it asks Windows to switch off background scanning on each wireless adapter while a game runs.
See what you are connected to
- Settings > Network & internet > Wi-Fi > (your network) properties shows the band and channel next to Network band (channel). If it lists more than one band, Multi-Link Operation is supported on that connection (Microsoft Support).
netsh wlan show driverslists Radio types supported: 802.11ax means Wi-Fi 6/6E, 802.11be means Wi-Fi 7.netsh wlan show networks mode=bssidlists each access point your adapter can hear, with its signal strength, radio type and channel, according to Microsoft's netsh reference. Count how many share your channel.
2.4, 5 or 6 GHz
Microsoft's comparison of the three bands:
| Band | For it | Against it |
|---|---|---|
| 2.4 GHz | Longer range, better through walls | Slower, fewer channels that don't overlap, more congested |
| 5 GHz | Faster, more channels that don't overlap, less congested | Shorter range, worse through walls |
| 6 GHz | Low congestion, lower latency | Shorter range than the other bands, worse through walls; the router, the adapter and its driver must all support Wi-Fi 6E |
Microsoft goes as far as "A strong 6 GHz connection is the best for gaming, streaming, and video calls". The word doing the work is strong: a few walls away, the 5 GHz link can be the steadier one, and only a measurement in your own home says which.
Channels, width and radar
Microsoft's Wi-Fi troubleshooting page suggests changing the router's channel to reduce interference, and the netsh list shows which channels your neighbours use. Microsoft's home-layout guide says to pick channel 1, 6 or 11 on 2.4 GHz, the ones that don't overlap, and on 5 GHz, where overlap matters less, the channel with the fewest access points for your signal strength. For 2.4 GHz, the same guide notes that some older adapters and drivers don't work well with a 40 MHz channel width, and suggests 20 MHz when the signal is strong and the channel clear but the connection still isn't reliable. Wider channels, 160 MHz on Wi-Fi 6 and 320 MHz in the 6 GHz band on Wi-Fi 7, add bandwidth (Wi-Fi Alliance).
Part of the 5 GHz band is shared with radar. Under the European standard, ETSI EN 301 893 (version 2.2.1, 2024), a router using a channel that falls partly or wholly within 5,250-5,350 MHz or 5,470-5,725 MHz must run Dynamic Frequency Selection (DFS): it must check the channel for radar before using it, which in the standard check takes 60 seconds (10 minutes within 5,600-5,650 MHz), and when it detects radar it must tell its clients to stop transmitting there within 10 seconds and keep off the channel for at least 30 minutes. If your router's channel list marks some 5 GHz channels as DFS, these are the ones. A detection mid-match interrupts your connection while the router moves, so if a good link drops at random moments, try a channel outside those ranges. The figures above are from the European standard.
What Wi-Fi 6, 6E and 7 change
- OFDMA (Wi-Fi 6): per the Wi-Fi Alliance, it "effectively shares channels to increase network efficiency and lower latency".
- OBSS packet detection (802.11ax): lets an access point and its clients ignore frames from other networks that are typically some distance away. Cisco credits it with "a significant reduction in latency variation", because the access point or client is "much less likely to have its TXOP delayed by a friendly (or rogue) neighbor", a TXOP being its transmit opportunity.
- 6 GHz (Wi-Fi 6E and 7): Microsoft describes it as "a less crowded spectrum".
- Multi-Link Operation (Wi-Fi 7): lets devices use several bands at once "to avoid network congestion and maintain connectivity", per Microsoft. Wi-Fi 7 needs Windows 11, version 24H2 or later.
Microsoft lists the router, the PC's adapter and Windows as requirements, so a new router alone does not bring these features to your PC. How much any of them changes ping on your network has not been measured here.
Placement, extenders and mesh
Microsoft's checklist: fewer walls between your PC and the access point; closer is better, "but not right next to it"; the access point toward the middle of the home and higher, not in a corner or under a desk; and look for things that interfere, such as a metal filing cabinet. If you can't move either end, Microsoft suggests a network extender. An extender or mesh node that reaches the router over the air adds a second wireless link on the way, and everything above about shared airtime applies to it as well; where the nodes are joined by a cable, that second wireless link is gone.
When only a cable helps
A cable takes the radio out of the path: no shared airtime, no frames resent over the air, no radar. It doesn't need to be special for a gigabit port: IEEE 802.3ab defined gigabit Ethernet (1000BASE-T) over four-pair Category 5 cabling. Where a cable can't reach, two wired alternatives exist: powerline adapters (IEEE 1901 covers networking over a building's power lines) and MoCA, which reuses existing coax. No measurement of their latency is cited here, so test them the same way as Wi-Fi.
To see what the wireless link itself adds, run ipconfig and note the Default Gateway (your router), then run ping /n 100 followed by that address, once on Wi-Fi and once on a cable if you can. The router is one hop away, so what varies there is your link to it, not the internet. Compare how much the times spread, not just the average.
What does not help
- TCP and adapter settings on the PC. None of them changes airtime or interference; network tweaks says the same about its own boxes.
- A faster internet plan. It changes the line to your provider, not the radio between your PC and the router.
- A new router on its own, for the features that need the PC's adapter too.
Related
- High ping and lag spikes: what you can actually fix
- Network tweaks
- Strict or moderate NAT on PC
- Can a VPN lower your ping?
- DPC latency: when a driver is what stutters
Did this page help?
What was missing, or what did not work? We read every one of these.
If this page did not solve it, write to us — say which article you read, and we will fix the article.