CONNECTIVITY
Ping Test
Run a server-side ICMP ping test against a public hostname or IP address. The result shows reachability, packet loss and round-trip timing.
39DExternal testRuns from the toolbox server
RUN TEST
Ping Test
HOW IT WORKS
About the Ping Test
The server resolves the hostname, confirms that every resolved address is public, and sends four ICMP echo requests. Results reflect the route and firewall policy seen from the toolbox server, not from your own computer.
How to use this result
- Run the test from this server.Use a public hostname, address, prefix or ASN in the format requested above.
- Compare with another observation point.Run a local command or use a second provider to identify location-specific behaviour.
- Correlate related evidence.Use the related tools below to compare DNS, routes, ports, TLS and application responses.
- Keep the time and context.Routing, DNS caches and reputation data change, so record when the result was collected.
Common interpretation issues
- A failed ping does not always mean the service is offline; many firewalls block ICMP.
- High latency may be caused by distance, congestion, traffic shaping or an indirect route.
- Intermittent packet loss is more useful when compared with traceroute or MTR results.
NEED HELP INTERPRETING THE RESULT?
39D supports business networks, cyber security and managed IT.
For ongoing support or a larger infrastructure project, speak to the 39D team.
Frequently asked questions
Why does a website work when ping fails?
Web traffic and ICMP are different protocols. A firewall can allow HTTPS while dropping ping requests.
Is this my local latency?
No. The measurement starts from the 39D toolbox server, which is useful for an external view.