Loss Rate
%
0.0%
Of all requests sent
Professional browser-based reliability test
Packet Loss Test
Send a burst of timed requests to this site's own server and see exactly how many make it back cleanly — the metric behind dropped calls, rubber-banding and frozen video.
Live loss gauge
Same-origin test server
Private, browser-side history
Reliability Overview
Loss rate, sent/lost counts and average latency update live while the test runs.
Ready to begin
Start the test right away
One button, front and center — sends a burst of concurrent, timed requests and tracks exactly what comes back.
Sent
reqs
0reqs
Total requests dispatched
Lost
reqs
0reqs
Timed out or failed
Avg Latency
ms
0ms
Of successful requests
Reliability GradePerfect
A+
Run a test to see how many requests make it through cleanly.
Requests SentVolume
0
Total concurrent, timed requests in this run.
Avg LatencySuccessful
0 ms
Average round trip for requests that made it back.
Live Loss Trend
Cumulative loss rate (%)
Advanced connection & device details
ASNDetecting…
CountryDetecting…
IP TimezoneDetecting…
Request SchemeDetecting…
Browser Downlink EstimateNot supported by this browser
Browser RTT EstimateNot supported by this browser
Browser–
Operating System–
Screen Resolution–
Viewport Size–
Device Pixel Ratio–
CPU Cores–
Device Memory–
Language–
Cookies Enabled–
User Agent: –
Burst Request ProbingSends concurrent, timed requests and tracks what doesn't come back.
Own Test ServerRuns on this site, never a third party.
Clear Pass/Fail SignalEvery request is counted as received or lost — nothing guessed.
Private by DefaultHistory is stored only in your browser.
Ready. Press Start Test to begin.
PACKET LOSS TEST WORKFLOW
Honest Request-Level Loss, Clearly Labelled
Browser JavaScript has no access to raw ICMP ping, so this tool measures loss the way a real web app experiences it: it opens several concurrent HTTP requests to this site's own server (Controllers/SpeedTestController.cs), gives each one a fixed 1.5-second window to complete, and counts anything that errors or doesn't return in time as lost. That is a genuine, honest measurement of request reliability on this path — it is a proxy for classic ICMP packet loss, not an identical measurement, since a single HTTP request can itself involve several underlying network packets. Loss shown here reliably reflects real problems (weak Wi-Fi, congestion, flaky hardware) even if the exact percentage can differ slightly from a command-line ping -c tool.
Packet Loss Test FAQ
What is packet loss?
Packet loss is data that never arrives at all. Even a small amount can cause dropped words in calls, frozen frames in video and rubber-banding in online games, because the sending and receiving ends have to detect the gap and recover from it.
Is this the same as a command-line "ping -c" packet loss test?
Not exactly. A browser cannot send raw ICMP packets, so this tool sends real HTTP requests to this site's own server and counts anything that errors or fails to respond within 1.5 seconds as lost. It's an honest, request-level measurement of reliability on this path rather than an ICMP-identical one.
What counts as a good result?
0% is ideal and very achievable on a healthy connection. Under 1% is generally unnoticeable, 1–2.5% can cause occasional glitches, and above 5% is likely to be clearly noticeable in calls, streaming and games.
Why did I get some loss on a connection that feels fine?
Brief loss can happen even on good connections due to momentary Wi-Fi interference or a busy server, especially in short tests. Try a longer test length and run it a few times before drawing conclusions.
Is my data stored?
No. Requests are sent live and never written to disk. Recent results are kept only in your browser's local storage.
Why did the test show 100% loss?
This usually means the test requests never reached the server at all — check that you're online and that no firewall, VPN or ad blocker is blocking requests to this site.
Test History
Packet Loss Test Settings
Save local historyStores your last tests only in this browser, not on our server.
Test length controls how many requests are sent — Quick (20), Standard (40) or Extended (80), each with up to 5 in flight at once and a 1.5-second timeout. Longer tests give a more statistically reliable loss percentage.