Ping Test
Measure latency and packet loss to a host — from our server and from locations worldwide.
- via Check-Host.net
ICMP and TCP ping
We send real ICMP echo requests where possible, and also a TCP ping to a port for hosts that drop ICMP — many do, yet still work perfectly. You get min, average, max and jitter.
Global latency
Alongside our own measurement, we ping from dozens of countries via Check-Host.net so you can see latency and reachability from where your users actually are.
Latency, jitter and loss
Every run reports minimum, average and maximum round-trip time, jitter and packet loss, so you can tell a slow link from an unstable one.
Frequently asked questions
Why does ping fail while the website works?
Many servers and firewalls drop ICMP echo requests. Our TCP ping connects to a real port, so it still measures latency when ICMP is blocked.
What is a good ping?
Under 50 ms is excellent, under 150 ms is fine for most uses, and above 300 ms is noticeable in calls and games. Distance alone adds about 1 ms of round trip per 100 km.
How do I ping a specific port?
Write the port after the host, for example example.com:22. The TCP ping then measures how long a connection to that port takes. Without a port it uses 443.
Why do the worldwide results differ from ours?
Latency depends on distance and routing, so nodes far from the host show higher times. A node that cannot reach the host at all while others can points to a regional block or a routing problem.