What Is Packet Loss and How to Fix It
What is packet loss and how to fix it? Packet loss means some data packets fail to reach their destination. Confirm it with a repeated test, compare your router with an internet destination, then fix the layer where loss begins: Wi-Fi, cabling, router, ISP path, or the remote service.
What is packet loss and how to fix it
Packet loss is a delivery problem, not a speed rating. IP is best effort, so it does not promise that every packet will arrive; Microsoft explains that higher-level protocols may handle some loss. TCP can retransmit missing data, but real-time traffic may continue without it. That is why a fast download can coexist with frozen video, robotic audio, rubber-banding, or short disconnects.
| Metric | What it measures | What a bad result feels like |
|---|---|---|
| Download or upload speed | How much data can move at once | Transfers or streams cannot keep up |
| Ping | Round-trip time for a reply | Every action feels delayed |
| Jitter | How much the delay varies | Voice and gameplay become uneven |
| Packet loss | Packets that do not reach the destination | Missing updates, retries, freezes, or dropouts |
Loss is specific to a path and direction. A clean result to one destination does not prove that every game, call, or website has a clean route. A router that ignores probes may still forward traffic, so the destination and symptoms matter.
Measure packet loss before changing settings
Start with Loqmi's browser speed test from the problem room and device. Record it while the issue is visible, then repeat with other traffic paused. For a direct loss check, test your default gateway, a public destination, and the failing service.
- Run repeated pings to the gateway. Loss here points to the device-to-router link, Wi-Fi, an Ethernet cable, or the router itself.
- Run the same count to a public IP or hostname. If the gateway is clean but the public target loses replies, investigate the WAN, ISP, or route.
- Compare the result with the affected game, call platform, VPN endpoint, or website when it exposes a destination. Final-destination loss is not fixed by replacing Wi-Fi.
- Repeat during a quiet period and while the problem is happening, keeping the device, target, and connection type the same.
On Windows, ping /n 100 <target> sends a chosen number of echo requests; on macOS and Linux, ping -c 100 <target> does the equivalent. It is a sample, not a universal threshold. In Microsoft's sample pathping report, 13/100 = 13% means 13 lost probes on that link. The report distinguishes link loss from a router not answering probes sent to itself.
Find where the loss starts
| What you see | Most likely area | Next check |
|---|---|---|
| Loss to the gateway | Wi-Fi, cable, adapter, router, or local interference | Compare Ethernet with Wi-Fi and try another cable or port. |
| Gateway is clean; several public targets lose replies | Modem, access line, ISP, or upstream routing | Repeat wired tests and keep the times and destinations. |
| Only one service or game is affected | That service, its route, or a destination-specific policy | Compare another destination and use the service's own status or network display. |
| Loss appears at one middle hop, but later hops are clean | Often ICMP rate-limiting or deprioritisation | Do not blame that router unless the loss continues through the final destination. |
| Loss appears only while the connection is busy | Queueing, congestion, or an overloaded router | Pause uploads and downloads, then test again under the same load. |
Windows users can use pathping /n <target> after a simple ping. It combines a route trace with repeated probes and reports loss for hops and links, but takes time. On other systems, traceroute <target> or MTR can show the path. Treat a single intermediate-hop result as a clue, not a diagnosis.
Fix common home-network causes
- Use Ethernet as a control. A short wired test removes radio interference, distance, and most Wi-Fi contention. If loss disappears, see how to fix slow Wi-Fi and compare 2.4 GHz with 5 GHz for the room and device.
- Check the physical path. Reseat Ethernet plugs, replace a damaged cable, and try another router port. For cable or DSL service, check that the modem's wall connection is seated; do not open provider equipment.
- Remove congestion. Pause backups, game updates, large uploads, and unnecessary streams. If loss returns only when the household is busy, enable documented queue-management or QoS and re-test.
- Restart and update. Power-cycle the modem and router, then check the manufacturer's support page for firmware. Follow the model's instructions and do not interrupt an update.
- Change one variable at a time. DNS can repair name-resolution failures, but it cannot repair dropped packets. A VPN changes the route and may help one destination, while a manual MTU change is appropriate only when testing shows a path-MTU problem. Neither is a general packet-loss cure.
Check the affected device
Windows 11
Open Start > Settings > Network & internet > Wi-Fi or Ethernet, then run the gateway and public-target pings in Terminal or Command Prompt. If the adapter still misbehaves, use Start > Settings > Network & internet > Advanced network settings > Network reset only as a last resort; Microsoft warns that it reinstalls adapters and may require VPN or virtual-switch setup again.
macOS
Check Apple menu > System Settings > Network > Wi-Fi. For built-in diagnosis, hold Option, click the Wi-Fi status menu, and choose Open Wireless Diagnostics. In Terminal, run ping -c 100 <gateway>, then traceroute <target>. Wireless Diagnostics analyses the connection without changing settings.
Linux
Menu names depend on the distribution. On Ubuntu Desktop with GNOME, use Settings > Wi-Fi > your connected network > Network Options (gear) > IPv4 Address, or open Activities and search for Wi-Fi to forget a saved network. In Terminal, use ip route, then ping -c 100 <gateway> and traceroute <target>. Ubuntu documents this GNOME path.
Android
Open Settings > Network & internet or Connections > Internet/Wi-Fi, then tap the network. Forget and rejoin it before resetting settings; Google notes that labels vary by manufacturer. Run Loqmi in the affected room and repeat near the router. Android has no uniform desktop ping workflow.
iPhone and iPad
Open Settings > Wi-Fi and tap the network. Rejoin it first. As a last resort, use Settings > General > Transfer or Reset iPhone/iPad > Reset > Reset Network Settings; Apple says this removes saved Wi-Fi networks and passwords plus cellular, VPN, and APN settings. Use Loqmi for comparison.
Know when to contact the ISP
Contact the ISP when loss persists on Ethernet, affects multiple devices, reaches several destinations, and remains after a restart. Send timestamps, wired-versus-Wi-Fi results, gateway and public-target summaries, and the affected service. If only one service fails, report that evidence there instead. Your gaming ping and packet-loss results are more useful than a speed number alone.
Ask the ISP to investigate the access line, modem status, or upstream path; one unresponsive router is not proof. If the problem follows a busy household or large upload, reduce the load and check whether the router can manage queues. If Ethernet is healthy but one room is not, focus on Wi-Fi.
Avoid common misreads
| Claim | Better rule |
|---|---|
| “My speed is high, so I cannot have packet loss.” | Capacity and delivery consistency are different; test both. |
| “Any loss percentage is equally serious.” | Impact depends on the application, whether loss is sustained or bursty, and whether it reaches the final destination. |
| “The first hop with red numbers is broken.” | Only loss that continues to the destination is strong evidence of transit loss. |
| “Changing DNS is the universal fix.” | DNS affects lookups; it does not repair Wi-Fi interference, a bad cable, or a congested path. |
Key takeaways
- Packet loss is missing delivery, not simply slow speed; it can disrupt real-time traffic even on a fast plan.
- Test the gateway, a public destination, and the affected service, then compare Wi-Fi with Ethernet.
- Use current Windows 11, macOS, Ubuntu, Android, and iOS paths before resorting to a network reset.
- Ignore isolated intermediate-hop loss and escalate repeated end-to-end loss with timestamps and test evidence.
Frequently asked questions
Can a VPN fix packet loss?
Sometimes, but only when the loss is on the route to a particular service and the VPN uses a better path. A VPN cannot repair a damaged cable, weak Wi-Fi, overloaded router, or loss that happens before the VPN server. Compare the same destination with and without the VPN, and keep it off while diagnosing your home network.
Is packet loss the same as slow internet?
No. Slow internet usually means limited capacity or high latency; packet loss means some packets never arrive. They can happen together when a link is congested, but a fast speed test does not rule out intermittent loss. Look at repeated delivery tests and the symptoms of the specific activity, not download speed alone.
Why does packet loss happen only at certain times?
Time-of-day patterns often point to congestion: someone may be uploading, downloading, or streaming at home, or your provider may be busiest during peak hours. Compare a quiet-period test with a test while the problem is happening, using the same device, connection type, and destinations. If only peak hours are affected, save those timestamps for the ISP.
How long should I run a packet-loss test?
Use enough probes to catch the problem without creating extra traffic, then repeat during both a good period and a bad period. A short test can miss bursty loss. For intermittent problems, run a longer trace while the app is affected and record the destination, connection type, time, and whether loss reaches the final destination.
Sources
- Microsoft Learn: Diagnose packet loss
- Microsoft Learn: ping command
- Microsoft Learn: pathping command
- Microsoft Support: Fix Wi-Fi connection issues in Windows
- Apple User Guide: Use Wireless Diagnostics on your Mac
- Apple Support: If you can't connect to Wi-Fi on your iPhone or iPad
- Android Help: Fix internet connection problems on Android devices
- Ubuntu Desktop documentation: Network settings on Ubuntu 24.04