Packet Loss Test

Packet loss happens when data does not arrive and has to be resent – causing stutters, frozen video and lag. This test sends 60 small requests over 30 seconds and counts how many fail or time out.

Tool status: Functional with limitations Works, but there are technical limits explained on the page.

Request loss and stability

60 requests over 30 seconds, 2-second timeout each.

Median–ms
Minimum–ms
Jitter–ms
Failed requests–%

Target: . Nothing is measured until you press Start.

What this tool can and cannot do

Browsers can only use TCP-based HTTPS, which automatically resends lost packets. So this test detects severe loss (requests that fail or exceed a 2-second timeout) and latency spikes caused by retransmission, but it cannot count individual lost UDP/ICMP packets. A result of 0% means no requests failed, not a guarantee of zero packet loss.

Data sources: IPandNet test server

Understanding the results

Any failed requests on a wired connection indicate a real problem. Latency spikes (requests far slower than the median) often reveal hidden loss being corrected by retransmission.

Troubleshooting

  • Check cables and replace damaged or very old ones.
  • On Wi-Fi, reduce distance to the router and avoid interference from microwaves and thick walls.
  • Persistent loss on a wired connection should be reported to your ISP – include the time and results.

Frequently asked questions

How much packet loss is acceptable?

Ideally 0%. Under 1% is usually unnoticeable; 1–2.5% affects calls and games; above that, most real-time apps degrade badly.