How to Test Your Router for Packet Loss

What packet loss looks like

Packet loss means some of the data packets sent between two devices never arrive. The basics of packet loss are a good place to start if you are not sure how it differs from latency.

For ordinary web browsing, a small amount of lost packets may be invisible because the browser asks for the missing data again. For video calls, gaming, live streaming, and voice calls, packet loss is harder to ignore. You might see frozen video, robotic audio, delayed game actions, or calls that drop.

Testing for packet loss is the first step toward deciding whether your router is the problem or just the most visible piece of the connection.

Run a ping test

Open a terminal or command prompt on a computer connected to your network. Use the ping command followed by a stable public destination, such as a website you use daily, a public DNS address, or a game server host. The command is available on Windows, macOS, Linux, and most router diagnostic pages.

Let the test run for more than a few replies. A short burst can miss a problem that only appears under load or interference. If your operating system has a continuous ping option, use it to gather a larger sample before you stop the test.

The output will show the number of packets sent, the number received, the number lost, and the round-trip time for each reply. Some systems also show the minimum, maximum, and average round-trip time.

Read the ping results

Start with the loss percentage reported by ping. Even a small, consistent percentage can affect real-time applications, so do not dismiss it just because most packets arrive. Look for whether the loss is on one device, on one band, or on every wired and wireless device.

Run the test more than once. Try different destinations, because a busy public server can lose packets even when your home network is healthy. Try different times of day, because evening network congestion can make packet loss easier to see.

If every test to several destinations shows packet loss, your home network deserves a closer look. If only one destination shows loss, the problem may be on that server or on the internet path to it.

Use traceroute to find where loss happens

Ping tests the whole path between your computer and a target, so it cannot tell you where the packets are being lost. Traceroute can narrow down the location. Run traceroute on macOS or Linux, or tracert on Windows, to the same destination you used for ping.

Traceroute shows each router hop between your computer and the destination. The first hop is normally your router. If loss appears on the first hop, your router or its connection to the modem is the likely source. If the first hop is clean and loss appears several hops later, the issue may be with your internet provider or a backbone network outside your home.

Some routers do not answer traceroute probes, and a hop may show no response even when traffic is flowing. Do not judge packet loss from a single missing line. Compare several runs and use the ping loss percentage as the main signal.

Test Wi-Fi separately from Ethernet

To separate the router wireless function from the rest of the connection, connect a computer to the router with an Ethernet cable and run the same ping and traceroute tests. Then unplug the cable and run the tests over Wi-Fi from the same room.

If the wired test is clean and the wireless test shows packet loss, the problem is in the wireless path: distance from the router, walls, interference, band congestion, or the router radios. You can narrow it further by testing a second wireless device. If only one device shows loss, its wireless adapter or drivers may be responsible.

If both wired and wireless tests show packet loss, the router itself or the connection from your modem to the internet is the more likely problem.

• Wi-Fi only: investigate router placement, channel settings, and wireless interference.
• Wired and Wi-Fi: check the Ethernet cable, router firmware, and modem connection.
• Only after the first hop: the problem is likely outside your home network.

What to do after you find packet loss

Once you know where packet loss appears, choose the least disruptive fix first. Reboot the router, update its firmware, move it away from walls and metal objects, and try a different Wi-Fi channel. Those steps resolve many intermittent wireless problems without new hardware.

If the router is older or cannot handle the number of devices you connect, newer models are designed to improve reliability. Wi-Fi 7 routers, for example, add features that aim for lower latency and steadier performance in busy homes. Gaming routers often include diagnostics and quality-of-service controls that can help you manage traffic during critical moments.

For homes with coverage gaps, a mesh router may reduce packet loss on wireless clients by giving them a closer access point. If the loss is on a wired connection, test another Ethernet cable before replacing the router. If traceroute shows loss beyond your router, contact your internet provider with the test results.

When packet loss is not the router

Not every packet loss problem can be solved by buying a new router. The public internet path includes many routers owned by other organizations. You can measure that path, but you cannot change it from your home. The IEEE 802.11 standard continues to evolve, and the Wi-Fi Alliance emphasizes reliability in newer generations, but a router cannot fix congestion on a distant backbone link.

If your router has outdated firmware or weak security, an unknown device could be consuming your bandwidth or interfering with the network. NIST publishes cybersecurity standards, guidelines, and best practices that can help you keep a home network more secure. Mesh routers can help with coverage, but security hygiene matters on any network.

Run the tests again after you make changes. The goal is to compare the same path before and after a fix, not to label one device as the cause from a single test.

What to pick for your use

Questions

What is a router packet loss test?

A packet loss test uses ping and traceroute to send data packets from your computer to a destination and measure how many replies come back. It helps you see whether packets are being dropped on your home network, at your router, or beyond your connection.

How do I test packet loss on my router?

Run a continuous ping command from a computer on your network to a stable public destination. Then run a traceroute to the same destination. Compare wired and wireless results to see whether the loss is happening over Wi-Fi or on the entire path.

What does packet loss mean on a ping test?

It means some of the packets your computer sent did not receive replies. Those packets may have been dropped by your router, by a Wi-Fi adapter, by a cable, or by a router beyond your home network.

Can Wi-Fi cause packet loss?

Yes. Distance, walls, interference from neighboring networks, and weak router radios can all cause wireless packet loss. Testing over Ethernet tells you whether the loss disappears when you remove Wi-Fi from the path.

Should I test with Ethernet or Wi-Fi?

Start with Ethernet to test the router and internet path. Then test over Wi-Fi to see if the wireless link adds loss. Comparing the two results is the fastest way to locate the source.

What if the loss is after the first hop?

If traceroute shows packet loss after the first hop, the problem is likely outside your home network. Contact your internet provider with the test results. If the loss is on the first hop, focus on your router, Ethernet cables, and modem connection.