How to Diagnose and Fix Packet Loss: Step-by-Step Guide for Windows, macOS & Home Routers

Few networking problems are more frustrating than packet loss. You run a standard speed test and see 300 Mbps download speed, yet your Discord audio cuts out, your Zoom video freezes every two minutes, and characters in competitive games rubber-band backward. That is because raw bandwidth throughput and packet transmission reliability are two completely distinct network dimensions.

Packet loss occurs when one or more units of data (packets) traveling across a computer network fail to reach their destination. Even a modest 2% to 5% packet loss can degrade real-time interactive protocols into an unusable state. In this comprehensive engineering guide, we walk you through how to systematically identify the exact physical or logical hop where packets are being dropped and how to eliminate it.

---

Step 1: Isolate Local vs. External Network Packet Loss

Before contacting your Internet Service Provider, you must determine whether packets are dropping inside your home network (between your PC and router) or outside in the ISP backbone.

Open your command line terminal and execute a local continuous ping to your default gateway:

# On Windows Command Prompt:
ping -n 100 192.168.1.1

# On macOS or Linux Terminal:
ping -c 100 192.168.1.1

(Note: Replace 192.168.1.1 with your router's actual LAN IP address, such as 192.168.0.1 or 10.0.0.1).

• If loss is > 0% locally: The issue is 100% inside your home. Check your Ethernet cable, Wi-Fi interference, or router CPU load.
• If loss is 0% locally: Your local equipment is working cleanly. The packet loss is occurring upstream at your ISP modem, fiber optical terminal (ONT), or regional routing exchange.

---

Step 2: Run MTR (My Traceroute) to Pinpoint the Dropping Hop

Standard traceroute only tests three pings per hop, which frequently misses intermittent packet bursts. A real network diagnostics tool like MTR (My Traceroute) or Windows WinMTR sends continuous packets along every router hop from your computer to a destination target (like Cloudflare 1.1.1.1 or Google 8.8.8.8):

# Install & run MTR on macOS:
brew install mtr
sudo mtr 1.1.1.1

# Install & run on Ubuntu/Debian Linux:
sudo apt install mtr
mtr 1.1.1.1

Inspect the Loss% column across each hop:

1. Hop 1 (Your Router): If Loss% is present here, replace your Ethernet cable or switch to a 5 GHz/6 GHz Wi-Fi channel.
2. Hop 2 (ISP First Node): If packet loss begins at Hop 2 and persists down every subsequent hop, your physical fiber line, coaxial cable, or modem is experiencing signal degradation (optical dBm loss or RF noise). Contact your ISP with these exact MTR timestamps.
3. Isolated Mid-Hop Loss: If an intermediate transit hop shows 15% loss but all subsequent hops show 0% loss, that router simply has ICMP rate-limiting enabled; it is not real packet loss. Real packet loss persists all the way to the final destination hop.

---

Step 3: Five Practical Fixes for Packet Loss

1. Replace Damaged Ethernet Cables: A Cat5e or Cat6 cable that has been bent beneath furniture or crimped with damaged RJ45 pins will intermittently drop 1000BASE-T link negotiation down to 100 Mbps, discarding collision frames.
2. Ditch 2.4 GHz Wi-Fi: The 2.4 GHz spectrum shares bandwidth with Bluetooth devices, baby monitors, and microwave ovens. Switch to 5 GHz or 6 GHz with a dedicated 80 MHz channel.
3. Enable SQM on Your Router: If packet loss only happens while family members are downloading games or uploading cloud backups, your router's queue is overflowing (Bufferbloat). Enabling Smart Queue Management (CAKE or FQ-CoDel) prevents queue drops.
4. Check MTU Size & Packet Fragmentation: An incorrectly oversized Maximum Transmission Unit (MTU) causes routers to fragment packets. Test using ping -f -l 1472 1.1.1.1 on Windows to verify MTU integrity.
5. Re-test with WRLDU Live Diagnostics: Use the WRLDU Live Ping & Jitter Monitor to continuously observe packet arrival stability in real-time.