Packet loss test
Check failed browser requests, latency and stability. This HTTP test is not a raw network-packet capture.
Request delivery heatmap
30 samplesRequest completion
- Received 0
- Failed 0
- Pending 30
What does my result mean?
Run the test to analyze transmission reliability for common online activities.
What this online packet loss test actually measures
The test sends 30 HTTP requests from your browser to the Internet Analysis endpoint. The displayed loss percentage is the fraction that fails or times out. It is an application-level reliability check, not a raw UDP or ICMP packet capture. TCP can recover lost network packets before the browser notices them.
How to interpret 0% or a failed sample
Zero failed requests means all 30 completed in this short run. It does not prove that your network has zero packet loss all day. One failed request out of 30 is about 3.3%; a timeout, server error or interrupted browser connection can cause it. Repeat before drawing conclusions.
Find whether the problem is Wi-Fi, the device or the ISP
- Run the test with heavy downloads and uploads paused.
- Repeat on the same device over Ethernet. If only Wi-Fi fails, investigate signal and interference.
- Compare a second device and repeat at the time the problem normally happens.
- Check the affected game or calling app too: its endpoint and protocol differ from this browser test.
- Save the actual sample count, duration and time of each run before contacting your provider.
Troubleshoot packet loss with good download speed · Understand jitter · Run the full connection-quality test
Measurement reference: IETF RFC 7680 defines IP-layer one-way packet loss; this browser check is a different measurement. See our methods and limitations. Reviewed September 10, 2026.