How to Check Packet Loss and Understand the Results

The fastest way to check packet loss is to run an online packet loss test, then confirm the result with ping, traceroute, or jitter checks if needed. This is the simplest answer for how to check packet loss when you need a quick browser-based result.

How to check packet loss quickly comes down to one repeatable number: packets sent versus packets received. If the percentage is above 0%, repeat the test and compare Wi-Fi with wired Ethernet.

To check packet loss quickly, run a test for at least 30 to 60 seconds, read the packet loss percentage, and compare ping and jitter at the same time. If packet loss appears, repeat the test on wired Ethernet before changing router or ISP settings.

You can also use a command-line ping test if you want to know how to test my packet loss from your own computer.

ping -n 100 1.1.1.1

ping -c 100 1.1.1.1

• Run an online packet loss test.
• Test for at least 30 to 60 seconds.
• Look for the packet loss percentage.
• Check ping and jitter at the same time.
• If packet loss appears, repeat the test on wired Ethernet.
• If the issue continues, run ping and traceroute to locate the problem.

Use this simple process if you want to know whether you have packet loss and where it may be coming from. Do not rely on one short test because packet loss can be intermittent.

This workflow covers how to test packet loss, how to test for packet loss, and how to do a packet loss test without mixing up Wi-Fi problems, ISP problems, and app-specific route problems.

There is no single perfect test for every situation. The best method depends on what you are trying to check and how much detail you need.

If you need how to run a packet loss test for a support ticket, use the same target, packet count, connection type, and time window so the before-and-after results are comparable.

A browser-based packet loss test is easiest for most users. It is useful when you want to test packet loss online without Java, downloads, or command-line tools.

A ping test is better when you want a simple, repeatable command that works on Windows, Mac, and Linux. Traceroute, pathping, and MTR are better when you need to diagnose packet loss and determine where packet loss is occurring.

• Use an online test when you need a fast answer.
• Use ping when you need a repeatable command.
• Use route tools when you need to locate the problem.
• Use game telemetry when one game or region feels broken.

Use this section when you need how to check packet loss on Windows without installing extra tools. Windows has built-in commands that can help you check for lost packets.

Open Command Prompt and send 100 packets to a stable public target.

If your goal is how to check for lost packets, the final ping summary is the line that matters most.

When the test ends, look for the summary line. It shows packets sent, packets received, packets lost, and the packet loss percentage.

ping -n 100 1.1.1.1

Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)

ping -t 1.1.1.1

pathping 1.1.1.1

• Press Windows + R, type cmd, and press Enter.
• Run ping -n 100 1.1.1.1.
• If Lost is higher than 0, packets were lost during the test.
• Use ping -t for a longer test, then press Ctrl + C to stop it.
• Use pathping when you need more detail across different hops.

If you need how to check packet loss on Mac or Linux, open Terminal and run a 100-packet ping test. When the test finishes, look for the packet loss line.

To test a specific website, app endpoint, or server, replace 1.1.1.1 with a domain or IP address. This is also useful for how to test packet loss on internet services that publish server addresses.

ping -c 100 1.1.1.1

100 packets transmitted, 100 received, 0% packet loss

ping -c 100 example.com

traceroute 1.1.1.1
mtr 1.1.1.1

• Use ping -c 100 for a basic check.
• Use traceroute when you need to see the route packets take.
• Use MTR when it is installed and you need continuous latency and loss by hop.
• Use the same target and packet count for before-and-after comparisons.

Packet loss is only one part of connection quality. You should also look at ping, jitter, and upload stability because a normal speed test does not always explain gaming lag or video call problems.

The basic formula for how to measure packet loss is lost packets divided by packets sent. If a test sends 100 packets and loses 1 packet, the result is 1% packet loss.

For a better result, test packet loss and jitter together. If packet loss is 0% but jitter is unstable, your issue may be delay variation rather than lost packets.

This is the practical answer for how to test jitter and packet loss together: read loss percentage, ping, jitter, and upload stability as one group.

Use this checklist when reading your test results. The important question is not only whether a number appears, but whether the same pattern repeats when the symptom happens.

0% packet loss is what you want to see. If your problem continues with 0% packet loss, look at ping, jitter, device performance, game server issues, or application settings.

One lost packet in a short test may not prove a serious issue. Repeat the test. If packet loss appears repeatedly, especially during the time you feel lag or call drops, treat it as a real problem.

Constant packet loss usually means something in the connection path is unstable. It may be Wi-Fi interference, router overload, bad cables, ISP congestion, or a remote server issue.

Finding packet loss is useful. Finding where it starts is better. The practical answer for how to determine where packet loss is occurring is to test in layers: your router, the public internet, and then the affected service.

First, check your local connection. On Windows, run ipconfig, find Default Gateway, and ping that address. If you see packet loss to your router, the issue is likely inside your local network.

Next, test a stable public target such as 1.1.1.1. If your router test is clean but your internet test shows loss, the problem may be your modem, ISP connection, or upstream route.

If only one app or game has issues, test that service's server if you know the domain or IP address. If packet loss appears only to that service, your home network may be fine.

This layered approach is how to diagnose packet loss, how to detect packet loss in a network, and how to identify packet loss without blaming the wrong part of the connection.

ipconfig
ping -n 100 192.168.1.1

ping -n 100 1.1.1.1
ping -n 100 8.8.8.8

ping -c 100 1.1.1.1
ping -c 100 8.8.8.8

tracert 1.1.1.1
traceroute 1.1.1.1

• Do not assume packet loss at one middle hop always means a real problem.
• Some routers limit or ignore diagnostic traffic.
• The key sign is packet loss that starts at one hop and continues through later hops, including the final destination.

Many people first notice packet loss in games because games are sensitive to real-time network problems. For games such as Fortnite, CS2, Valorant, and League of Legends, check the game settings for network stats, telemetry, performance graphs, ping display, packet loss display, or network debug stats.

If you need how to see packet loss in Fortnite, enable the game's network debug stats and watch for loss during fights, building, or region changes. If you need how to see packet loss in CS2, use the game's telemetry and compare it with a gateway ping.

If you need how to see packet loss in Valorant, turn on network stats that show packet loss and ping, then compare Ethernet with Wi-Fi. If you need how to check packet loss League of Legends, use the game's network indicators or support tools and compare the selected region with a separate packet loss test.

In-game stats are useful, but they may only describe your connection to that game server. A separate test helps you know whether the problem is your network or that specific game route.

• Test your connection on Ethernet.
• Try a nearby game server region.
• Run the test while no downloads or uploads are active.
• Compare another device on the same network.
• Repeat the same game test at a different time of day.

Once you know you have packet loss, use the result to choose the right fix. The fastest way to decide how to lower packet loss is to fix the closest confirmed cause.

If packet loss happens on Wi-Fi, move closer to the router, use Ethernet if possible, restart the router, move the router away from walls and electronics, reduce active devices, and avoid weak mesh backhaul connections.

If packet loss happens on Ethernet, replace the Ethernet cable, try another router or switch port, avoid damaged or sharply bent cables, restart your modem and router, and test another computer if possible.

If packet loss happens only under load, your connection may be congested. Pause large downloads, stop cloud backups while gaming or calling, limit upload-heavy apps, and enable QoS or smart queue management if your router supports it.

This is also how to decrease packet loss, how to avoid packet loss, and how to deal with packet loss in a way that follows the evidence instead of guessing.

• Fix Wi-Fi first if Ethernet works but wireless drops packets.
• Check cables and ports first if wired Ethernet drops packets.
• Reduce upload load if loss appears during calls, streams, or cloud backups.
• Collect evidence before contacting your ISP if loss starts outside your network.

A good packet loss check uses more than one test and compares results. Avoid these mistakes when testing because they can make you blame the wrong cause.

Use your result to choose the next step. Once you know how to check packet loss, the easiest next step is to run a fresh packet loss test and compare it with a ping test. If both show loss, you have stronger evidence.

If you need how to check internet packet loss or how to test internet for packet loss, make sure your gateway test is clean before you focus on the ISP or remote service.

Packet loss is easier to fix when you measure it correctly. Start with a quick packet loss test, then use ping, traceroute, and the steps in this guide to confirm the result and locate the cause.

If your test shows packet loss, your next best read is a guide on how to fix packet loss. If your packet loss is 0% but your connection still feels unstable, check jitter, ping, and overall connection quality next.