Online Ping Test — Ping Any Host
Send ICMP echo requests to any hostname or IP address from our server and see latency, packet loss and jitter — with a plain reading of what the numbers mean.
Pingr needs a quick check that you are a person before running more tests. This usually resolves by itself.
What this ping test measures
Pingr sends five ICMP echo requests to the host you enter and times how long each reply takes to come back. That round trip — out across the internet and back — is what everybody means by “ping”. The test runs from Pingr’s own server, not from your computer, so what you are measuring is the path between our probe and your target. If you want to know about your connection instead, the Internet Ping Test measures that directly from your browser.
How to read the result
Average is the figure most people mean by ping. Under 30 ms means the target is close or fronted by a CDN; 100–200 ms is a normal intercontinental round trip; above 250 ms usually means real distance or a satellite link rather than a fault. There is no tuning that removes the speed of light.
Minimum is the best the path managed — effectively the physical floor. Maximum shows the worst. A large gap between them means the path is queuing traffic somewhere.
Packet loss is the share of requests that got no reply. Any loss to a well-connected host is worth noticing, but loss on an ICMP test specifically is often not what it looks like: many routers and servers deliberately rate-limit ICMP, answering some echo requests and dropping the rest as a matter of policy. Loss with low latency usually means something intermittent or rate-limited; loss with high latency usually means congestion.
Jitter is how much each round trip differs from the one before it. It matters for anything real-time — voice, video, games — where arriving late and arriving unevenly are different problems. A steady 80 ms is far better for a call than an average of 40 ms that swings between 10 and 90. Turn on Deep Test for 20 packets instead of 5; jitter from five samples is barely a measurement.
Why a host might not answer ping
A very large share of the internet does not answer ICMP. Cloud load balancers, CDN edges, corporate firewalls and plenty of ordinary servers drop echo requests on purpose, because answering them offers an attacker a free way to map a network. So “no reply” is not the same as “offline”, and any tool that tells you otherwise is guessing.
When ping comes back empty, test something the host has a reason to answer. Website Ping runs DNS, TCP, TLS and a real HTTP request, and reports a site as reachable when it serves traffic normally even if it ignores ping entirely. Ping Port checks a single TCP port — and even a refused connection is useful, because a refusal proves the host is alive and reachable.
What you can enter
A hostname (example.com), an IPv4 address (8.8.8.8) or an IPv6 address (2606:4700:4700::1111). Paste a full URL with a path and Pingr will hand it to Website Ping rather than rejecting it, because a URL is a question about a website, not about a host.
Private, loopback, link-local and cloud-metadata addresses are refused, and a hostname that resolves to any of them is refused too — the whole request, not just the offending record. That is deliberate: a public diagnostics tool that will reach into private networks on request is a security hole with a friendly interface. More about what Pingr will and will not test.