Online Ping Tool

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

Hostname or IP Address

Packets

Quick:

Pinging…

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.

For online gaming, under 20 ms is excellent and under 50 ms is very good — most players won't notice any lag. Under 100 ms is acceptable for casual gaming but may cause occasional issues in fast-paced titles. For web browsing and streaming, under 100 ms is perfectly fine since these applications are not sensitive to small latency variations. Anything over 200 ms will be noticeable as sluggishness, and over 500 ms makes real-time applications unusable.

The most common reason is a firewall blocking ICMP echo requests. Many servers and cloud providers (AWS, Google Cloud, Cloudflare) intentionally drop ICMP packets to prevent network reconnaissance, while the server still serves HTTP/HTTPS traffic normally. Other causes include: rate limiting (some routers deprioritize ICMP), the host being on a private network unreachable from the internet, or the hostname not resolving in DNS. A ping timeout (Request timeout) is not a reliable indicator that a host is down.

TTL (Time To Live) is a field in the IP packet header that limits how many router hops the packet can traverse. Each router decrements TTL by 1; when it reaches 0, the packet is discarded and an ICMP "Time Exceeded" error is sent back. This prevents packets from looping forever. In a ping response, the TTL value tells you approximately how many hops the reply packet has left. A TTL of 64 typically means Linux/macOS origin, 128 means Windows, and 255 means network equipment (Cisco routers). The starting TTL minus the received TTL gives an estimate of the hop count.

Ping is the tool/command used to measure round-trip time. Latency is the broader term for the delay in network communication — the time a packet takes to travel from source to destination (one-way) or back (RTT). Jitter is the variation in latency over time — measured as the standard deviation or mean deviation (mdev) of RTT values. High jitter (even with acceptable average latency) causes problems for real-time applications like VoIP and video calls, because packets arrive irregularly. For gaming and VoIP, low jitter (under 5 ms) is as important as low latency.

Ping uses ICMP (Internet Control Message Protocol) Echo Request and Echo Reply messages, defined in RFC 792. The ping tool sends an ICMP Echo Request packet to the target host. If the host is reachable and not blocking ICMP, it replies with an ICMP Echo Reply. The round-trip time (RTT) is the difference between when the request was sent and when the reply arrived. Ping does not use TCP or UDP — it operates at the network layer (Layer 3). Each packet carries a sequence number (icmp_seq) so out-of-order or dropped packets can be detected.

A ping flood (ICMP flood) is a type of Denial-of-Service (DoS) attack where an attacker sends ICMP Echo Requests to a target at a very high rate, overwhelming the target's network or processing capacity. The ping -f (flood) command can send thousands of packets per second. This is why many servers and firewalls block inbound ICMP — not because they're offline, but as a security measure. Performing a ping flood against servers you don't own is illegal in most jurisdictions. This tool sends only the number of packets you specify (4, 6, 8, or 10) — never a flood.

About This Online Ping Tool

This free Ping tool sends ICMP echo requests from our server to any hostname or IP address and streams the results to your browser line by line in real time. It supports both IPv4 and IPv6, lets you choose the packet count (4–10), and shows a packet loss and RTT summary when complete. Results reflect latency between our server and the target — not your local connection.

When to use this tool

Check if a remote host is reachable from a data-centre perspective
Measure baseline round-trip latency to a server or CDN edge node
Diagnose packet loss on a specific network path
Verify a host is responding before and after a configuration change

Standards & References

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 Range	Quality	Typical Cause	Impact
< 20 ms	Excellent	Local network or nearby CDN	Imperceptible for any use case
20 – 50 ms	Very Good	Same country / region	Ideal for gaming, video calls, VoIP
50 – 100 ms	Good	Cross-country or nearby continent	Fine for browsing, slight lag in gaming
100 – 200 ms	Acceptable	Intercontinental (e.g. US → EU)	Noticeable in real-time games, OK for video
200 – 500 ms	Poor	Long-distance routing or congestion	Sluggish browsing, poor VoIP, laggy games
> 500 ms	Very Poor	Satellite link, severe congestion	Timeouts 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.

In-depth guides and technical articles.

View all →

Internet Jul 8, 2026

Bufferbloat — Why Your Fast Connection Feels Slow and How Ping Under Load Reveals the Problem

Bufferbloat — oversized network buffers that add 300-800ms of latency during congestion — explains why 100 Mbps connections feel laggy during video calls. Standard ping tests miss it entirely because they test idle latency. Here's how to detect bufferbloat with a loaded ping test, why CoDel and CAKE algorithms solve it, and why DOCSIS cable connections are particularly susceptible during large uploads.

Internet Jun 23, 2026

A Successful Ping Doesn't Mean Your Service Is Running — What ICMP Actually Tells You and What It Doesn't

A successful ping proves the host's IP is reachable — not that any service is running. A failed ping could mean the host is down, ICMP is firewalled, or there's packet loss somewhere in the path — three completely different problems with different solutions. Here's what ping can and cannot diagnose, how to interpret latency patterns (consistent, variable/jitter, increasing), and the correct escalation from ping to traceroute to port check to service-level testing.

Internet Jun 17, 2026

Why Your Ping to the Other Side of the World Can Never Go Below ~150ms: The Speed-of-Light Floor

No network upgrade will get your ping to a server on the other side of the world below roughly 130-150ms — not because of congestion or old equipment, but because of the speed of light in fiber, which sets a hard physical floor on latency. Here's how to calculate that floor for any distance, why real fiber routes are longer than great-circle distance (making the floor even higher in practice), why satellite internet has its own altitude-driven latency profile, and how to interpret ping results to servers on different continents.

Internet Jun 12, 2026

ICMP and Ping: Why It Has No Ports, Why It's Blocked, and What "Ping Failed" Actually Tells You

Ping uses ICMP — a protocol with no ports, no connections, and no relationship to whether a web server or any other application is actually working. Here's why ping is so commonly blocked by firewalls, what ping success/failure actually tells you (and doesn't), and how blocking the wrong ICMP message type can cause silent, hard-to-diagnose connection failures via Path MTU Discovery.

Internet Jun 10, 2026

Network Diagnostics: The Systematic Workflow From Ping to Port Scan

A systematic diagnostic workflow finds network problems in minutes: ping → DNS lookup → traceroute → port scan. Each tool answers a specific question and eliminates a layer. Here's the complete process, what each result means, and how to distinguish local problems from remote ones.