Why this is not ICMP ping
The familiar ping command sends ICMP echo requests, which requires a raw socket and therefore root. Container platforms and serverless hosts do not grant that, so this tool opens an ordinary TCP connection to port 443 and times the handshake, falling back to port 80.
The number that comes back is comparable to ICMP round-trip time but not identical. A TCP handshake is one and a half round trips at the network level plus whatever the server spends accepting the connection, so expect it to read slightly higher than ICMP against the same host.
What the numbers mean
Three attempts are made and the minimum, average and maximum are reported. The minimum is the most useful single figure: it is the closest you get to the true network latency, because it is the attempt least affected by queuing and scheduling noise.
A wide spread between minimum and maximum matters more than a high average. Consistent 180 ms to a host on another continent is normal and fine. A range of 20 ms to 400 ms on the same connection suggests congestion, an overloaded server, or a saturated link somewhere in between.
Rough distance expectations
Light travels about 200 km per millisecond through fibre, and real paths are never direct, so a useful rule of thumb is that round-trip latency is roughly one millisecond per 100 km of physical separation plus per-hop processing.
Within one Indian metro, expect single-digit to low-double-digit milliseconds. Across India, roughly 20-60 ms. India to Europe or Singapore, around 100-180 ms. India to the US west coast, 200 ms and up. Substantially worse than these figures suggests a routing problem rather than distance.
When a host shows as unreachable
Unreachable here means neither port 443 nor port 80 accepted a connection. That is not the same as the host being down. A server that answers ICMP but runs no web service will show as unreachable, and so will one behind a firewall that drops connections from unknown addresses.
If you control the host, check that something is listening and that the firewall permits inbound connections from outside your network.
Frequently asked questions
Why is the result higher than ping from my laptop?
Two reasons. The measurement runs from this server rather than from your machine, so it reflects a different network path entirely. And a TCP handshake costs more than an ICMP echo, so it reads a little higher even along the same path.
What is a good latency figure?
It depends entirely on distance. Judge consistency rather than the absolute number: a stable figure appropriate to the distance is healthy, and wide variance between the minimum and maximum is the real warning sign.
Does a failed test mean the site is down?
Not necessarily. It means ports 443 and 80 did not accept a connection from this server. Firewalls, geographic blocking and services on non-standard ports all produce the same result.
Can I test a specific port?
Not with this tool -- it tries 443 then 80. Use the Port Checker to see which of the common service ports are accepting connections.