📡 Ping Test
Check whether a host answers and how long the round trip takes, measured from our servers rather than your own connection. That makes it useful for telling apart “the site is down for everyone” from “the site is down for me”.
What is being measured
Our server sends an ICMP echo request to the host and reports the reply: the resolved address, the round trip in milliseconds, the TTL left on the packet and the payload size. The timing is between our machine and the target, not between you and it - which is the point. A host that answers us but not you is a problem on your route; a host that answers neither is genuinely unreachable.
The name has to resolve before anything can be pinged. An error naming the host rather than a timeout means DNS failed, so check the A records before you go looking for a network fault.
The TTL in the reply is not a DNS TTL
Same three letters, unrelated meaning. Here it is a hop counter in the IP header: the sender picks a starting value and every router decrements it by one, discarding the packet at zero so a routing loop cannot run forever. Subtract to count the hops:
reply TTL 117 started at 128 (Windows) -> 11 routers crossed
reply TTL 53 started at 64 (Linux) -> 11 routers crossed
Frequently asked questions
What is a good ping time?
Under 30 ms is same-region and feels instant, 30-100 ms is normal cross-country traffic, and anything past 150 ms is noticeable in a call or a game. Satellite links sit near 600 ms and there is nothing wrong with them.
Why does ping fail when the website loads fine?
ICMP and HTTP are separate protocols. Blocking ping is a common hardening step and costs the operator nothing, so a silent host is usually a filtered one. Test port 443 instead if you want to know whether the site is up.
Why is the ping time here different from my own?
The packet starts from our server, so it takes a different path and crosses
different networks. Use this to check the host, and your own
ping command to check your connection to it.