How do I run a global ping test?

Enter any domain or IP address into the ping tool and click Check. The test runs simultaneously from 50+ nodes across different countries, ISPs, and data centers, returning latency and packet loss data from each location within seconds. No account or installation required.

What does packet loss mean in a ping test?

Packet loss is the percentage of ICMP echo requests that were sent but received no reply. 0% is ideal. Loss above 1–2% on a clean connection typically indicates a routing problem, a firewall filtering ICMP traffic, or server congestion affecting specific network paths.

Can I ping a server from a specific country?

Yes. Use the country-specific node pages (for example /ping/germany or /ping/india) to run a ping check exclusively from nodes in that country. This is useful for diagnosing regional routing issues or CDN misconfigurations that only affect certain geographic areas.

How is this different from running ping on my own computer?

Your local ping only shows latency from your own location. This tool pings simultaneously from 50+ locations worldwide, revealing whether a server is unreachable globally or only from specific regions or ISPs — essential for identifying CDN misconfigurations or regional network outages.

Ping Test for 1.1.1.1

Advanced Settings

Show world map

Info Ping HTTP TCP UDP MTR DNS

Ping server 1.1.1.1

Permanent link |

Location	Result	Min/Avg/Max	IP Address
Albania, Tirana
Australia, Sydney
Bosnia and Herzegovina, Novi Travnik
Bulgaria, Sofia
Canada, Montreal
Switzerland, Bern
Chile, Santiago
China, Hohhot
Germany, Nuernberg
Germany, Frankfurt am Main
Germany, Frankfurt am Main
Germany, Limburg
Germany, Frankfurt am Main
Germany, Duesseldorf
Denmark, Glostrup Municipality
Spain, Bilbao
Finland, Helsinki
Finland, Helsinki
France, Gravelines
France, Paris
United Kingdom, London
Georgia, Tbilisi
Greece, Athens
Hong Kong, Hong Kong
Croatia, Zagreb
Hungary, Budapest
Indonesia, Jakarta
Israel, Petach Tikwa
Israel, Netanja
India, New Delhi
Iceland, Reykjavik (Miðborg)
Italy, Como
Kuwait, Kuwait City
Lithuania, Pilaite
Latvia, Riga
Moldova, Chisinau
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Norway, Oslo
Poland, Warsaw
Romania, Bacău
Romania, Bucharest
Serbia, Belgrade
Russia, St Petersburg
Singapore, Singapore
Turkey, Istanbul
Taiwan, Taipei
United States, Miami
United States, Dallas
United States, Kansas City
United States, Dallas
South Africa, Johannesburg

Global ICMP Ping & Network Latency Test

Ping sends ICMP echo requests to a target and measures how long each packet takes to return. This tool runs that test simultaneously from over 50 nodes across different countries, ISPs, and data centers. The result is a quick read on whether your server is reachable globally and how response times vary by region — without installing anything or logging in anywhere.

Latency and Packet Loss

Latency is the round-trip time in milliseconds. What matters is not just the number but how it varies across locations — a server answering in 8ms from Germany and 270ms from Australia is completely normal. The same server timing out in Singapore while responding fine elsewhere is a problem specific to that path. Packet loss above 1–2% on a clean internet connection is worth investigating further.

Anycast & BGP Routing

CDNs like Cloudflare, Fastly, and AWS announce the same IP from multiple locations simultaneously using Anycast. A ping from Frankfurt to an Anycast address should hit a nearby edge node and return in single-digit milliseconds. If Singapore returns 150ms to the same IP, traffic is likely routing to the wrong region — usually a BGP configuration issue on the CDN or a transit provider not accepting the announcement locally.

Live Monitoring Mode

A standard ping sends a few packets and stops. Live mode runs for 60 seconds continuously and plots each response on a chart as it arrives. This is the right approach when you suspect intermittent drops — a one-off test might catch a clean window, while a 60-second stream shows the loss spikes that are actually hitting users. It is also useful during incident response to watch whether a fix is taking effect in real time.