Global ping

Measure round-trip latency, jitter and packet loss from real public probes, with every result tied to the node that returned it.

No measurement yetSubmit a public target to see the probes and measurement evidence that actually return.

Understand latency and packet loss

Ping uses repeated probes to measure round-trip time and missing replies. Enter a public IP or hostname and compare locations as a first step in connection troubleshooting.

Two examples, explainedIllustrative · not live results

Consistent repliesOne probe

Example observation: Average 35 ms · jitter 2 msPacket loss 0%
How to interpret it: Little variation in this sampleNot a bandwidth or uptime guarantee

Variable repliesOne probe

Example observation: Average 180 ms · jitter 80 msPacket loss 10%
How to interpret it: Repeat to confirm the patternInspect the path with MTR

Not a speed testPing measures round-trip replies, not download bandwidth or your device’s access speed.

Common questions

Can a website work when Ping fails?

Yes. A host can block ICMP while allowing HTTPS. Check TCP port 443 or run an HTTP/TLS test.

Why do locations show different results?

Distance, network interconnection and routing vary. Compare probes near your actual users rather than choosing only the fastest result.

What is a normal latency?

There is no universal threshold. Compare the same probe and target over time, then judge against the application’s latency requirements.

Does 0% loss guarantee stability?

No. It means no replies were missing in this sample. Short tests can miss intermittent problems; compare results across different times.

Why does jitter matter?

Variable latency can affect calls, video and real-time interactions. Consider packet loss and application behavior alongside average latency.

Can I compare IPv4 and IPv6 results?

Yes, with context. They may use different routes or destination servers. Check the resolved target address and probe location first.