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.

Rapport pour time.nist.gov

Info Ping HTTP TCP UDP MTR DNS

Ping du serveur time.nist.gov

Vérifié le Oct 23, 2026 05:01:26 UTC |

| Revérifier |

Emplacement	Résultat	Temps	Adresse IP
Australia, Sydney	Ok	166.2 ms	132.163.97.2
Bosnia and Herzegovina, Novi Travnik	Ok	150.0 ms	132.163.97.6
Bulgaria, Sofia	Ok	145.0 ms	132.163.97.6
Canada, Montreal	Délai d'attente	-	129.6.15.25
Switzerland, Bern	Ok	117.5 ms	132.163.96.4
Switzerland, Zurich	Ok	132.0 ms	132.163.97.2
China, Hohhot	Ok	180.0 ms	132.163.96.3
Cyprus, Larnaca	Ok	177.5 ms	132.163.96.1
Germany, Nuernberg	Ok	130.2 ms	132.163.96.2
Germany, Frankfurt am Main	Ok	130.0 ms	132.163.96.6
Germany, Frankfurt am Main	Ok	121.0 ms	132.163.97.6
Germany, Frankfurt am Main	Ok	134.3 ms	132.163.97.4
Germany, Koblenz	Ok	165.2 ms	132.163.96.6
Germany, Frankfurt am Main	Ok	148.0 ms	132.163.96.2
Denmark, Glostrup Municipality	Ok	150.3 ms	132.163.96.3
Spain, Bilbao	Ok	166.2 ms	132.163.97.3
Spain, Barcelona	Ok	137.0 ms	132.163.97.2
Finland, Helsinki	Ok	149.7 ms	132.163.96.2
Finland, Helsinki	Ok	146.0 ms	132.163.96.6
France, Gravelines	Ok	118.0 ms	132.163.97.3
France, Paris	Délai d'attente	-	129.6.15.27
United Kingdom, London	Ok	120.8 ms	132.163.97.1
Hong Kong, Hong Kong	Délai d'attente	-	132.163.97.2
Croatia, Zagreb	Ok	146.0 ms	132.163.96.3
Hungary, Budapest	Ok	173.8 ms	132.163.96.3
Israel, Petach Tikwa	Ok	176.2 ms	132.163.96.1
Israel, Netanja	Ok	172.2 ms	132.163.96.1
Iran, Tehran	Ok	214.5 ms	132.163.97.6
Iran, Tehran	Ok	199.2 ms	132.163.96.1
Iceland, Reykjavik (Miðborg)	Ok	161.3 ms	132.163.97.2
Italy, Como	Ok	139.2 ms	132.163.97.2
Japan, Tokyo	Ok	130.0 ms	132.163.97.1
South Korea, Seoul	Ok	162.7 ms	132.163.97.4
Kazakhstan, Almaty	Ok	207.3 ms	132.163.96.6
Lithuania, Pilaite	Ok	182.3 ms	132.163.97.2
Latvia, Riga	Ok	181.0 ms	132.163.97.1
Netherlands, Amsterdam	Ok	117.7 ms	132.163.96.3
Netherlands, Amsterdam	Ok	117.0 ms	132.163.97.6
Netherlands, Amsterdam	Ok	118.0 ms	132.163.96.4
Netherlands, Amsterdam	Ok	118.0 ms	132.163.97.1
Netherlands, Eygelshoven	Ok	124.0 ms	132.163.96.6
Norway, Oslo	Ok	141.0 ms	132.163.97.6
Poland, Warsaw	Délai d'attente	-	129.6.15.27
Romania, Bacău	Ok	171.8 ms	132.163.96.6
Romania, Bucharest	Ok	154.7 ms	132.163.96.6
Serbia, Belgrade	Ok	150.5 ms	132.163.97.4
Russia, Moscow	Ok	159.3 ms	132.163.96.2
Singapore, Singapore	Ok	198.3 ms	132.163.96.4
Tor, Onion	Délai d'attente	-	time.nist.gov
Tor, Onion	Délai d'attente	-	time.nist.gov
Tor, Onion	Délai d'attente	-	time.nist.gov
Turkey, Istanbul	Ok	154.0 ms	132.163.97.2
Ukraine, Khmelnytskyi	Ok	151.2 ms	132.163.97.6
United States, Dallas	Délai d'attente	-	129.6.15.27
United States, Los Angeles	Ok	35.0 ms	132.163.97.3
United States, Houston	Ok	28.0 ms	132.163.96.2
United States, Miami	Délai d'attente	-	129.6.15.25
South Africa, Johannesburg	Délai d'attente	-	129.6.15.25