How to troubleshoot WiFi with high packet loss rate? The game was lagging and the voice lines were all awkward, so I used three pings to catch the real culprit
last Wednesday night while playing ranked matches, my character teleported a bit while walking, and my teammates said my voice chat was intermittent, like a radio with poor signal. I casually tested the speed—550 Mbps, very fast. Later, I realized—it wasn't speed that was stuck, but packet loss. These two are completely different matters, and many people have been fooled by the "normal speed test" for a whole year.
clarify first: packet loss and latency are two different things
delay is due to traffic jams; the bag is still on the road but arriving late; The lost package was simply lost by the courier and never even arrived.
why don't you notice packet loss when watching videos, and why is gaming so sensitive? Because downloading videos uses TCP, if lost, it will automatically retransmit, and at most you see a brief buffer in a circle. But the game's real-time sync uses UDP, no retransmission, and if a packet is lost, that frame is lost—this means characters teleport, skills not being released, voice lines missing words.
there's another counterintuitive thing: signal will lose packets even if the signal is full A full grid just means you're close to the router, not the air is clean. WiFi shares air, but interference, channel collisions, and routers overwhelmed can cause packets to be lost halfway. I once wrote a about WiFi full bars but still not online. Many people said the comments section was full but still laggy, and most likely the packet loss rate was excessive.
How is
packet loss rate calculated normally? The ruler I set for myself:
| packet loss rate | what to do | |
| 0~1% | no noticeable | ignore it |
| 2~5% | Occasional buffering in videos, occasional pauses in games | You can check but don't worry |
| 5%~10% | Obvious teleportation in games, Voice intermittent | must be checked for over |
| 10% of | web pages that are unresponsive | major issues such as hardware or line-level |
three pings, first shift the blame to the right place
the most basic but effective tool for packet loss is ping. Don't just stare at your phone—just open a command line on your computer.
Windows press Win+R, enter cmd and press Enter, then proceed in two steps:
ping -n 100 192.168.1.1
ping -n 100 223.5.5.5
send 100 packets, after running it will get statistics: 100 sent, 97 received, 3 lost, and 3% packet loss rate. Comparing the two commands, the blame is clear:
- ping the gateway (192.168.1.1) is lost—the problem is in your home, the WiFi segment or router itself
- the gateway is lost, ping 223.5.5.5 is lost—the problem is at the outlet, the optical modem, line, or carrier
- all lose it—first address the gateway section, step by step
want to see more details, you can use WinMTR (a free tool). Enter a target address like 223.5.5.5. It lists packet loss rate and latency for each hopping route, making it clear when the packet starts to be lost.
my test data from that night: Ping the gateway lost 11%, ping 223.5.5.5 lost 13%. Both segments are missing, and the numbers are close, which means the package was gone before you even left the house—what's inside has nothing to do with the carrier. If I had called for repair right away, I probably would've waited for the technician to come for nothing.
the gateway section, let's just throw it away: four suspects lined up one by one
Suspicion One: Weak signal. Don't look at the number of grids, look at the numbers. Install a WiFi analyzer app on your phone (search for it on Android and you'll find a bunch of them). Depending on the RSSI at the frequency point you're connecting to: use it anywhere below -60, -70 is the edge, and after -75, packet loss rates will increase sharply. 2.4G can still show "full bar" through two walls, which is a gesture from phone manufacturers, but the actual discount is 78. If the signal isn't enough, moving the router is better than anything. Don't put it in a weak current box or TV cabinet. In this router placement test I moved five locations, and the difference was about 20 dB.
Suspicion 2: Channel collision. This is the real culprit of that night. The router channel was set to automatic, and it picked 13 for itself. The building across from me also chose 13, and the two networks competed in the same lane. The 2.4G waveform in the WiFi analyzer overlaps like mountains. 2. 4G only has three channels that do not interfere with each other: 1, 6, and 11. Manually select the emptiest one. After switching channels, I pinged 100 packets again, and the packet loss rate dropped from 11% straight to zero, in less than two minutes. How to choose a channel: I previously wrote WiFi channel interference troubleshooting explained in detail, so I won't repeat it.
Suspect 3: Router overload. two signals: first, the running time. The router's backend homepage usually shows that mine ran for over 900 hours without restarting, and the cache and connection meter were already exposed; Second, bring a lot of devices. With so many smart devices at home, entry-level routers can't handle it. Switching off power and restarting is just a life-saving solution, not a cure. To prevent the router itself from becoming a bottleneck, I've broken down the two hardware indicators of CPU and memory in these two articles: Is the router's CPU important and how much memory is enough For those old machines that occasionally disconnect and get slower the more you use them, don't hesitate to replace them directly.
Suspicion Four: Source of interference. microwave is the number one killer of 2.4G—the entire spectrum is noisy during operation. If you put the router next to the kitchen, the whole house gets stuck during the few minutes of heating dinner at night. Next are Bluetooth devices and USB 3.0 hard drive enclosures. If the USB 3.0 interface and cable shielding are poor, harmonic interference can occur in the 2.4G band, as confirmed in the official white paper. Later, I moved the USB 3.0 drive enclosure next to the NAS half a meter away, and the 2.4G packet loss noticeably improved.
Gateway Not Lost, Public Network Lost: Don't Be Too Quick to Blame Carriers
If the ping gateway is clean but ping 223.5.5.5 is missing, do three things first before making a call.
First, plug in the network cable and ping again. Excluding WiFi issues, the real problem is the broadband side if the wired is lost. Second, compare with ping: if 223.5.5.5 is lost and 119.29.29.29 is not, it just gets congested on a certain path, and changing DNS can bypass it. Third, check for light degradation in the background via the light modem. Receiving light power from -8 to -27dBm is considered healthy; when it approaches -30, a fault report is needed. Fiber bending or dirty connectors will worsen light decay. How to read the indicator light and light power of the optical modem (ONT)? This article comprehensive self-check for the optical modem indicator light.
another situation is that during the evening rush hour, everything is lost and the area is clean in the second half of the night—this is shared bandwidth congestion in the area, your home cable is fine, but the main line in the hallway is crowded. When reporting a repair, bring a screenshot of your ping record: what time to, packet loss rate, and which ping address. For carriers, tickets with data and tickets for "My Home SIM Card" are two priorities.
fix the comparison table and the order I suggested
gather all these into a table and assign them accordingly:
| ping results | accompanied by features | most likely causes | actions |
| the gateway loses + signal below -75 | only lags in rooms far from the router | coverage is insufficient | move the router, switch to 5G, or Mesh |
| Gateway Lost + channel overlap | Worsened at night | neighbors collided with channels | Manually choose 1/6/11 |
| Gateway Drop + Runs for 900+ hours+ | gets slower the more you use it, reboots take several days | router overloads and ages | reboot to keep it alive, then replace the device when the time is right |
| public network loss + light degradation super-27 | LOS light occasionally flashes red | fiber optic issue | fault report, screenshot with light degradation |
| public network loss + evening rush hour pattern | normal recovery at midnight | congestion in the area | repair or package upgrade |
my processing sequence was four steps: first ping the gateway to separate the pot, then using the WiFi analyzer to check the signal and channel, then restarting the router to eliminate overload, and finally checking the optical modem and calling the carrier. The first two steps and five minutes can solve 80% of the lost packet problem at home. When it comes to changing machines, first think carefully about whether it's coverage or performance—no matter how expensive a single router is for poor coverage, it's useless; adding a node to set up Mesh is the right solution.
