Measure latency, packet loss, and jitter across custom probes.
Monitor changing latency during maintenance windows.
This page measures basic reachability and latency to a host. The UI stays unchanged, but the new content clarifies an essential trust note: ping results depend on the probe source, routing path, firewalls, NAT, and ICMP handling along the way.
Enter a hostname or IP address, then choose packet count, interval, and payload size. Those settings shape how the test is performed, but the result is still a point in time observation from the server running the page.
The tool sends a series of probes, records response times, and summarizes minimum, average, maximum, and loss. It is a connectivity test, not an application health guarantee.
Run a test against a stable host and compare min, average, max, and loss. If replies disappear, do not assume the host is down immediately. ICMP filtering, rate limits, and path changes can all affect visibility.
Use ping for first-pass troubleshooting, latency comparisons, and verifying whether a host is broadly reachable from the observation point running the tool.
Ping, traceroute, and open port tests can all be affected by firewalls, routing policy, NAT, and rate limits. Treat the output as an informational estimate of current path behavior.
It measures whether the target responds and summarizes latency, packet loss, and related timing values for the probe set.
No. Firewalls, ICMP filtering, rate limits, routing policy, and NAT behavior can all prevent a reply even when the host or service is reachable.
Latency can change because of path selection, congestion, server load, filtering, or differences in the observation point running the test.
No. A successful ping shows basic reachability to the probe method, not whether a website, API, or TCP service is healthy.
It is useful for basic troubleshooting, confirming a path exists, comparing latency before and after changes, and spotting obvious packet loss.
The output is informational and depends on the network path, firewalls, NAT, and rate limits between the probing system and the target.
Map the path when ping shows loss or unstable latency.
Test a specific service after confirming general reachability.
Add geographic and ISP context to troubleshooting.