Ping Result Analyzer

Parse pasted ping output for packet loss and min/avg/max latency, with interpretation.

Paste the raw output of a ping run and this tool extracts the packets sent/received, packet loss percentage, and the min/avg/max round-trip time (RTT), then grades it ok / warning / danger at a glance. It recognizes both the Windows form (Packets: Sent = 4, Received = 4) and the Linux/macOS form (4 packets transmitted, 4 received).

You no longer have to read the numbers by hand to tell whether there is loss or high latency, which makes it handy for first-pass network triage. To turn repeated latency samples into statistics, use the latency percentile calculator; to grade a server's speed, see the response time tiers.

Paste ping outputPaste the output of a Windows or Linux/macOS ping command. No network calls are made.

Paste the full ping output and we will analyze packet loss and response time.

Formats you can paste

You only need the summary lines of a ping run. Either of these two formats is recognized.

Linux / macOS: 4 packets transmitted, 4 received, 0% packet loss and rtt min/avg/max/mdev = 1.2/3.4/5.6/0.7 ms (or round-trip min/avg/max = ...)
Windows: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) and Minimum = 1ms, Maximum = 3ms, Average = 2ms

How it grades

The status uses the rules below, taking whichever of average latency or loss is worse.

OK: 0% loss and average RTT below 100ms
Warning: loss up to 10%, or average RTT 100–250ms
Danger: loss above 10%, or average RTT above 250ms

High latency points to path congestion or physical distance; packet loss points to a wireless hop, overload, or an MTU problem.

Frequently asked questions

Which lines should I copy and paste?

Paste the entire ping output. The tool automatically finds the summary line (packets transmitted / Packets: Sent) and the RTT line. Even a partial paste works as long as a recognizable line is present.

Does it support both Windows and Linux formats?

Yes. It recognizes Windows 'Packets: Sent/Received/Lost' and 'Minimum/Maximum/Average', as well as Linux/macOS 'packets transmitted/received', '% packet loss', and 'rtt'/'round-trip min/avg/max' lines.

How much packet loss is a problem?

Ideally it should be 0%. Even sporadic 1-2% loss can affect TCP retransmission and video-call quality, and anything above 10% is treated as a clear fault.

What does a high average response time suggest?

Physical distance (intercontinental), path congestion, wireless-hop delay, or router queuing. It also helps to watch how much it varies (mdev/jitter).

Is what I paste sent to a server?

No. All parsing runs entirely in your browser with regular expressions, and the ping output you paste is never transmitted or stored anywhere.