Multi-Location Ping
Ping a hostname or IP address from several locations around the world at the same time and compare reachability, packet loss and average latency per region.
- Runs on our servers
- Free to use
- API available →
About this tool
A single ping tells you how a host looks from one place. The Multi-Location Ping sends ICMP echo requests from servers on several continents at the same time and lays the results side by side: online/offline per location, packets received, average round-trip time and the IP each probe reached, with the best and worst averages summarised on top. It is the quickest way to tell a regional routing problem from a global outage and to see whether a CDN or anycast setup actually serves users nearby.
For the full output of a single probe use Ping Online; to follow the path use Traceroute.
How to use it — quick steps
- 01
Enter the hostname or ip address
Type or paste the hostname or ip address in the field above. The lookup runs from our servers.
- 02
Press "Ping from all locations"
Press "Ping from all locations" or Ctrl + Enter. It takes a few seconds. Results can be copied.
- 03
Read the result
It appears in the dark panel under the form in a few seconds. Every block has [copy] and other actions.
Key features of this tool
Worldwide vantage points
Probes run from data centres on several continents, so you see how the host responds to users far from it.
Loss and latency per region
Each location reports packets received and the average round-trip time, with the best and worst averages summarised.
Resolved IP per location
The address each probe reached, useful for spotting GeoDNS, anycast and CDN routing differences.
Frequently asked questions
Why does latency differ so much by location?
Round-trip time grows with distance and the number of networks crossed: a server in Frankfurt answers Europe in a few milliseconds and Sydney in hundreds. CDNs and anycast fix this by answering from a nearby node.
A location shows offline while others are online
The host may block ICMP from that region, a route may be down, or the probe timed out. Compare with the HTTP Status Code Checker before concluding the service itself is down.
Why are the resolved IPs different per location?
GeoDNS and anycast return the address of the nearest node; seeing several IPs is normal for large sites and CDNs.
Where does the data come from?
The APIVoid Ping Test API, which runs the probes from its own servers in each region.