A normal speed test does not rule out packet loss. Throughput measures how much data moves; packet loss measures whether individual packets arrive. Confirm the game is reporting loss, test your local gateway over Ethernet, compare an unloaded and busy connection, then test a public destination and the game-specific route. Change one variable at a time.
Diagnostic commands and connection-isolation steps were checked against current Microsoft pathping and Wi-Fi guidance, Xbox network-statistics documentation, and the LagZero testing method linked below.
IN THIS GUIDE
- First, prove the symptom is packet loss
- 1. Build a tiny test log
- 2. Test your local gateway
- 3. Compare Wi-Fi with Ethernet
- 4. Pause traffic and test under load
- 5. Test beyond the router
- 6. Use pathping carefully on Windows
- 7. Separate one game from all games
- 8. Check the modem and ISP evidence
- 9. Run a controlled VPN route comparison
- What not to do
- FAQ
- Sources
Your download test says the connection is thriving. Your game says your character has discovered short-range teleportation. Both can be true.
Having packet loss but internet is fine usually means “fine” was measured with the wrong tool. A speed test emphasizes throughput. Games care about timely, consistent delivery of many small packets. Retransmissions can hide loss during downloads; real-time game traffic cannot always wait for a do-over.
The fix is not to reboot everything while chanting “gaming DNS.” It is to find the first place where repeatable loss appears.
First, prove the symptom is packet loss
Turn on the game’s built-in network statistics if available. Record packet loss, ping, jitter, and FPS during a bad session.
Packet loss often appears as rubber-banding, skipped movement, delayed updates, or a network-warning icon. Similar-looking problems include:
- Low FPS or frame-time spikes: the device is struggling to render.
- High ping: every packet arrives late, but packets may not be missing.
- Jitter: latency swings sharply from moment to moment.
- Server trouble: several players break at once while your local tests stay clean.
Check the publisher’s official service-status page. Then compare another online game. If one title reports loss while everything else is stable, focus on that game’s server region, current service health, or route, not the entire internet.
Also remember that a web packet-loss test uses its own destination and protocol.
1. Build a tiny test log
Before changing settings, write down:
- date and local time;
- game, mode, and selected server region;
- Wi-Fi or Ethernet;
- in-game ping, jitter, and loss;
- whether anyone was uploading or downloading;
- whether another game had the same symptom.
Collect at least one good session and one bad session. This converts “random lag” into a pattern your ISP or game support can investigate.
2. Test your local gateway
On Windows, open Command Prompt and run:
ipconfigFind Default Gateway, then send a longer sample to that address:
ping -n 200 YOUR_GATEWAY_IPExample:
ping -n 200 192.168.1.1Repeatable loss or large spikes here place the problem inside the home: the PC, Wi-Fi radio, cable, adapter, router, or local interference.
Some routers deprioritize ping replies, so interpret the result alongside the game symptom. If the gateway reports occasional missed replies but gameplay and later tests remain clean, the router may simply be rude to diagnostic traffic.
3. Compare Wi-Fi with Ethernet
Connect the gaming device directly to the router using a known-good Ethernet cable. Keep the same game, server region, and approximate time.
If the loss disappears on Ethernet, investigate Wi-Fi:
- move closer to the access point;
- use 5 GHz or 6 GHz at short range;
- move the router into the open;
- avoid a repeater in the gaming path;
- update the Wi-Fi adapter driver;
- test a less crowded channel;
- disable adapter power saving during one comparison.
Microsoft’s current Wi-Fi troubleshooting guide recommends isolating the device, frequency band, and network equipment rather than assuming the internet plan is the problem.
If you still have packet loss on Ethernet, try a second cable and router port. Then test another wired device. Loss on one PC suggests its adapter, driver, security filter, or software. Loss on multiple wired devices points farther upstream.
4. Pause traffic and test under load
Packet loss while gaming can appear when an upload queue fills. Common culprits include cloud backup, photo sync, livestreaming, video calls, security cameras, and game updates.
Pause those jobs, play the same mode, and compare. Then run a latency-under-load test with the network quiet and again while it is busy.
If loss and delay appear only under load, enable smart queue management or well-configured QoS on the router if supported. The useful feature is active queue control, not a plastic “GAMER” badge large enough to be seen from orbit.
Our guide to why games lag at night explains how to separate household load from evening ISP congestion.
5. Test beyond the router
With the local gateway clean, test a stable public destination:
ping -n 200 1.1.1.1Interpret the gateway and public results together:
| Gateway | Public destination | Next suspect |
|---|---|---|
| Lossy or spiky | Lossy or spiky | Device, Wi-Fi, cable, or router |
| Clean | Lossy or spiky | Modem, access link, congestion, or upstream path |
| Clean | Clean, one game bad | Game service, region, or game-specific route |
| Both clean, FPS drops | Not mainly network | Rendering, drivers, heat, or overlays |
One destination can be healthy while another route is not.
6. Use pathping carefully on Windows
Microsoft’s pathping combines route discovery with packet-loss measurement over time. Run:
pathping 1.1.1.1Let it finish. The command can take several minutes. Look for sustained loss that begins at one hop and continues through later hops.
Do not treat every asterisk or one lossy-looking intermediate hop as proof. Routers may limit or ignore diagnostic replies while forwarding normal traffic successfully. If a hop looks bad but every later hop and the destination are clean, transit is probably still working.
Microsoft documents the command and its timing in the current pathping reference.
7. Separate one game from all games
When you see packet loss only in games, split the category again:
- One game only: check its official status, selected region, current update notes, and support tools.
- All games, web browsing fine: test UDP-sensitive real-time traffic, household load, adapter drivers, and the ISP path.
- Games and voice chat fail together: suspect local loss, upload saturation, or a broader route issue.
- One device only: inspect that device’s adapter, driver, overlays, security software, and virtual network adapters.
Do not open random ports to fix packet loss. Port forwarding may affect inbound connectivity or NAT behavior, but it does not repair a weak radio signal or congested link. Likewise, changing DNS rarely changes packet delivery after a match is connected.
8. Check the modem and ISP evidence
If wired gateway tests are clean but public or game traffic repeatedly loses packets, record results over several days. Include exact times and whether the symptom affects multiple wired devices.
Reboot the modem or gateway once, inspect accessible cables for loose connections, and check the ISP’s outage page. Do not open provider equipment or touch outdoor lines.
Send support:
- wired gateway and public test results;
- the game’s loss reading;
- dates and time windows;
- affected devices and games;
- whether loss happens under load or while idle;
- a
pathpingresult, with the destination included.
“Three wired devices lose packets from 8:10-9:30 p.m.” is actionable. “My internet has bad vibes” is emotionally valid but difficult to escalate.
9. Run a controlled VPN route comparison
A VPN can help only when it replaces a poor upstream route. It cannot fix loss between your device and router, overloaded Wi-Fi, a saturated upload, or a struggling game server. The extra tunnel can also add latency.
Test only after the local path is clean:
- Choose a nearby VPN endpoint.
- Keep the same game region and mode.
- Play for 10 minutes without the VPN and record loss, ping, and jitter.
- Connect and repeat immediately.
- Reverse the order on another day.
- Keep the VPN only if the broken metric improves repeatedly.
Read does a VPN lower ping? for the honest route test and gaming VPN troubleshooting if the tunnel creates a different problem.
What not to do
- Do not disable the firewall permanently.
- Do not install mystery “packet booster” tools.
- Do not change MTU, DNS, drivers, and router settings at once.
- Do not assume a faster plan automatically changes routing.
- Do not call one missed ping a diagnosis.
- Do not use a VPN to bypass game rules or restrictions.
FAQ
Why do I have packet loss but a good speed test?
Speed tests emphasize throughput and may recover lost data through retransmission. Games use real-time traffic where missing or late packets are more visible. Test latency, jitter, and loss separately from download speed.
Is any packet loss bad for gaming?
Sustained loss can cause visible problems, especially in fast multiplayer games. A single missed diagnostic reply is not enough evidence because some devices deprioritize ping. Confirm the pattern over a longer sample and compare it with the in-game reading.
Why do I get packet loss only in one game?
The game may use a different server region, provider, or network route. Check its official service status, compare nearby official regions, and test another game before changing your home network.
Can Ethernet still have packet loss?
Yes. A damaged cable, bad router port, adapter driver, network filter, modem issue, congestion, or upstream route can affect a wired connection. Ethernet removes radio interference; it does not make every later hop perfect.
Can a VPN fix packet loss while gaming?
Sometimes, if it replaces a poor ISP route. It cannot repair local Wi-Fi, a faulty cable, full upload queue, or game-server trouble, and it may increase latency. Use repeated direct-versus-VPN comparisons.
If the local path is clean and the upstream route keeps dropping the ball, join the LagZero waitlist. When we launch, compare one nearby route with your normal connection. No zero-loss prophecy, just a fair rematch.