Ping Output Analyser
Paste any ping run and get latency, jitter and loss with a plain-English verdict.
How this reads your output
The tool reads every per-packet time and the summary from a ping run, computes latency, jitter and loss, and then names the single worst problem rather than leaving you to interpret a wall of numbers. Loss outranks jitter outranks latency, because that is the order in which they wreck real-time applications.
What the results mean
- Average latency
- The typical round trip. Below 50 ms feels instant; above 150 ms is sluggish on calls and in fast games.
- Jitter
- How much the latency varies between packets. This, not the average, is what makes voice break up.
- mdev
- What Linux ping prints. It is deviation from the average, not jitter, and is shown so you can match it to your terminal.
- Loss
- The share of packets that never returned, when the sample is large enough to judge.
Common problems and fixes
- The verdict blames jitter but my latency looks fine
- That is the point — a low average with high variation is worse for calls than a high, steady latency. The verdict weighs what actually disrupts real-time use.
- It says the sample is too small
- Fewer than 20 packets cannot support a confident verdict. Re-run with ping -n 50 or ping -c 50 and paste that.
Frequently asked questions
Which matters more, latency or jitter?
For real-time use, jitter usually matters more. A steady 120 ms is workable for a call; a latency that swings between 20 and 120 ms is not, even though its average is lower. This tool weighs them accordingly rather than just reporting the average.
What should I ping to test my connection?
A nearby, reliable target like 1.1.1.1 or 8.8.8.8 tests your connection to the internet’s edge. Pinging a specific game or work server instead tells you about the path to that server, which may be the thing you actually care about.