How to Check Packet Loss in Windows 11 (Complete Guide 2026)
Packet loss is one of the most common network problems that can cause unstable internet connections, lag during online games, choppy video calls, slow websites, and random disconnections. If your Windows 11 PC appears to be connected to the internet but the connection keeps dropping, checking for packet loss can help identify the problem.
Windows 11 includes several built-in tools that can help you test packet loss. The simplest method is using the ping command in Command Prompt. For more detailed analysis, you can use pathping, tracert, and PowerShell networking commands.
 |
| Learn how to check packet loss in Windows 11 using Ping, PathPing, and Tracert to diagnose Wi-Fi, Ethernet, router, and internet connection problems. |
In this guide, you will learn how to check packet loss in Windows 11, how to understand packet loss percentages, how to test your router and internet connection, how to use continuous ping, how to identify where packet loss occurs, and how to troubleshoot common causes.
What Is Packet Loss?
Packet loss occurs when network packets sent from one device to another fail to reach their intended destination.
When you use the internet, information is divided into small units called packets. These packets travel across your local network and, in many cases, through multiple routers before reaching the destination.
If some packets are lost along the way, applications may need to retransmit information or deal with missing data.
Microsoft notes that some packet loss can occur normally and does not always create noticeable problems. However, packet loss can reduce network performance and cause applications or higher-level network protocols to fail.
What Causes Packet Loss?
Packet loss can happen for many different reasons. The cause may be inside your Windows 11 PC, on your local network, at your router, or somewhere farther along the network path.
Common causes include:
- Weak Wi-Fi signal
- Wireless interference
- Network congestion
- Faulty Ethernet cables
- Router problems
- Network adapter problems
- Outdated or problematic drivers
- ISP network problems
- Overloaded network equipment
- Routing problems
- Firewall or security software
- Incorrect network configuration
- MTU-related problems
- Remote server or network policies
Microsoft also identifies factors such as local policy, resource limitations, ARP or neighbor-discovery failures, missing routes, congestion, remote policies, and MTU-related drops as possible causes of packet loss.
How to Check Packet Loss in Windows 11 with Ping
The easiest way to check packet loss is with the built-in ping command.
- Press Windows + S.
- Type Command Prompt.
- Open Command Prompt.
- Type a ping command.
- Press Enter.
For example, to test your router:
ping 192.168.1.1
Your router address may be different. To find your default gateway, run:
ipconfig
Then look for Default Gateway under your active network adapter.
For a basic internet test, you can also try:
ping 1.1.1.1
At the end of the test, Windows displays packet statistics.
For example:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
This means all four test packets received replies.
How to Calculate Packet Loss from Ping
Windows calculates packet loss based on the number of packets sent and the number of packets that did not receive replies.
For example:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss)
There is no observed loss in this test.
Another example:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss)
One out of ten packets was lost, producing a reported loss rate of 10 percent.
A larger test provides more observations than the default four packets.
How to Test Packet Loss with 100 Ping Requests
For a more useful short-term test, send 100 ping requests.
ping /n 100 192.168.1.1
Replace 192.168.1.1 with the address you want to test.
Testing 100 packets gives you a larger sample than the default four requests and makes intermittent packet loss easier to observe.
You can also test a public IP address:
ping /n 100 1.1.1.1
Keep in mind that packet loss to a remote destination does not automatically prove that your Windows PC or Wi-Fi connection is responsible.
How to Continuously Check Packet Loss
Windows can continuously ping a destination using the /t parameter.
ping /t 192.168.1.1
The command continues until you stop it.
Press:
Ctrl + C
to stop the test.
Windows will then display the accumulated packet statistics.
Continuous ping is particularly useful when your connection drops randomly. You can leave the test running while waiting for a problem to occur.
How to Check Packet Loss to Your Router
Testing your router is one of the most important first steps.
First find the default gateway:
ipconfig
For example:
Default Gateway . . . . . . . . . : 192.168.1.1
Then run:
ping /n 100 192.168.1.1
If you observe packet loss to your own router, investigate your local network before blaming the ISP.
Possible causes include:
- Weak Wi-Fi signal
- Wireless interference
- Router overload
- Faulty Ethernet cable
- Network adapter problems
- Driver problems
- Local network congestion
How to Check Packet Loss on Wi-Fi
Wi-Fi is particularly susceptible to interference and signal-quality problems.
Start by checking your Wi-Fi signal strength.
If the signal is weak, move closer to the router and repeat the packet-loss test.
You can also compare the results at different locations.
For example:
Location A: 0% packet loss Location B: 5% packet loss Location C: 15% packet loss
If packet loss increases as you move farther away from the router, wireless signal quality may be contributing to the problem.
See our related guide:
How to Check Wi-Fi Signal Strength in Windows 11
How to Check Packet Loss on Ethernet
If you are using an Ethernet connection, packet loss can be investigated by testing the local gateway.
ping /n 100 YOUR-GATEWAY
If packet loss occurs even when connected directly through Ethernet, investigate:
- Ethernet cable
- Router port
- Network adapter
- Network adapter driver
- Router hardware
- Local network configuration
Try another Ethernet cable or router port if possible.
How to Check Packet Loss to the Internet
After testing your router, test a remote IP address.
For example:
ping /n 100 1.1.1.1
Compare the result with the router test.
For example:
Router: 0% packet loss Public IP: 5% packet loss
This suggests that the local connection to the router is working during the test while some loss occurs farther along the path.
However, more testing is needed to determine exactly where the loss occurs.
How to Check Packet Loss to a Website
You can also test a hostname:
ping /n 100 example.com
When pinging a hostname, Windows first resolves the hostname to an IP address.
This means a hostname test involves name resolution in addition to the ICMP connectivity test.
If an IP address works but the hostname does not, investigate DNS resolution.
You can review DNS configuration with:
ipconfig /all
And test name resolution with:
nslookup example.com
How to Find Where Packet Loss Occurs
A basic ping test can tell you that packet loss exists, but it cannot always tell you where the loss occurs.
For a more detailed analysis, Windows includes pathping.
Run:
pathping 1.1.1.1
Pathping combines route tracing with repeated ping measurements. Microsoft documents it as a tool that provides latency and network-loss information at intermediate hops between the source and destination.
How to Use PathPing to Diagnose Packet Loss
Open Command Prompt and run:
pathping 1.1.1.1
Pathping first identifies the route to the destination and then collects statistics from the routers and links along the path.
The command can take significantly longer than a normal ping because it gathers repeated measurements.
Microsoft's documentation notes that the statistics-gathering phase can take around 90 seconds depending on the number of hops.
The resulting report includes information about:
- Hop number
- Round-trip time
- Packets sent
- Packets lost
- Loss percentage
- Router or link information
How to Interpret PathPing Packet Loss
Pathping can show loss associated with individual routers or links.
This distinction is important.
A router can show packet loss when responding to diagnostic traffic without necessarily dropping traffic that it is forwarding to the final destination.
Microsoft specifically warns through its pathping output documentation that packet loss shown for a router itself does not necessarily affect its ability to forward traffic that is not addressed to that router.
Therefore, do not automatically assume that the first hop showing loss is the cause of the entire connection problem.
How to Use Tracert to Investigate Packet Loss
Another useful Windows command is tracert.
Run:
tracert 1.1.1.1
Tracert shows the routers, or hops, along the route to a destination.
It can help you understand how traffic travels from your PC toward the destination.
Microsoft notes that pathping can be used when you need both the route and latency or packet-loss information for individual routers and links.
What Does 0% Packet Loss Mean?
0% packet loss means that all packets in the particular test received replies.
For example:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)
This is a good result for that particular destination and test period.
However, 0% loss in one short test does not guarantee that your connection will never experience packet loss.
Intermittent problems may require longer monitoring.
What Does 1% Packet Loss Mean?
1% packet loss means that approximately one percent of the tested packets did not receive replies.
Whether this creates a noticeable problem depends on the application, destination, duration, and type of traffic.
A small amount of packet loss may not always produce obvious symptoms, while persistent loss can affect real-time applications more noticeably.
What Does 5% Packet Loss Mean?
5% packet loss means that approximately five percent of the tested packets were lost during the measurement.
If the loss is persistent, it is worth investigating.
For example, test your router first:
ping /n 100 YOUR-GATEWAY
Then compare it with a remote destination:
ping /n 100 1.1.1.1
This comparison helps determine whether the problem is more likely local or farther along the network path.
What Does 10% Packet Loss Mean?
10% packet loss is significant enough to justify further investigation, especially if it occurs consistently.
You may experience:
- Online gaming lag
- Voice call interruptions
- Video conferencing problems
- Slow or inconsistent network transfers
- Random application disconnections
Start by testing the local router and then move outward toward remote destinations.
Can Packet Loss Cause Gaming Lag?
Yes. Packet loss can cause problems in online games because some information sent between your PC and the game server may not arrive successfully.
Depending on the game, this can appear as:
- Character movement delays
- Rubber-banding
- Delayed actions
- Temporary freezes
- Disconnections
However, high latency, jitter, server problems, and congestion can also cause gaming problems.
Packet loss should therefore be tested rather than assumed to be the cause.
Can Packet Loss Affect Video Calls?
Packet loss can affect real-time communication applications.
Possible symptoms include:
- Audio cutting out
- Video freezing
- Pixelated video
- Delayed communication
- Call disconnects
If the problem occurs repeatedly, test the local network with a continuous ping.
How to Fix Packet Loss on Windows 11
The correct solution depends on where the packet loss occurs.
1. Restart Your Router
Restarting the router can resolve temporary networking problems.
After restarting it, repeat the packet-loss test.
2. Move Closer to the Wi-Fi Router
If packet loss occurs over Wi-Fi, test the connection closer to the router.
3. Use Ethernet
If possible, connect your PC directly to the router using Ethernet and repeat the test.
If the loss disappears, wireless conditions may be contributing to the problem.
4. Check the Network Adapter
Check whether your network adapter is functioning correctly.
See:
How to Check Network Adapter in Windows 11
5. Check Your DNS Settings
DNS problems do not necessarily cause packet loss, but incorrect name resolution can make network problems appear similar to connectivity failures.
See:
How to Check DNS Settings in Windows 11
6. Check the Ethernet Cable
If you use Ethernet, replace the cable or test another router port.
7. Update or Reinstall the Network Driver
Driver problems can contribute to local networking issues. Check Device Manager for warnings associated with the network adapter.
8. Check for VPN or Security Software
VPNs, firewalls, and security software can alter network traffic or filtering behavior.
Temporarily testing without a VPN can help determine whether it is involved, provided doing so is safe for your environment.
9. Check for Network Congestion
Heavy downloads, cloud synchronization, streaming, and multiple connected devices can increase network congestion.
10. Contact Your ISP
If packet loss occurs beyond your local network and persists across multiple tests, your ISP may need to investigate the connection.
How to Determine if Packet Loss Is Your Wi-Fi or ISP
Use a simple comparison.
First test the router:
ping /n 100 YOUR-GATEWAY
Then test a remote destination:
ping /n 100 1.1.1.1
Consider these examples.
| Router Loss | Internet Loss | Possible Direction |
|---|---|---|
| 0% | 0% | No packet loss observed |
| 5% | 8% | Investigate local network first |
| 0% | 5% | Investigate beyond the local network |
| 10% | 10% | Strong reason to investigate local connectivity |
These results are diagnostic clues, not definitive proof of the exact cause.
How to Check Packet Loss Without a Speed Test
A speed test measures bandwidth, while packet-loss testing measures whether test packets receive replies.
You can check packet loss using only Windows built-in tools.
For example:
ping /n 100 192.168.1.1
Then:
ping /n 100 1.1.1.1
For more detailed route analysis:
pathping 1.1.1.1
This means you do not need to install a separate application for basic packet-loss troubleshooting.
Does Packet Loss Always Mean a Bad Internet Connection?
No.
Packet loss needs to be interpreted in context.
Some devices may deprioritize or filter diagnostic traffic such as ICMP while continuing to forward normal application traffic.
Microsoft's packet-loss documentation also explains that packet loss can occur for different reasons at local and remote points in the network.
For this reason, do not diagnose an ISP problem based on a single ping test to one remote server.
Packet Loss vs Latency
Packet loss and latency are different network measurements.
Latency describes how long it takes for data to travel to a destination and return in a round-trip measurement.
Packet loss describes packets that do not successfully receive a response.
You can have:
- Low latency with no packet loss
- High latency with no packet loss
- Low latency with packet loss
- High latency with packet loss
This distinction is important when troubleshooting online gaming, video calls, and general internet performance.
Packet Loss vs Internet Speed
Packet loss is also different from internet speed.
Internet speed measures bandwidth, while packet loss measures unsuccessful packet delivery in a test.
A connection can have fast download speeds but still suffer from intermittent packet loss.
For bandwidth testing, see:
How to Check Internet Speed in Windows
Advanced Packet Loss Troubleshooting with PktMon
Windows also includes Packet Monitor (Pktmon), a built-in diagnostic tool that can capture packet traces and provide packet-loss statistics.
Microsoft recommends Pktmon as part of packet-loss investigation because it can help attribute local packet loss to specific reasons and locations.
For example, Microsoft documents a basic workflow using:
pktmon.exe start -c
Stop the capture with:
pktmon.exe stop
And convert the ETL output to text with:
pktmon.exe etl2txt PktMon.etl
This is an advanced diagnostic method and is usually unnecessary for simple home-network troubleshooting.
Best Order for Testing Packet Loss
If you want an efficient troubleshooting process, test from the closest destination to the farthest.
- Ping localhost
ping 127.0.0.1
- Ping your own IP address
ping YOUR-IP
- Ping your router
ping /n 100 YOUR-GATEWAY
- Ping a public IP
ping /n 100 1.1.1.1
- Ping a hostname
ping /n 100 example.com
- Use pathping if necessary
pathping 1.1.1.1
This sequence helps separate local problems from problems farther along the network path.
Packet Loss Troubleshooting Cheat Sheet
| Command | Purpose |
|---|---|
ping 127.0.0.1 |
Test the local TCP/IP stack |
ipconfig |
Find your IP address and default gateway |
ping /n 100 YOUR-GATEWAY |
Test the local network |
ping /n 100 1.1.1.1 |
Test a remote IP address |
ping /t YOUR-GATEWAY |
Monitor the local connection continuously |
tracert 1.1.1.1 |
View the route to a destination |
pathping 1.1.1.1 |
Analyze latency and packet loss along the route |
nslookup example.com |
Test DNS name resolution |
Related Articles
- How to Check Wi-Fi Signal Strength in Windows 11
- How to Check Internet Speed in Windows
- How to Check IP Address in Windows 11
- How to Check MAC Address in Windows 11
- How to Check DNS Settings in Windows 11
- How to Check Network Adapter in Windows 11
- How to Ping an IP Address in Windows 11
Frequently Asked Questions
How do I check packet loss in Windows 11?
Open Command Prompt and run a ping test such as ping /n 100 1.1.1.1. Windows will display the number of packets sent, received, lost, and the resulting packet-loss percentage.
What is a normal packet loss percentage?
A test showing 0% packet loss means that all tested packets received replies. Persistent packet loss should be investigated, especially when it causes noticeable network problems.
How do I check packet loss to my router?
Run ipconfig to find your Default Gateway, then use ping /n 100 followed by the gateway address.
Can Wi-Fi cause packet loss?
Yes. Weak signal strength, interference, congestion, and other wireless conditions can contribute to packet loss.
Can Ethernet have packet loss?
Yes. Faulty cables, router ports, adapters, drivers, hardware, and network problems can contribute to packet loss over Ethernet.
Does packet loss make games lag?
It can. Packet loss may cause rubber-banding, delayed actions, freezes, or disconnections in online games. Latency and other network problems can cause similar symptoms.
What command shows packet loss in Windows?
The ping command shows packet-loss statistics at the end of the test. pathping provides more detailed information about loss along the network path.
What is the difference between ping and pathping?
Ping tests connectivity and reports response statistics for a destination. Pathping combines route information with repeated measurements to provide latency and packet-loss information at intermediate hops.
Can packet loss be caused by my ISP?
Yes. Packet loss can occur beyond your local network. However, test your router and local connection first before concluding that the ISP is responsible.
Does 0% packet loss mean my internet is perfect?
No. It means that no loss was observed during that particular test. Other problems such as high latency, DNS failures, slow bandwidth, or intermittent issues can still exist.
Can I check packet loss without installing software?
Yes. Windows 11 includes ping, tracert, pathping, and other built-in networking tools.
Final Thoughts
Checking packet loss is an important step when troubleshooting an unstable Windows 11 internet connection.
The easiest method is to use:
ping /n 100 YOUR-GATEWAY
Then compare the result with a remote destination:
ping /n 100 1.1.1.1
If you need more detailed information about where loss occurs, use:
pathping 1.1.1.1
Start with your local network before assuming the problem is caused by your ISP. Testing the router, network adapter, Wi-Fi signal, DNS configuration, and remote destinations can help narrow down the source of the problem.
Remember that packet loss is only one part of network performance. Latency, jitter, bandwidth, DNS resolution, routing, and application-level problems can also affect your internet experience.
With the built-in networking tools in Windows 11, you can perform a detailed first-level packet-loss investigation without installing additional software.