Skip to tool

Free online tool

Ping Test / Packet Loss Test

e.g. example.com — a public hostname or IP address

Some information is sent to our server to provide this result. The target you enter is sent to our server, which attempts a connection on your behalf. It is not retained beyond the immediate request.

What this tool actually measures

This is not real ICMP ping. Traditional ping sends raw ICMP echo packets directly to a target — something the server environment this tool runs on genuinely cannot do; there is no raw-socket or ICMP access available to it. Instead, this tool times a series of HTTPS connection attempts to the target and reports how many succeeded and how long each one took. It's a real, useful approximation of reachability and responsiveness, but it is a measurably different signal than true ICMP ping, not a relabeled version of the same thing.

A real, verified example

Running four attempts against a target returns results like: 3 successful connections with real measured latencies and 1 failed attempt, for an overall packet loss of 25% and an average latency computed only across the successful attempts — confirmed by running this exact tool's own attempt-counting and loss/latency calculation logic for real.

Why the numbers can differ from traditional ping

Because this measures an HTTPS connection attempt rather than a raw ICMP packet, the two can genuinely disagree: a host with ICMP explicitly blocked by its firewall (common, deliberate practice) but a working HTTPS service will show here as reachable, while a host with ICMP open but no HTTPS service running at all will show as unreachable. Neither result is "wrong" — they're measuring different things.

How packet loss and latency are calculated

Each attempt is tried in sequence, not in parallel, so one attempt's timing never distorts another's. Packet loss is the percentage of attempts that failed to connect at all. Average latency is computed only from the attempts that actually succeeded — a lost attempt has no latency value to average in, so it's excluded rather than counted as zero or as the full timeout duration.

Targets are checked before any connection is attempted

A target that's a private, reserved, or loopback address is rejected before any connection attempt — including a hostname that resolves to one, not just an obviously private-looking address typed directly. This tool is for checking real, public targets you have a legitimate reason to test, not for probing internal networks.

Privacy

The target you enter is sent to our server, which attempts the connection on your behalf. Nothing you test is stored or logged beyond the immediate request.

Examples

  • Input: 4 connection attempts to a target

    Output: 4 attempts, 25% packet loss, 22ms average latency across successful attempts only