Free online ping test with real IPv4 and IPv6 (ICMPv6) echo from our London probe, reporting per-attempt round-trip time, TTL/hop limit, average, min, max, and packet loss. Set the packet size, interval, TTL, and DSCP, test the Don't-Fragment bit, or discover the path MTU. Use it to verify a service is responsive and measure baseline latency. If a host filters ICMP, 100% loss does not necessarily mean it is down.
Ping sends an ICMP echo request to a host and times how long the matching echo reply takes to come back. That round-trip time, measured in milliseconds, is your latency to the host. This tool sends real ICMP (and ICMPv6 over IPv6) from a probe in London, so the numbers reflect an actual network path rather than a browser request. It reports each attempt's round-trip time and TTL, then summarises the minimum, average, maximum, and packet loss across the run.
Packet loss is the share of echo requests that got no reply. A few percent of loss is usually harmless, but rising loss or a wide gap between the minimum and maximum times (jitter) points to congestion or an unstable link. One important gotcha: 100% loss does not always mean the host is down. Many firewalls silently drop ICMP, so a well-run server can be fully reachable on 443 while never answering a ping.
Setting the Don't-Fragment bit and varying the packet size lets you probe the path MTU: the largest packet that can cross the whole route without fragmentation. If large DF-marked packets fail while small ones succeed, an MTU mismatch somewhere on the path is the likely cause.
For nearby servers, under 30 ms is excellent and under 100 ms is fine for most uses. Because this probe is in London, times to distant regions will be higher simply due to physical distance, which is normal.
Many hosts and firewalls block or rate-limit ICMP echo, so the server never replies to ping even though it serves traffic normally. Test the actual service port with a port checker to confirm reachability.
TTL (Time To Live) is a hop counter that starts at a set value and drops by one at each router. The value returned hints at how many hops away the host is and which operating system family it runs.
Yes. This tool sends ICMPv6 echo when a host has an IPv6 address, so you can measure latency and loss over IPv6 the same way you would over IPv4.