Ping Test
Check host reachability and measure round-trip latency.
Sends 4 ICMP echo packets from our server to the target and reports round-trip time, packet
loss, and TTL. Useful as a quick reachability test and for rough latency comparisons. Results
reflect our server's path to the target — your own network may see different numbers because
it takes a different route.
Running...
Reading the result
- Round-trip time (ms) — total time for a packet to reach the target and come back. Local hosts: <5 ms. Same country: 10–80 ms. Cross-continent: 100–300 ms. Satellite: 500+ ms.
- Packet loss — out of 4 packets, how many got back. Anything >0 on a stable network is unusual.
- TTL — remaining hop count returned by the target. Common starting values are 64 (Linux), 128 (Windows), 255 (some network gear); the value you see has been decremented by the number of routers in between.
- Variance — large gaps between min and max times suggest congestion somewhere along the path.
When to use it
- Is the host alive? The classic "ping it" sanity check before deeper debugging.
- Comparing latency to different regions — ping multiple targets and compare numbers.
- Quick outage check — if your own ping succeeds but mine fails, the issue is between our networks, not at the destination.
- Confirming firewall behavior — many hosts deliberately drop ICMP. A failing ping doesn't always mean the host is down.
Limitations
- Ping measures latency for tiny ICMP packets. Real application performance over TCP/HTTP can be very different — that's what tools like traceroute and HTTP-level checks are for.
- Some hosts (Cloudflare-fronted, some clouds) rate-limit or block ICMP. They're fine; ping just can't tell.
- Latency from our server is one data point. For "is it slow for my users", measure from your users' networks.