Insights

How to Reduce Packet Loss

Reduce packet loss with controlled Wi-Fi, Ethernet and congestion tests. Learn how to measure results, apply targeted fixes and escalate persistent issues.

How to Reduce Packet Loss: Ethernet wall socket with bent contacts, with the doxxnet wordmark.
On this page

To reduce packet loss, pause bandwidth-heavy background transfers, compare Wi-Fi with an Ethernet connection, and check your cables and router ports. Measure loss before and after each change. If it persists, test for congestion, update supported network drivers and router firmware, and look at the affected service or your ISP connection. Fix the segment your tests point to. Don't assume a faster internet plan will solve it.

In short:

  • Start simple: pause transfers, try Ethernet, swap the cable.
  • Measure first: look at loss while the problem is happening, not afterward.
  • Change one thing at a time, and retest the same way.

Start with reversible fixes and retest

Begin with changes you can easily undo, then repeat the activity that showed the problem. Keep the application, destination and network load as similar as you can, so the comparison actually tells you something.

  1. Record the symptom. Note whether you see broken voice, stalled video, game disconnects or a packet-loss reading inside the application. Write down when it happens and whether other devices are affected.
  2. Pause competing transfers. Stop downloads, uploads, cloud backups and other nonessential traffic you control. Closing bandwidth-heavy background applications is a practical first step when congestion may be involved.
  3. Compare Wi-Fi with Ethernet. Test the same device and application over a wired connection. Improvement on Ethernet points toward Wi-Fi interference, distance or a weak signal, not immediately toward your internet service.
  4. Check the physical connection. Reseat the cable, then try a known-good cable or a different router port. Change these one at a time so you know which swap helped.
  5. Restart your own router if practical. Warn other users first, since a restart interrupts their connections and any remote sessions. Restarting means rebooting the device. It isn't the same as a factory reset, which erases the configuration.

An improvement gives you a lead, not a confirmed cause. If pausing transfers helps, look at load. If Ethernet helps, look at Wi-Fi. If nothing changes, set a baseline (next section) before you make broader changes.

Measure loss while the problem is happening

Packet loss means packets never reach their destination. Latency is how long traffic takes to travel. Jitter is how much that delay varies. A connection can have high latency or uneven timing without any packet loss, so record these separately.

  1. Start with the affected application. Turn on its network statistics if it has them, and watch while the symptom occurs. That ties your measurement to the traffic you actually need to fix.
  2. Choose comparison targets that respond. Test your local gateway, a public endpoint and the affected endpoint where you're permitted to. Comparing several targets, including the gateway and the application endpoint, helps separate local connectivity from wider problems.
  3. Repeat and record. Save the destination, time, connection type, sent and received counts, reported loss and latency. Compare samples from symptom periods with quiet ones, and watch for longer if the problem comes and goes.

Run a short Windows sample

In Windows Command Prompt, this command sends 50 pings to Cloudflare's server:

ping -n 50 1.1.1.1

For your gateway, find the default gateway address in your active network adapter's connection details, then replace YOUR_GATEWAY_ADDRESS with it:

ping -n 50 YOUR_GATEWAY_ADDRESS

Ordinary ping needs no administrator rights and changes no settings, so there's nothing to undo. Only run it against destinations you're authorized to test, and press Ctrl+C to stop it.

Ping measures replies to diagnostic traffic, not every packet your application uses. A problem limited to a game or real-time application may not show up in ping, and a target that doesn't answer may simply be refusing diagnostic requests. Endpoint loss together with application symptoms is a stronger reason to investigate than either one alone.

Separate device and Wi-Fi faults from upstream problems

The most useful next test depends on which devices and destinations are affected. Compare results under similar conditions, and treat each pattern as a lead, not proof.

What you seeWhere to lookNext test
Loss on Wi-Fi gets better on EthernetWireless signal, interference or the wireless adapterRepeat the same application test near the router, then try another device
Loss affects only one deviceThat device's adapter, software or local connectionSwap its cable and port separately, then compare another device on the same network
Several internet targets show loss, but the gateway stays cleanThe shared internet connection or paths beyond the gatewayRepeat wired tests on another device and compare quiet with busy periods
Only one application or destination is affectedThe application, the destination service or its pathCheck that application's statistics and the service status, then test other destinations

Wi-Fi interference becomes a useful lead when wired tests improve under similar conditions. If loss continues on Ethernet, focus on the device, cable, port and upstream checks. Keep swaps controlled: changing the device and the cable together makes it hard to know which one mattered.

Traceroute or MTR can show where diagnostic replies stop or slow down, but they don't automatically point to a faulty router. Some routers limit how often they send ICMP TTL Exceeded responses, so one intermediate hop timing out can just be rate-limited diagnostics, not lost traffic.

Look for loss that persists at the destination and matches what the application is doing before you blame a router or ISP. Keep your router's protection and firewall on while you test. Connecting an unprotected device straight to a modem isn't a necessary troubleshooting step.

Reduce competing traffic before tuning QoS

If loss shows up under load, cutting traffic is a sensible next step. Too much traffic can overload a network and cause packet loss, but extra delay during a busy period doesn't by itself mean packets are going missing.

  1. Compare quiet and busy conditions. Repeat your application and endpoint tests with bulk transfers paused, then compare with the conditions that normally trigger the issue.
  2. Cap or schedule nonessential traffic. Move cloud backups and large transfers away from calls and other real-time work. Count uploads as well as downloads when you look at what's competing for the connection.
  3. Consider supported QoS or queue management. Quality of Service (QoS) divides limited capacity among types of traffic. It doesn't create more bandwidth. If your router supports it, follow its documentation and prioritize the real-time traffic you care about.
  4. Save, change and compare. Record the original settings, change one policy, then rerun the same tests. Compare application network statistics with QoS on and off, and revert if things get worse.

If stopping a backup improves both the application and its loss reading, scheduling or limiting that transfer is a targeted fix. If only latency improves, you've reduced delay but haven't shown that you reduced packet loss. And if loss continues during quiet periods, cable, port and adapter swaps will tell you more than adjusting traffic priorities again and again.

Update or replace only the components your tests implicate

Software updates and hardware replacement help most after controlled tests have narrowed the problem to one device or link. Replacing a router before checking the cable, adapter and affected destinations can leave the real fault untouched.

  1. Follow the swap results. If a known-good cable repeatedly makes the symptom disappear and the original cable brings it back, replace that cable. Apply the same logic to a port or adapter, and confirm it across comparable tests.
  2. Use supported software channels. Get network drivers and router firmware from the vendor's supported download channel. If symptoms began after a driver update, consider the vendor-supported way to roll back and compare the earlier version.
  3. Prepare for router changes. Go ahead only if you own the router or have administrator permission, you have local access and you've saved its configuration. Read the manufacturer's recovery instructions first, and never interrupt the power or the update.
  4. Follow firmware instructions exactly. Manufacturer guidance may require extra steps after an update, including restoring defaults. Treat that as a specific maintenance requirement. It isn't a reason to factory-reset every connection with packet loss.
  5. Inspect documented interface counters if you can. Technical users can check whether interface errors climb during the symptom. Read the counters using the device's documentation and alongside your swap results. They're not a diagnosis on their own.

After each update or replacement, rerun the original test before you change anything else. If nothing changed, go back to the other areas your tests implicated instead of replacing more parts. Blanket TCP tuning, DNS flushing, factory resets and turning off firewalls aren't routine packet-loss fixes, and changing DNS generally won't repair loss on a connection that's already established.

Test private connections without exposing your services

A private connection adds a path you should keep separate from the underlying internet connection in your mind. Keep access controls in place while you test. Making a private service publicly reachable changes its exposure, not just how good your comparison is.

  1. Test the underlying connection where policy allows. Use a responding public endpoint through an authorized route that lets you observe the underlying connection. Don't disconnect a required protected connection or turn off a kill switch to get this result.
  2. Test the private endpoint through its authorized path. Use the affected application's statistics and supported diagnostics. Leave firewall rules and private-service access restrictions as they are.
  3. Label the destinations and paths clearly. A public test and a private-service test reach different destinations, so they aren't a like-for-like comparison. A clean public test narrows things down but doesn't prove the route to the private service is healthy.
  4. Look at tunnel-specific behavior when it's indicated. If only the tunneled application fails, check the tunnel provider's supported diagnostics and MTU guidance. MTU (maximum transmission unit) is the largest packet size a link allows, and tunnel-related loss can involve server load, transport behavior or MTU mismatches.

If policy stops you from running a separate test of the underlying connection, ask the network administrator for an approved way to diagnose it. Don't guess at a universal MTU, and don't publish a self-hosted service just to make it easier to probe. A private or encrypted connection won't repair damaged cables, faulty Wi-Fi or a remote service that's down.

Escalate persistent loss with before-and-after results

If many destinations are affected, look at the shared connection. If just one service is affected, check that service and its path first. A problem on a remote game server may be beyond anything you can fix locally, and the same distinction tells you whom to contact.

  1. Check the affected service's status. An outage or incident can explain application symptoms even when your other connections work. Don't change your whole network to fix a failure that's specific to one destination.
  2. Contact the right operator. If you keep seeing loss across internet destinations after your local checks, contact your ISP or network administrator. If the problem is limited to one service or private path, start with that service's operator or the administrator in charge of the path.
  3. Provide a reproducible record. Include timestamps and timezone, connection type, affected applications, repeated endpoint results, and the cable, port, device or software changes you've already tried. Keep measured packet loss separate from latency and application disconnects.
  4. Describe route findings carefully. Report a suspected location, not a definite fault or direction of loss based on a single intermediate-hop timeout. Before you post logs publicly, redact account details, private addresses and sensitive service names.

After a local change or an operator fix, rerun the baseline with the same targets and durations under similar load. Check the affected application as well as ping, then keep monitoring during the conditions that used to trigger the problem. A single clean sample shows improvement during that sample. It isn't a permanent fix.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.