Online Ping Tool

Send ICMP echo requests to any hostname or IP and see real-time response times line by line.

Quick:
Pinging…

        
β€”
Packets Sent
β€”
Received
β€”
Packet Loss
β€”
Avg RTT

Frequently Asked Questions

Ping measures round-trip time (RTT) β€” the time it takes for a small packet to travel from the server to the target host and back. Lower RTT means lower network latency. Results are shown in milliseconds (ms).

Many servers block ICMP echo requests via firewall rules (e.g. Google's main IPs, some CDNs). A non-response does not necessarily mean the host is down β€” the website may still be reachable via HTTP/HTTPS.

Packet loss is the percentage of packets sent that didn't receive a reply. 0% loss is normal and ideal. Loss above 5% suggests network instability, congestion, or a firewall dropping packets. 100% loss means the host is unreachable or blocking ICMP.

This tool runs the ping command on our server and streams the output to your browser in real time. Results reflect latency between our server and the target host, not your local connection.

How It Works

Enter a Host

Type any domain name or IP address. Use Quick buttons for common targets like 8.8.8.8 or google.com.

Real-Time Streaming

Each ping reply appears immediately as it arrives β€” no waiting for all packets to finish. Lines stream via Server-Sent Events.

Stats Summary

When pinging completes, packet loss, RTT min/avg/max, and received count are extracted and shown in a summary bar.

Understanding Ping Results

RTT RangeQualityTypical CauseImpact
< 20 msExcellentLocal network or nearby CDNImperceptible for any use case
20 – 50 msVery GoodSame country / regionIdeal for gaming, video calls, VoIP
50 – 100 msGoodCross-country or nearby continentFine for browsing, slight lag in gaming
100 – 200 msAcceptableIntercontinental (e.g. US β†’ EU)Noticeable in real-time games, OK for video
200 – 500 msPoorLong-distance routing or congestionSluggish browsing, poor VoIP, laggy games
> 500 msVery PoorSatellite link, severe congestionTimeouts likely, most real-time apps unusable

Common Ping Output Lines Explained

64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=12.3 ms

A successful reply. icmp_seq is the packet number. ttl (Time To Live) indicates remaining hops β€” decrements by 1 at each router. time is the round-trip latency in milliseconds.

Request timeout for icmp_seq 2

No reply received within the timeout window (1 second here). Could mean the host is down, ICMP is blocked by a firewall, or the packet was lost in transit.

4 packets transmitted, 4 received, 0% packet loss

The summary line. 0% loss is perfect. Even 1–2% loss on a stable host suggests a network issue between this server and the target.

rtt min/avg/max/mdev = 10.1/12.3/15.8/1.9 ms

RTT statistics. mdev (mean deviation) measures jitter β€” how consistent the response times are. High mdev with acceptable avg indicates an unstable connection.