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 65+ 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 65+ 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.

Report for time.nist.gov

Info Ping HTTP TCP UDP MTR DNS

Ping server time.nist.gov

Checked Oct 23, 2026 19:45:39 UTC |

| Check again |

Location	Result	Time	IP Address
Albania, Tirana	4/6	338.0 ms	132.163.96.1
Australia, Sydney	Ok	186.0 ms	132.163.96.1
Bosnia and Herzegovina, Novi Travnik	Ok	150.0 ms	132.163.97.3
Bulgaria, Sofia	Timeout	-	129.6.15.26
Canada, Montreal	Ok	41.0 ms	132.163.96.4
Switzerland, Bern	Ok	118.8 ms	132.163.97.2
Switzerland, Zurich	Ok	131.3 ms	132.163.96.1
China, Hohhot	Ok	184.0 ms	132.163.97.1
Cyprus, Larnaca	Ok	175.8 ms	132.163.96.6
Germany, Nuernberg	Ok	136.0 ms	132.163.96.1
Germany, Frankfurt am Main	Ok	131.0 ms	132.163.96.1
Germany, Frankfurt am Main	Ok	121.0 ms	132.163.97.3
Germany, Frankfurt am Main	Ok	135.3 ms	132.163.96.2
Germany, Koblenz	Timeout	-	129.6.15.25
Germany, Frankfurt am Main	Timeout	-	129.6.15.25
Denmark, Glostrup Municipality	3/6	196.7 ms	132.163.96.1
Spain, Bilbao	Ok	166.3 ms	132.163.97.1
Spain, Barcelona	Ok	137.2 ms	132.163.97.4
Finland, Helsinki	Ok	148.2 ms	132.163.96.3
Finland, Helsinki	Ok	146.0 ms	132.163.97.1
France, Gravelines	Ok	117.5 ms	132.163.96.3
France, Paris	2/6	143.0 ms	132.163.96.3
United Kingdom, London	Ok	128.0 ms	132.163.97.4
Hong Kong, Hong Kong	Timeout	-	132.163.96.6
Croatia, Zagreb	Ok	137.2 ms	132.163.97.3
Hungary, Budapest	2/6	183.5 ms	132.163.96.2
Israel, Petach Tikwa	Ok	173.2 ms	132.163.97.6
Israel, Netanja	Ok	170.5 ms	132.163.97.6
Iran, Tehran	Ok	216.2 ms	132.163.96.1
Iran, Tehran	Ok	242.5 ms	132.163.96.1
Iceland, Reykjavik (Miðborg)	Ok	161.3 ms	132.163.97.4
Italy, Como	Ok	134.3 ms	132.163.97.4
Japan, Tokyo	Ok	129.5 ms	132.163.96.4
South Korea, Seoul	Ok	165.5 ms	132.163.96.2
Kazakhstan, Almaty	Ok	207.3 ms	132.163.96.1
Lithuania, Pilaite	2/6	216.0 ms	132.163.97.2
Latvia, Riga	1/6	216.0 ms	132.163.97.3
Moldova, Chisinau	Timeout	-	129.6.15.25
Netherlands, Amsterdam	Ok	119.3 ms	132.163.96.1
Netherlands, Amsterdam	Ok	117.0 ms	132.163.97.6
Netherlands, Amsterdam	Ok	118.8 ms	132.163.97.1
Netherlands, Amsterdam	Ok	118.5 ms	132.163.96.2
Netherlands, Eygelshoven	Ok	131.8 ms	132.163.97.2
Norway, Oslo	Ok	141.0 ms	132.163.97.1
Poland, Warsaw	3/6	171.7 ms	132.163.96.1
Romania, Bacău	Ok	186.5 ms	132.163.96.1
Romania, Bucharest	Timeout	-	129.6.15.27
Serbia, Belgrade	Timeout	-	129.6.15.25
Russia, Moscow	Ok	158.5 ms	132.163.96.6
Singapore, Singapore	Ok	199.2 ms	132.163.97.4
Tor, Onion	Timeout	-	time.nist.gov
Tor, Onion	Timeout	-	time.nist.gov
Tor, Onion	Timeout	-	time.nist.gov
Turkey, Istanbul	Ok	152.8 ms	132.163.96.6
Ukraine, Khmelnytskyi	Ok	150.2 ms	132.163.96.2
United States, Dallas	Ok	21.0 ms	132.163.97.2
United States, Los Angeles	Ok	35.0 ms	132.163.96.2
United States, Houston	Ok	28.0 ms	132.163.97.2
United States, Miami	Timeout	-	129.6.15.25
South Africa, Johannesburg	Ok	275.0 ms	132.163.96.2