How to Fix Packet Loss

1. Test your packet loss first

Before moving furniture or adjusting router settings, run the live speed test tool above to capture your baseline network health. Packet loss cannot be diagnosed by looking at download speed alone. Pay attention to all four core transmission metrics:

• Packet loss (percentage): The share of transmitted packets that failed to return. A stable connection maintains exactly 0% packet loss. Sustained packet loss above 1% causes audible voice clipping and online gaming rubber-banding.
• Ping / Latency (milliseconds): The time required for a packet to travel round-trip to the test server. High baseline ping often accompanies severe packet loss.
• Jitter (milliseconds): The variation in packet delivery timing. Sudden spikes in jitter frequently indicate that your router or wireless link is struggling right before packets start getting discarded.
• Download and upload bandwidth (Mbps): Verifies that your connection is delivering the throughput you pay for.

Always run the test at least three consecutive times when the network is quiet, and then repeat the test while normal household streaming or downloading is taking place. Want to measure your connection first? Run a packet loss test to capture your initial numbers.

2. Find where packet loss is happening

To permanently resolve packet loss, you must determine which physical link in the network chain is discarding your data. Data packets travel through multiple discrete stages between your computer and a remote game or conference server:

Each point in this chain presents distinct failure modes:

• Your device: Outdated network adapter drivers, third-party firewall software, background sync engines, or aggressive power-saving modes can drop packets before they reach your local network adapter.
• Wi-Fi or Ethernet: Radio frequency interference, wall obstacles, crowded 2.4 GHz channels, damaged copper pins, or kinked Cat5e/Cat6 patch cords cause physical transmission corruption.
• The router: An overheating processor, memory leaks from months of uptime, or full queue buffers under heavy simultaneous traffic force the router to drop incoming packets (tail drop).
• The modem or Optical Network Terminal (ONT): Poor coaxial line signal levels (DOCSIS downstream/upstream power imbalance, low Signal-to-Noise Ratio), corrupted optical fiber connectors, or hardware overheating cause carrier-level frame drops.
• The ISP access network: Damaged outdoor tap connections, water intrusion in neighborhood underground vaults, or overloaded neighborhood nodes during peak evening hours (7:00–11:00 p.m.) degrade packets across entire streets.
• Upstream internet transit & destination servers: Congested peering points between major telecom backbones or an overloaded game server cluster can drop packets even when your local home connection is pristine.

3. The fastest way to narrow down packet loss

Rather than guessing which component is broken, use targeted comparative testing. By changing one environmental factor at a time, you can narrow down the exact source of your packet loss in minutes:

4. How to fix packet loss: Step-by-step sequence

Follow this troubleshooting sequence in order. Start with the simplest, zero-cost fixes before moving on to hardware inspections and ISP escalation:

1. Run a baseline packet loss test: Measure your current packet loss percentage on the live tool above while your home network is idle. Note down your packet loss, ping, and jitter.
2. Stop background downloads and updates: Pause active game updates on Steam, Battle.net, PlayStation, and Xbox consoles, as well as Windows Update downloads. Uncapped background transfers saturate packet queues.
3. Pause cloud backup and file syncing: Applications like iCloud Photo Sync, Google Drive, OneDrive, and Dropbox continuously upload files in the background. Because home upload speeds are much smaller than download speeds, cloud sync can choke outgoing packet acknowledgments.
4. Close bandwidth-heavy applications: Shut down torrent clients, streaming capture software, and peer-to-peer applications running in your system tray.
5. Restart your router and modem: Unplug both devices from wall power, wait 60 seconds for internal capacitors to fully discharge, and plug the modem back in first. Once the modem shows solid connection lights, power on your router. This clears memory fragmentation and resets internal routing tables.
6. Inspect Ethernet cables and physical connectors: Check RJ45 connectors on all patch cables between your computer, router, and modem. Make sure the plastic retaining clips click firmly into place. Replace cables with visible kinks or cracked outer jackets.
7. Try a different Ethernet LAN port on your router: Router switch ports can fail individually due to electrical surges or physical wear. Move your patch cable to an adjacent LAN port.
8. Test with a direct Ethernet cable instead of Wi-Fi: Connect your device directly to your router with a Cat5e or Cat6 patch cord. If packet loss drops to 0%, your local Wi-Fi environment was the culprit.
9. Improve Wi-Fi signal and router placement: If you must remain on Wi-Fi, move your router to an elevated, central location away from floors, metal filing cabinets, and concrete walls.
10. Reduce wireless interference: Steer your device away from the crowded 2.4 GHz band to the 5 GHz or 6 GHz frequency band. Keep the router away from 2.4 GHz cordless phones, microwave ovens, and Bluetooth hubs.
11. Check whether multiple household devices are saturating bandwidth: Check your router’s traffic monitor to see if another device is downloading 4K video or uploading large media files without your knowledge.
12. Update router firmware: Log into your router’s web administration panel and install the latest vendor firmware update to fix known network driver bugs and memory leak vulnerabilities.
13. Enable Smart Queue Management (SQM): If your router supports SQM (such as FQ-CoDel or CAKE), turn it on to prevent packet queues from filling up under load.
14. Test a second device on the same connection: Connect a laptop, smartphone, or tablet and run the packet loss test. If the second device shows 0% loss, the problem is isolated to your primary device’s network card or software.
15. Test at different times of day: Compare packet loss at 9:00 a.m. (off-peak) versus 8:00 p.m. (peak evening hours). Time-dependent loss indicates neighborhood node congestion on your provider’s network.
16. Check whether packet loss happens across multiple destinations: Run tests to multiple public endpoints. If loss only occurs when connecting to one specific multiplayer game, the problem is server-side or path-specific.
17. Contact your ISP when evidence demonstrates an upstream fault: If packet loss persists on a direct, quiet wired connection across multiple devices and times of day, contact your provider with documented test logs.

5. How to fix packet loss on Wi-Fi

Wi-Fi is the single most common cause of packet loss in residential environments. Wireless networks transmit data over unlicensed radio frequencies that are easily corrupted by distance, physical obstacles, and electromagnetic noise. When a wireless frame is corrupted in transit, the receiving antenna discards it, manifesting as packet loss in real-time applications.

To eliminate packet loss on Wi-Fi without running long cables across your home:

• Switch from 2.4 GHz to the 5 GHz or 6 GHz band: The 2.4 GHz band is crowded with Bluetooth devices, microwave ovens, baby monitors, and dozens of neighboring Wi-Fi networks. It also has only three non-overlapping channels (1, 6, and 11). The 5 GHz and 6 GHz bands offer wider, cleaner channels with virtually zero household radio interference.
• Understand the distance tradeoff: Higher frequency bands (5 GHz and 6 GHz) deliver higher throughput and less interference, but their shorter wavelengths attenuate rapidly through solid walls, brick, and metal lath. If your gaming console or desk is several rooms away, 5 GHz signal strength may drop below -70 dBm, triggering packet loss. In that scenario, move closer to the router or add a wired access point.
• Select a clean wireless channel: Use a free Wi-Fi analyzer app on your smartphone or laptop to scan nearby access points. If multiple neighbors are broadcasting on channel 6, manually configure your router to channel 1 or 11 in your router’s wireless settings.
• Elevate your router: Place your wireless router at least 3 to 5 feet off the floor on an open table or shelf. Placing a router inside a closed entertainment center, behind a large TV, or near thick metal ductwork severely degrades antenna radiation patterns.
• Limit legacy devices: Old 802.11b/g Wi-Fi devices force modern routers to reserve extra transmission airtime for slow packets, increasing the risk of frame collisions and queue drops for all other connected devices.

Remember: If packet loss completely vanishes when you plug in a wired Ethernet cable, your wireless environment is undeniably part of the problem. For competitive gaming and vital work calls, a wired connection is always the most dependable solution. Learn more about testing wireless performance with our Wi-Fi speed test.

6. How to fix packet loss on Ethernet

While wired Ethernet is significantly more reliable than Wi-Fi, it is not impervious to physical damage and hardware faults. When packet loss occurs over an Ethernet connection, the issue is almost always a physical layer defect or network interface configuration issue:

• Damaged copper pairs or loose retention clips: Ethernet patch cables contain eight tiny copper wires twisted into four pairs. If a cable has been stepped on, bent sharply around doorframes, or pinched under furniture, internal copper strands can fracture. If the plastic retaining tab on the RJ45 connector is broken, the plug will wiggle in the jack, causing intermittent packet drops.
• Verify link speed negotiation: Open your operating system’s network adapter settings and inspect your connection speed. A standard gigabit connection should display 1,000 Mbps (1 Gbps) Full Duplex. If your adapter has fallen back to 100 Mbps or 10 Mbps Half Duplex, your cable has lost connection on one or more internal pairs and must be replaced.
• Use quality Cat5e or Cat6 cables: Avoid unbranded, ultra-thin flat cables or aged Cat5 cords that lack proper shielding and twist ratios. Standard Cat5e or Cat6 cables support full gigabit speeds with minimal crosstalk over distances up to 100 meters (328 feet).
• Switch router LAN ports: Individual Ethernet switch ports on home routers can degrade due to electrostatic discharge or cracked solder joints. Move your cable into an adjacent LAN port to rule out a localized port hardware defect.
• Update Network Interface Card (NIC) drivers: Outdated or corrupted network drivers can drop incoming packets at the operating system level. Download the latest official drivers directly from your motherboard or computer manufacturer’s support portal.

7. Can your router or modem cause packet loss?

Yes. Your home router and modem are dedicated computers with their own microprocessors, memory chips, and operating systems. When this equipment struggles under hardware or software stress, packet loss is an immediate symptom:

• Overheating and thermal throttling: Routers generate substantial heat. When placed in enclosed cabinets, stacked directly on top of warm modems, or covered in dust, internal chips throttle clock speeds or malfunction, dropping packets during heavy traffic. Ensure equipment has adequate ventilation.
• Memory exhaustion and state table saturation: Cheap or aging routers have limited RAM. When dozens of household devices maintain thousands of concurrent stateful NAT connections (from peer-to-peer transfers, IoT equipment, and gaming), the router’s memory exhausts and newly arriving packets are dumped.
• Coaxial line signal degradation (Cable Modems): If you use cable internet, log into your modem’s diagnostic page (typically accessible at 192.168.100.1) and examine your downstream power levels, upstream power, and Signal-to-Noise Ratio (SNR). Excessive “Uncorrectable Codewords” indicate physical line noise, loose coaxial splitters, or corroded outdoor drops that require an ISP technician.
• The direct modem bypass test: To confirm whether your router is the source of packet loss, connect a computer directly to your standalone modem or fiber ONT with an Ethernet cable (restart the modem so it assigns a public IP to your computer). Run the packet loss test. If loss drops from 5% to 0%, your router hardware or router configuration was the bottleneck.

8. Reduce packet loss caused by network congestion

Network congestion occurs when the volume of data your household attempts to send or receive exceeds the physical throughput of your connection or router processor. It is important to distinguish between connected devices and active bandwidth consumers:

Having 30 smart light bulbs and smart plugs connected to your Wi-Fi network does not cause packet loss, because idle smart devices transmit tiny, intermittent heartbeat packets measured in kilobytes. In contrast, two active users can completely overwhelm a high-speed connection if one user is uploading raw video footage to YouTube while another downloads a 100 GB game patch.

Because residential internet connections are asymmetric—offering significantly less upload bandwidth than download bandwidth—upload saturation is especially dangerous. When your upload bandwidth fills up completely, outgoing TCP acknowledgment packets (ACKs) are delayed or dropped. When remote servers stop receiving ACKs, they assume data was lost and halt downstream transmissions, causing severe stutter across your entire home network. Pause active cloud backups and uncapped file uploads whenever stability is critical.

9. Can bufferbloat cause packet loss?

Yes. Bufferbloat is the excessive latency and packet delay that occurs when a router buffers too much data in an attempt to prevent packet drops. When network traffic surges, standard home routers place packets into deep internal queues. While buffering prevents immediate packet loss during minor traffic spikes, oversized queues cause latency to skyrocket from 20 ms to hundreds or even thousands of milliseconds.

Once a router’s queue buffer is completely filled, any newly arriving packets cannot be held and are immediately discarded. This is known as tail drop. When bufferbloat reaches this tipping point, users experience both massive latency spikes and severe packet loss simultaneously.

To eliminate bufferbloat-induced packet loss:

• Enable Smart Queue Management (SQM): Modern routers running SQM algorithms—such as FQ-CoDel or CAKE—replace deep, dumb queues with intelligent packet scheduling. SQM dynamically prioritizes lightweight, latency-sensitive packets (gaming inputs, VoIP audio) ahead of bulk file downloads, keeping packet queues lean and virtually eliminating tail drop.
• Set Quality of Service (QoS) bandwidth limits: If your router lacks SQM, standard QoS settings allow you to cap maximum download and upload bandwidth to 85%–90% of your tested line speed. Preventing your connection from reaching 100% saturation stops internal buffers from overflowing.

To see if bufferbloat is affecting your connection under load, check our detailed bufferbloat test and read our comprehensive explainer on what is bufferbloat.

10. How to fix packet loss while gaming

Online multiplayer games are uniquely vulnerable to packet loss because they rely on real-time UDP (User Datagram Protocol) packets. Unlike web pages or streaming video, games cannot wait for lost packets to be resent. Every game tick must deliver real-time player coordinates, hit registration, and physics updates. When packets are lost in transit, the game engine is forced to interpolate player positions, resulting in:

• Rubber-banding: Your character teleports backward to a position from two seconds ago.
• Desynchronization and unregistered hits: Shots fired on your screen never register on the server.
• Abrupt disconnections: The game server assumes your client has timed out and kicks you from the match.

Crucially, fast download speed and low ping do not guarantee zero packet loss. You can have a 1,000 Mbps fiber connection with a 15 ms ping and still experience 5% packet loss if your local Wi-Fi drops frames or an intermediate transit route is congested.

To fix gaming packet loss:

1. Always connect your gaming PC or console via wired Ethernet.
2. Close background game launchers (Steam, Epic, EA App, Battle.net) and stop peer-to-peer game update sharing.
3. Select game servers geographically closer to your physical location in your game’s matchmaking settings.
4. Check the official server status page or community channels (Discord, Reddit, X) for the game you are playing to verify if the issue is a known game server outage.
5. Explore our dedicated guide on internet speed for gaming, and check your latency with the ping test and jitter test.

11. How packet loss affects video calls

Real-time conferencing applications like Zoom, Microsoft Teams, and Google Meet use advanced audio and video codecs designed to conceal minor packet loss. Through algorithms known as Packet Loss Concealment (PLC), these apps interpolate missing audio syllables to keep conversations intelligible.

However, when packet loss climbs above 1% to 2%, concealment algorithms break down, producing unmistakable call quality defects:

• Robotic and metallic audio: Voices sound digitized and clipped as syllables are discarded.
• Frozen video feeds: Video frames pause or drop to low-resolution pixelated slides while audio continues.
• Dropped call connections: The conference platform displays “Your internet connection is unstable” before disconnecting the call entirely.

According to Microsoft’s official Teams network requirements, real-time audio calls require packet loss to remain strictly below 1% for professional communication quality. If you experience call drops during work meetings, switch to a wired Ethernet connection, disable background camera uploads on cloud drives, and review our recommendations on internet speed for video calls.

12. Can a VPN fix packet loss?

A Virtual Private Network (VPN) can sometimes fix packet loss, but only under one very specific set of circumstances: when the packet loss is occurring along an upstream transit peering route between your ISP and the destination server.

When you enable a VPN, all your traffic is encrypted and routed directly to the VPN provider’s data center before heading out to the broader internet. If your ISP’s standard route to a specific game or service passes through a congested or damaged carrier exchange point, the VPN route may bypass that problematic hop entirely.

However, a VPN cannot fix:

• Local Wi-Fi radio interference or weak signal strength
• Damaged Ethernet cables or loose wall jacks
• Overheated or crashing home routers
• Physical line noise on your outdoor coaxial or fiber drop

In fact, because VPNs add encryption overhead, increase packet header size, and route data through additional network hops, they can sometimes introduce new packet loss and increase baseline latency. To find out if a VPN helps your situation, run the packet loss test with the VPN completely turned off, then enable the VPN and test again across multiple runs. Keep the VPN active only if it consistently produces lower packet loss for your destination.

13. What if packet loss is coming from your ISP?

Not all packet loss can be solved inside your home. If you have systematically tested and eliminated every local variable, the failure is taking place on your provider’s physical access line or regional routing infrastructure. The key indicators that your ISP is responsible include:

• Packet loss persists when testing a computer plugged directly into the modem via a brand-new Ethernet cable with all Wi-Fi disabled.
• Packet loss affects every device in your household equally.
• Packet loss occurs consistently across multiple unrelated public test servers and websites.
• Packet loss follows a predictable daily schedule, spiking during peak evening hours (7:00–11:00 p.m.) and clearing up late at night.

14. What if packet loss happens in only one game or app?

If the live packet loss test on this page shows clean 0% loss, your video calls run smoothly, and web browsing is instantaneous, but you experience heavy packet loss in one specific game or application, your home internet connection is almost certainly fine.

Single-service packet loss typically indicates one of two external issues:

• Server-side overload: The specific game server cluster or matchmaking host you are connected to is experiencing hardware saturation, a DDoS attack, or routine maintenance.
• Peering route congestion: Your ISP’s network connection to the specific data center hosting that service passes through a congested third-party transit exchange point. In this scenario, selecting an alternate server region in the game’s settings or temporarily using a reputable gaming VPN can re-route your packets around the congested link.

15. How to know whether packet loss is fixed

Network troubleshooting requires scientific discipline. Never change five settings simultaneously, because if packet loss disappears, you will not know which change fixed it—and if packet loss worsens, you will not know what broke.

Use this five-step controlled verification process:

1. Establish a baseline: Run the packet loss test above three times on a quiet network and record your average loss percentage, ping, and jitter.
2. Change exactly ONE variable: Plug in an Ethernet cable, swap a patch cord, or pause a background upload. Do not touch any other equipment.
3. Retest immediately under identical conditions: Run the packet loss test three times and compare the new numbers directly to your baseline.
4. Verify under normal network load: Once idle packet loss is resolved, perform a loaded test while streaming or gaming to confirm the connection holds under pressure.
5. Repeat during peak hours: Run tests during peak evening hours (7:00–11:00 p.m.) to confirm that the fix holds when neighborhood network congestion is highest.

16. Packet loss vs. ping vs. jitter

Understanding how packet loss compares to latency and jitter helps you quickly identify which network property is causing issues with your connection:

17. What is a good packet loss percentage?

Because packet loss represents missing information, lower is always better. While web browsing can gracefully handle minor packet loss via background TCP retries, real-time interactive applications require near-zero loss for smooth operation:

• 0% Packet Loss (Ideal / Optimal): The gold standard for home broadband. Packets arrive completely intact with zero retransmissions. Online games run without rubber-banding, and video conferences remain crystal clear.
• 0.1% to 1.0% Packet Loss (Acceptable for browsing, marginal for gaming): Barely perceptible during everyday web browsing and streaming video. However, competitive gamers may notice occasional micro-stutters or delayed hit confirmations, and voice calls may experience subtle audio clicks.
• 1.0% to 3.0% Packet Loss (Problematic): Highly disruptive to real-time traffic. Voice audio cuts out noticeably on Zoom and Microsoft Teams, games suffer from frequent rubber-banding, and web pages occasionally require manual refreshes.
• Above 3.0% Packet Loss (Critical / Unstable): Severely impaired connection quality. Frequent disconnections from multiplayer game lobbies, dropped voice calls, frozen video streams, and failed file transfers. Immediate hardware inspection or ISP ticket submission is required.

18. Advanced packet loss troubleshooting

For technically inclined users on Windows, macOS, or Linux, operating system command-line utilities provide granular diagnostic visibility into where packets are being dropped:

Important caution on interpreting traceroute results: Many commercial backbone routers are explicitly configured to rate-limit or completely ignore ICMP echo request packets to protect their CPUs from overload. If hop 4 displays 100% packet loss (or asterisks) but hop 5 and all subsequent hops show 0% loss, that intermediate router is simply rate-limiting diagnostic pings—it is not dropping actual user data packets. Packet loss is only genuine if it persists across every subsequent hop all the way to the final destination.

19. Quick packet loss fix checklist

Keep this actionable checklist handy whenever you need to troubleshoot packet loss:

• [ ] Run a baseline test on the tool above and record your packet loss percentage.
• [ ] Switch your computer or console from Wi-Fi to a wired Cat5e/Cat6 Ethernet cable.
• [ ] Pause all active game downloads (Steam, console updates) and torrents.
• [ ] Pause background cloud file synchronization (iCloud, OneDrive, Google Drive).
• [ ] Unplug your modem and router for 60 seconds to clear congested memory buffers.
• [ ] Inspect Ethernet patch cords for damaged clips or sharp physical kinks.
• [ ] Move your Ethernet patch cable to a different LAN port on your router.
• [ ] If using Wi-Fi, steer devices to the 5 GHz or 6 GHz frequency band.
• [ ] Move your router to an elevated, open central location away from metal and concrete.
• [ ] Check for bufferbloat and enable Smart Queue Management (SQM) in router settings.
• [ ] Update your router firmware and PC network adapter drivers.
• [ ] Test with a second device to confirm whether the problem is device-specific.
• [ ] Connect your computer directly to the standalone modem to bypass the router.
• [ ] Compare packet loss during morning off-peak hours versus peak evening hours.
• [ ] Contact your internet service provider with documented test logs if wired packet loss persists.

20. Where to go next

Now that you have tested your packet loss and worked through the diagnostic steps, explore our companion guides to keep every part of your connection performing at its peak:

• Measure dedicated UDP loss: Run our high-accuracy 1,000-packet test on the packet loss test.
• Stabilize latency fluctuations: Learn how to stop lag spikes and packet delay variation on how to reduce jitter.
• Lower your connection ping: Optimize gaming responsiveness with our practical guide on how to reduce ping.
• Diagnose queue bloat under load: Test how your connection behaves under heavy traffic on the bufferbloat test.
• Optimize overall broadband performance: Discover proven hardware and software optimizations on how to improve internet speed.
• Troubleshoot severe slow-downs: Work through our step-by-step resolution tree on how to fix slow internet.