Modem packet loss troubleshooting: 4 tests that pinpoint gaming lag causes

Part of our guide on udp loss detection commands

Most guides test the wrong thing first—here's how to prove the modem is guilty before you call your ISP.

Why packet loss shows up at the modem first

Packet loss at the modem happens when data leaving your network hits congestion, signal degradation, or errors before it reaches the ISP's network. The modem is the handoff point. It converts your local traffic into whatever the ISP's line carries (cable, fiber, DSL) and any fault on that line, in the modem's chipset, or in the ISP's first routing hop shows up as dropped packets.

Three causes dominate. Line noise from damaged coax or corroded phone wiring raises the error rate until packets fail their checksum and get discarded. Overheating modems throttle or reboot, cutting traffic for seconds at a time. ISP congestion at peak hours queues your packets until buffers overflow and the oldest ones are dropped.

Modem loss is different from router loss in one key way: it affects every device equally. If your PC on Ethernet and your phone on Wi-Fi both see loss to the same target at the same time, the modem or ISP is guilty. Router problems are selective: one band, one device, or one SSID.

• Line noise: damaged coax, loose F-connectors, corroded DSL pairs, or ingress from electrical interference – shows as rising uncorrectable errors in modem logs
• Overheating: modems in cabinets or on top of other gear thermal-throttle after 20 to 40 minutes of load, then recover when idle
• ISP congestion: loss spikes between 6 PM and 11 PM on cable networks when neighborhood usage peaks, clears overnight
• Firmware bugs: some modem models drop packets after days of uptime until rebooted, traced to memory leaks or stale NAT tables

Test 1: Ping the modem gateway for 10 minutes

This test isolates the modem from everything downstream. The gateway address (usually 192.168.1.1, 192.168.0.1, or 10.0.0.1) is the modem's internal IP. Pinging it proves whether packets are dropping between your device and the modem itself. If that sounds like your situation, read up on packet loss over ethernet next.

Run the test wired first. Open Command Prompt or Terminal and type ping 192.168.1.1 -t on Windows, or ping 192.168.1.1 on Mac and Linux. Let it run for 10 minutes. Short tests miss intermittent loss. You want at least 600 packets so a handful of drops registers as a real percentage.

Watch for two numbers: packet loss and latency spikes. Zero loss is the target on Ethernet. Loss above 0.5% points to the modem, the line, or a duplex mismatch on the Ethernet port. Latency should sit under 5 ms and stay flat. Spikes to 50 ms or higher with no loss suggest the modem is processing other traffic or queuing your ICMP replies behind bulk transfers.

On Wi-Fi, 1% to 2% loss is normal in a busy 2.4 GHz environment. Above that, interference is likely. Test again on 5 GHz or wired. If loss disappears on Ethernet, the modem is not the problem. If that sounds like your situation, read up on WiFi 6 packet loss test next.

1. Find your gateway IP: open Command Prompt and type ipconfig (Windows) or ifconfig (Mac/Linux), look for Default Gateway
2. Start the ping: ping 192.168.1.1 -t on Windows or ping -c 600 192.168.1.1 on Mac/Linux
3. Let it run for 10 minutes without pausing or switching windows: some network stacks throttle background ICMP
4. Stop the test: press Ctrl+C and read the summary line for packet loss percentage and average latency
5. Repeat on a second wired device to confirm the result is not NIC-specific

Test 2: Trace to the ISP's first hop and compare loss

The ISP's first hop is the router your modem talks to when packets leave your house. If you see loss to the gateway and also to the first hop, the fault is outside your equipment: either the line or the ISP's infrastructure.

Run tracert 8.8.8.8 on Windows or traceroute 8.8.8.8 on Mac and Linux. The second line in the output (right after your gateway) is the ISP's first router. Copy that IP address. Now ping it for 10 minutes the same way you pinged the gateway.

Compare the two results. If gateway loss is 0.5% and first-hop loss is also 0.5%, the problem is upstream: your ISP's line, their router, or congestion in their network. If gateway loss is 0% but first-hop loss is 3%, the ISP's router is overloaded or your modem's upstream signal is weak. If first-hop loss is lower than gateway loss, something is wrong with your reading: re-test. If that sounds like your situation, read up on why 1% average still stutters next.

Some ISPs rate-limit ICMP to their own routers, so you might see 10% to 20% loss on ping but zero loss in actual game traffic. Cross-check with a game server ping or a UDP test tool to confirm.

Test 3: Compare wired versus wireless loss to the same target

This test separates modem issues from Wi-Fi problems. Packet loss that appears on wireless but vanishes on Ethernet is not a modem fault: it's interference, range, or a misconfigured wireless channel.

Pick a stable external target: 8.8.8.8 or a game server IP you know. Ping it for 10 minutes on an Ethernet connection and record the loss percentage. Unplug, switch to Wi-Fi on the same device, and ping the same target for another 10 minutes. Before you commit to anything, it is worth looking at lag test pc for intermittent packet loss.

If wired shows 0.2% loss and wireless shows 0.2% loss, the modem or ISP is the cause. If wired shows 0% and wireless shows 4%, you have a local RF problem: overlapping channels, a weak signal, or a congested band. If both are clean but you see loss in-game, the issue is routing or the game server itself.

GearUP Booster helps here by rerouting game traffic around ISP congestion points and optimizing the path between your modem and the game server. It won't fix a broken modem or a noisy Wi-Fi channel, but once you've confirmed the line is clean, it reduces ping spikes and stabilizes packet delivery. The free trial on PC lets you test it against your baseline without committing.

Test 4: Run a long-duration UDP test to catch bursty loss

Ping uses ICMP, which some modems and ISPs treat differently than game traffic. Games send UDP packets in bursts, and loss during those bursts (bursty loss) is what actually causes rubber-banding and desync. A UDP test simulates real game conditions better than ping. Before you commit to anything, it is worth looking at high ping despite good speed test.

Use a tool like iperf3 or GearUP's ping test feature, which sends UDP packets to game server regions. Run the test for 15 to 20 minutes while you're doing nothing else on the network. Target a game server or a known-stable endpoint.

If the UDP test shows 0.8% loss but your ICMP pings were clean, your modem is prioritizing ICMP or deprioritizing UDP under load. That's a QoS misconfiguration or a sign the modem's buffer is too small. If both tests show the same loss, you have a straightforward line or ISP issue.

Bursty loss is harder to catch with ping because it happens in 2- to 5-second windows when traffic spikes. A 10-minute average might look fine, but those few seconds wreck a game. UDP tests log per-second loss, so you see the spikes clearly.

When to escalate to your ISP versus swap the modem

If all four tests show consistent loss above 0.5% to both the gateway and the ISP first hop, the problem is outside your house. Call your ISP with the data. Tell them you've tested wired to the gateway and to their first hop, both show loss, and you need a line check.

Most ISPs can see your modem's signal levels remotely: downstream power in dBmV, upstream power, and signal-to-noise ratio (SNR). For cable, downstream should sit between -7 and +7 dBmV, upstream between 35 and 51 dBmV, and SNR above 33 dB. Outside those ranges, the line or a splitter is the issue.

If loss only appears to the gateway and the first hop is clean, the modem is likely failing. Overheating, bad capacitors, or firmware corruption all cause intermittent packet loss that clears after a reboot and returns hours later. Modems generally last 3 to 5 years under continuous load. Swap it if it's older or if reboots only fix the issue temporarily.

ISP-provided modems are often to blame because they run hot and use low-end chipsets. Buying your own modem (something like a Motorola MB8600 or Netgear CM1000 for cable) gives you better visibility into stats and more stable firmware. The upfront cost pays back in 12 to 18 months versus rental fees.

• Call the ISP when: loss appears on gateway and first hop equally, signal levels are out of spec, or loss spikes at the same time every evening
• Replace the modem when: loss is only to the gateway, the modem runs hot to the touch, reboots temporarily fix it, or it's over 4 years old
• Check firmware first: log into the modem's web interface (usually 192.168.100.1 for cable modems), look for a firmware update option, apply it, then reboot and re-test

How to stop modem packet loss from coming back

Once you've fixed the immediate issue, three habits keep it from returning. Reboot the modem every 4 to 6 weeks, or right after any firmware update. Modems accumulate stale sessions, memory leaks, and routing-table bloat that clears on reboot. Set a calendar reminder.

Check signal levels monthly if you own the modem. Log into its web interface and screenshot the downstream power, upstream power, SNR, and uncorrectable error counts. If errors climb from zero to hundreds per hour, the line is degrading: call the ISP before loss becomes constant.

Keep the modem cool. Mount it vertically with open air on all sides, away from heat sources. Modems in enclosed cabinets or stacked with other gear run 10 to 20°C hotter, and heat is the leading cause of premature failure. A small USB fan costs under $10 and extends life noticeably.

1. Reboot the modem every 4 to 6 weeks: unplug power, wait 30 seconds, plug back in, wait 3 to 5 minutes for full reconnect
2. Log signal levels monthly and compare to baseline: rising error counts or falling SNR mean a line fault is developing
3. Run the 10-minute gateway ping test quarterly as a health check, especially if you notice any in-game lag returning
4. Update modem firmware when the manufacturer releases it, then reboot immediately: half of post-update issues trace to skipped reboots

Questions people still ask

I've seen more modem-blamed-for-router and router-blamed-for-ISP cases than actual modem failures: this sequence finally proves which one is guilty.