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 08:12:18 UTC |

| Check again |

Location	Result	Time	IP Address
Australia, Sydney	Timeout	-	129.6.15.25
Bosnia and Herzegovina, Novi Travnik	Ok	150.0 ms	132.163.96.1
Bulgaria, Sofia	Ok	145.2 ms	132.163.97.3
Canada, Montreal	Ok	41.3 ms	132.163.97.2
Switzerland, Bern	Ok	118.3 ms	132.163.96.2
Switzerland, Zurich	Ok	132.0 ms	132.163.97.2
China, Hohhot	5/6	185.2 ms	132.163.96.3
Cyprus, Larnaca	Ok	175.0 ms	132.163.96.1
Germany, Nuernberg	Ok	134.2 ms	132.163.96.2
Germany, Frankfurt am Main	Ok	130.0 ms	132.163.96.3
Germany, Frankfurt am Main	Ok	121.0 ms	132.163.96.2
Germany, Frankfurt am Main	Ok	132.0 ms	132.163.97.2
Germany, Koblenz	Ok	140.5 ms	132.163.97.4
Germany, Frankfurt am Main	Ok	150.7 ms	132.163.97.4
Denmark, Glostrup Municipality	4/6	191.0 ms	132.163.96.4
Spain, Bilbao	Ok	167.0 ms	132.163.96.6
Spain, Barcelona	Ok	138.0 ms	132.163.97.2
Finland, Helsinki	Ok	148.0 ms	132.163.96.1
Finland, Helsinki	Ok	146.0 ms	132.163.96.4
France, Gravelines	Ok	119.0 ms	132.163.97.1
France, Paris	2/6	144.5 ms	132.163.96.6
United Kingdom, London	Timeout	-	129.6.15.25
Hong Kong, Hong Kong	Timeout	-	132.163.97.4
Croatia, Zagreb	Ok	140.2 ms	132.163.96.2
Hungary, Budapest	2/6	176.5 ms	132.163.97.3
Israel, Petach Tikwa	Ok	176.2 ms	132.163.96.1
Israel, Netanja	Ok	172.0 ms	132.163.96.1
Iran, Tehran	Ok	203.0 ms	132.163.97.2
Iran, Tehran	Ok	206.0 ms	132.163.97.2
Iceland, Reykjavik (Miðborg)	Ok	161.0 ms	132.163.97.1
Italy, Como	Ok	135.2 ms	132.163.96.1
Japan, Tokyo	Ok	129.7 ms	132.163.97.2
South Korea, Seoul	Ok	162.7 ms	132.163.97.1
Kazakhstan, Almaty	5/6	210.0 ms	132.163.97.6
Lithuania, Pilaite	2/6	199.5 ms	132.163.96.1
Latvia, Riga	4/6	198.5 ms	132.163.97.1
Netherlands, Amsterdam	Ok	114.2 ms	132.163.97.1
Netherlands, Amsterdam	Timeout	-	129.6.15.25
Netherlands, Amsterdam	Ok	118.8 ms	132.163.97.1
Netherlands, Amsterdam	Ok	118.3 ms	132.163.96.6
Netherlands, Eygelshoven	Ok	124.2 ms	132.163.97.1
Norway, Oslo	Timeout	-	129.6.15.25
Poland, Warsaw	5/6	159.0 ms	132.163.97.3
Romania, Bacău	Ok	170.0 ms	132.163.97.4
Romania, Bucharest	Ok	154.8 ms	132.163.96.4
Serbia, Belgrade	Ok	150.7 ms	132.163.96.2
Russia, Moscow	Ok	157.7 ms	132.163.96.1
Singapore, Singapore	Ok	204.2 ms	132.163.96.3
Tor, Onion	Timeout	-	time.nist.gov
Tor, Onion	Timeout	-	time.nist.gov
Tor, Onion	Timeout	-	time.nist.gov
Turkey, Istanbul	Ok	155.0 ms	132.163.97.4
Ukraine, Khmelnytskyi	Ok	146.2 ms	132.163.96.1
United States, Dallas	5/6	20.6 ms	132.163.97.3
United States, Los Angeles	Ok	34.0 ms	132.163.97.1
United States, Houston	Ok	28.0 ms	132.163.96.1
United States, Miami	Ok	54.0 ms	132.163.97.3
South Africa, Johannesburg	Timeout	-	129.6.15.25