Localised Ping Output Parser
Analyse ping output in German, French, Spanish, Italian, Dutch or Portuguese.
What you paste
Parsed in your browser — never uploadedHow this reads your output
Windows localises ping output, so a German machine reports Zeit rather than time and a French one reports temps. Every tool that parses only English fails on those, which is unhelpful given the person pasting is usually troubleshooting in their own language. The reply lines are matched against patterns for each supported language, the one with the most matches wins, and the figures are computed from the per-packet round trips.
What the results mean
- Jitter
- The mean difference between consecutive replies, following RFC 3550. It is not the same as the mdev figure Linux ping prints, which measures deviation from the average instead.
- Spikes
- Replies more than three times the average. A few spikes in an otherwise steady run point at something else briefly taking the link.
- The plot
- Round trip over the run. Shape matters more than the summary: steady variation and occasional spikes are different faults.
Common problems and fixes
- No replies were recognised
- Paste the reply lines rather than only the summary, since jitter cannot be computed from a summary. If your output is in a language not listed, the numbers are still there: the figures with ms after them are the round trips, and they can be pasted into the latency percentile calculator as bare numbers.
- The results look fine but the connection feels bad
- Four replies is the Windows default and far too few to characterise anything. Run it with a count of at least fifty, and run it while the connection is actually being used, since a test on an idle link tells you about an idle link rather than about the moment the problem happens.
Frequently asked questions
Which languages are supported?
English, German, French, Spanish, Italian, Dutch and Portuguese. Those cover the localisations that turn up most often in support conversations. The detected language is reported so you can confirm it read the output correctly.
Why does Linux ping show mdev rather than jitter?
They measure different things. Linux mdev is the mean deviation from the average round trip; jitter as RFC 3550 defines it is the mean difference between consecutive packets. A run that drifts slowly has low jitter and high mdev, and one that alternates has the reverse.
How many packets should I send?
At least fifty for a usable picture, and several hundred if you are chasing something intermittent. The Windows default of four tells you the host is reachable and nothing more.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/ping-analyzer-multilingual/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="Localised Ping Output Parser" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/ping-analyzer-multilingual/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.
More in Interpreter
- Ping Output AnalyserPaste any ping run and get latency, jitter and loss with a plain-English verdict.
- True Jitter Calculator (RFC 3550)Measure real jitter — the variation between consecutive packets, not deviation from the average.
- Packet Loss Significance CheckerMeasure packet loss from ping output — and know when the sample is too small to trust.