Packet Loss Test
Find out whether data packets are being dropped on their way to the server.
ResultLost packets in %
Guides
Packet loss happens when data packets sent across a network fail to reach their destination. It’s usually measured as a percentage of packets sent, and even a small amount can disrupt real-time uses like gaming, video calls and VoIP — often more noticeably than it affects browsing, streaming or downloads.
Written by the Pingvero team · Last updated September 11, 2026
The Basics
Every time you load a page, join a call or play an online game, your data is broken into small pieces called packets and sent across the network to their destination, where they’re reassembled. Packet loss is what happens when one or more of those packets never arrive — they’re dropped somewhere along the way rather than simply arriving late. A connection can still show a fast download speed while some of its packets are quietly failing to make the trip, because throughput and reliability are two different things.
Packet loss is almost always expressed as a percentage of the packets that were sent. A test that sends 100 packets and receives 98 back has lost 2 of them — a packet loss of 2%.
| Packets sent | 100 |
|---|---|
| Packets lost | 2 |
| Packet loss | 2% |
Packet Loss %
=
(Lost Packets ÷ Sent Packets) × 100
Want to check your own connection? Use our free Packet Loss Test
Recognizing It
Packet loss tends to show up as small interruptions rather than a connection going down entirely.
None of these symptoms guarantee packet loss is the cause — high ping, high jitter, a slow connection, or something on the site or server’s end can all look similar from the outside. Running a Packet Loss Test is the only way to confirm it rather than guess.
Related Terms
Three different measurements that are easy to mix up.
Ping (or latency) is how long a packet takes to make a round trip. Jitter is how much that round-trip time varies from one packet to the next. Packet loss is simpler than either — it’s just whether the packet arrives at all. A connection can have excellent ping and jitter and still lose packets, and a connection that loses nothing can still have high ping or high jitter; each one has to be checked on its own.
| Metric | What it measures | What happens when it’s bad |
|---|---|---|
| Packet Loss | The share of packets sent that never arrive at all | Choppy calls, frozen video, rubber-banding and lag spikes in games |
| Ping / Latency | How long a packet that does arrive takes to make the round trip | A noticeable delay between an action and its effect |
| Jitter | How much that round-trip time varies from one packet to the next | Robotic-sounding calls, stuttering video and inconsistent lag |
Check all three with the Packet Loss Test, our ping tool and the Jitter Test — or a Latency Test for a closer look at delay on its own.
Reading a Result
General reference points, not fixed thresholds — what counts as acceptable depends on the application, how long you test for, the destination you test against and the network conditions at the time.
| Packet loss | General interpretation |
|---|---|
| 0% | Ideal — no observed packet loss during the test |
| Under 1% | Usually low impact, but the effect still depends on the application and test conditions |
| 1–2% | Can become noticeable in real-time applications such as calls and games |
| Above 2% | More likely to cause noticeable problems, especially for gaming and calls |
| Higher, sustained loss | Usually deserves investigation, particularly if it holds up over Ethernet and repeat tests |
No single percentage is always safe or always unacceptable — a video call and a large file download tolerate loss very differently. Run the Packet Loss Test to see where your own connection falls.
Troubleshooting
Packet loss can come from almost anywhere along the path between your device and the destination.
Distance from the router, thick walls and interference from neighboring networks or other wireless devices can weaken a signal enough that packets are corrupted or dropped. A crowded WiFi channel makes this worse, leaving less clean airtime for your own traffic.
When a link carries more traffic than it can handle, routers and switches along the way start dropping packets rather than queuing them indefinitely. This can happen on your own network, a shared connection, or further along your ISP’s infrastructure.
A damaged cable, a bent connector or a loose port can corrupt or drop packets before they even leave your network. This is often the culprit when loss appears consistently on one wired device but not others.
An aging router, one running near its limits, or a device that has overheated or picked up a firmware bug can start dropping packets under load. A simple restart often clears a temporary version of this.
The problem isn’t always upstream — an outdated or failing network adapter, a driver issue, or a device struggling to keep up with incoming traffic can lose packets on its own, even when the rest of the network is healthy.
Congestion, maintenance or routing issues on your provider’s network sit outside your home entirely, but still show up as packet loss on a test. Seeing the same loss on multiple devices over Ethernet is the usual way to confirm it.
A VPN routes traffic through an additional server and network path, which adds another point where packets can be delayed or dropped. It isn’t always to blame — testing with the VPN on and off is the clearest way to check.
Loss observed toward one destination doesn’t automatically mean your own network is at fault — an overloaded server or an inefficient route between you and it can produce the same result. Testing a different destination helps tell the two apart.
Methodology
A packet loss test works by sending a batch of small probes to a server and counting how many complete a round trip within a short time limit. Any that don’t respond in time are counted as lost in the context of that test; dividing the lost count by the number sent, then multiplying by 100, gives the packet loss percentage.
Because packet loss is often intermittent rather than constant, a single short test can miss a problem that only shows up occasionally, or catch a brief spike that isn’t representative of the connection overall. A single ping is rarely enough to characterize it — results also depend on the destination tested and the conditions at that moment, so running the test more than once gives a more reliable picture.
Try It Yourself
A short checklist for a result you can actually trust.
Fix It
None of these guarantee a specific result, but they address the most common causes, roughly in the order worth trying.
Test over a wired Ethernet connection — if the packet loss disappears, WiFi is almost certainly the source.
Restart your router, modem and any other equipment in the path; this clears a surprising number of temporary faults.
Check your Ethernet cables, connectors and the router ports they plug into for damage or a loose fit.
If WiFi is the issue, move closer to the router, reduce obstacles and interference, and try a different band or channel where your device supports it — see our guide to improving WiFi speed.
Reduce network congestion by pausing large downloads, uploads or backups while you test.
Check for a router or modem firmware update, without expecting it to be a guaranteed fix on its own.
Compare results at different times of day to see whether the issue is tied to peak usage.
Contact your ISP if packet loss persists over Ethernet, across several tests and on more than one device — that combination usually points beyond your home network.
Gaming
Online games depend on a steady stream of small updates to keep your view of the game in sync with the server and other players. When packets go missing, that stream breaks — which is why gaming tends to show packet loss more obviously than almost any other use. Typical signs include rubber-banding (where your character snaps back to an earlier position), actions that register late or not at all, and brief disconnects when too many packets in a row fail to arrive.
High ping is not the same thing as packet loss, and one doesn’t guarantee the other — a connection can respond quickly on average and still drop packets. That’s why it’s worth checking a Packet Loss Test alongside a quick ping test and Jitter Test, rather than judging from ping alone.
Wireless Connections
WiFi is more exposed to packet loss than a wired connection, mainly because signal strength depends on distance, walls and interference — things a cable doesn’t have to deal with. If packet loss shows up on WiFi but disappears over Ethernet from the same spot, the wireless link itself is almost certainly the cause.
Compare this test over WiFi with a WiFi Speed Test from the same spot, or see the full guide to improving WiFi speed.
Related Terms
Yes. An Internet speed test mostly measures throughput — how much data your connection can move per second — and it can show a connection is fast and low-latency even while it’s dropping packets intermittently. A connection posting 500 Mbps download with low latency can still have brief spells of packet loss that make video calls stutter or cause lag spikes in a game, because speed and reliability are separate properties of the same connection.
Run a Packet Loss Test alongside your next speed test rather than assuming a good speed result rules the problem out.
FAQ
Short answers to the questions people ask most about packet loss.
Packet loss happens when data packets sent across a network fail to reach their destination. It is usually expressed as a percentage of packets sent, and even a small amount can affect real-time uses like calls and gaming more noticeably than it affects browsing or downloads.
Not automatically. 1% packet loss rarely causes visible problems for browsing, streaming or downloads, since those recover quietly through retransmission. Real-time uses such as competitive gaming or voice calls are more sensitive and can occasionally show a brief stutter at that level.
Yes. 0% means every packet in a given test completed its round trip successfully — the best possible result. A single clean test does not guarantee packet loss never happens, though, since it can be intermittent, so testing again at a different time gives a fuller picture.
There is no single number that applies to every connection or every use. As a general guide, 0% is ideal, under 1% is usually unnoticeable, 1–2% can start to show up in real-time apps, and anything sustained above 2% is worth investigating — but what counts as acceptable also depends on what you are doing online and how the loss is distributed over time.
Common causes include WiFi interference or a weak signal, network congestion, an aging or overloaded router, faulty cables or hardware, problems on your own network adapter, issues on your ISP’s network, and occasionally an extra hop added by a VPN. See the causes section above for the full list.
WiFi is more exposed to packet loss than a wired connection because a wireless signal can be weakened by distance, walls and interference from neighboring networks or other devices. Testing the same connection over Ethernet is the quickest way to confirm whether WiFi itself is the source.
Not directly — they measure different things. Ping is the round-trip time for a packet that does arrive; packet loss is whether it arrives at all. A connection can have a low ping and still lose packets, or a higher ping and lose none, which is why it is worth checking both with a quick ping check and a Packet Loss Test.
Yes, often more noticeably than ping does. Online games depend on a steady stream of small updates, so lost packets can show up as rubber-banding, delayed actions or brief disconnects — sometimes at loss levels that would go unnoticed while just browsing.
Yes. Video and voice calls need a continuous stream of audio and video data, so lost packets tend to show up as frozen frames, robotic-sounding audio or dropped words, even when the call does not disconnect entirely.
Run a Packet Loss Test, which sends a batch of requests and reports what percentage failed to complete. Because loss can be intermittent, it helps to repeat the test at different times and to compare a WiFi result with a wired one.
Start with the simplest checks: test over Ethernet to rule out WiFi, restart your router and modem, and check your cables. If loss continues, reduce network congestion and update your router’s firmware; if it persists across several tests and devices, contact your ISP. See the full steps above.
Yes. A speed test measures throughput — how much data your connection can move per second — while packet loss measures reliability. A connection can show a high download speed and low latency and still lose packets intermittently, which can make real-time apps feel worse than the speed number suggests.
It can, though it does not always. A VPN routes your traffic through an extra server and network path, which adds another point where packets can be delayed or dropped. It is not the most common cause, so it is worth testing with and without the VPN rather than assuming it is responsible.
Get started
Run the free Packet Loss Test to get a real number, then pair it with a ping and jitter test for the full picture.