Quick Ping: hetzner
Real-time latency testing to www.hetzner.com
Ping Test - www.hetzner.com
Test network latency and connection quality
Hetzner Ping Test
This test measures latency from seven independent global test nodes (six in Europe and one in Australia) to Hetzner's public endpoint. Hetzner is a hosting provider built around data centers rather than a broad anycast edge, so the numbers here reflect the quality of the path from each test node into Hetzner's network, not the latency a reader would see from their own device.
Because hosting providers concentrate their capacity in a small number of regions, the distance between a test node and the nearest Hetzner location has a large effect on the result. A node close to a Hetzner data center in Germany or Finland will usually show much lower latency than one on another continent.
Why Test Hetzner Ping?
- Server responsiveness: Gauge how quickly a Hetzner Cloud server or dedicated server can be reached from different regions.
- Region selection: Compare latency from several locations before deciding where to deploy an instance.
- Storage Box access: Check reachability and response times for Hetzner Storage Box endpoints.
- Network troubleshooting: Spot routing problems or congestion between your users and Hetzner's network.
- Migration planning: Estimate user-perceived latency before moving workloads onto Hetzner.
How to Run the Hetzner Ping Test
- Keep the default Hetzner target host, or paste your own server IP or regional endpoint into the host field.
- Start the test to send probes from every available global node at once.
- Read the results per node to see how latency and packet loss differ by region.
What the Results Mean
Latency is the round-trip time for a probe to reach Hetzner's network and come back. Lower values mean a short, uncongested path, while high values point to geographic distance or routing detours.
- Under 60 ms (green): Excellent — the node sits close to a Hetzner location with a clean route.
- 60–120 ms (teal): Good — typical for regional or cross-country links.
- 120–200 ms (yellow): Fair — noticeable distance or some network congestion.
- Over 200 ms (red): Poor — long-haul or heavily loaded paths.
- Any packet loss above 0%: A danger sign that packets are being dropped, which hurts real traffic far more than latency alone.
When This Test Is Not Enough
ICMP probing only measures reachability and path latency; it does not test application throughput or the performance of a specific service. Some providers rate-limit or block ICMP, so a failed probe does not always mean the host is down. To measure the latency of your own connection to Hetzner, ping the same endpoint from your local machine. If you suspect intermittent problems, run a packet loss or jitter test instead, because those reveal variation that a single latency reading hides.