Ping / Latency
Test HTTP response latency against a host. Browsers and edge functions cannot send raw ICMP packets, so this performs a real HTTP latency test and labels it clearly as such.
Input
Results
Overview
The Ping / Latency tool measures how quickly a web server responds to HTTP requests. It makes four requests, then reports the minimum, average, and maximum response time and how many requests failed.
This is an HTTP latency test, not ICMP ping. Browsers and the server environment this site runs on cannot send ICMP echo packets, so no result here can tell you whether a host answers ping.
How It Works
This site's server sends four HTTP requests to the target (a HEAD request, falling back to GET if the server answers 405 Method Not Allowed) with a 5-second timeout each, and records how long each takes to receive a response. From those samples it calculates minimum, average, and maximum. The "packet loss" figure is the percentage of those four requests that failed; it is not network packet loss.
Because it is an application-level measurement, each time includes more than the network round trip: DNS resolution, TCP and TLS connection setup (when a new connection is needed), and the web server's own processing time. The first sample is often the slowest for that reason. The measurement is taken from this site's server, not from your device.
How to Use the Ping / Latency
- Enter a hostname or URL, for example
example.com. - Press Calculate and wait a few seconds for the four requests.
- Compare minimum, average, and maximum. A large spread suggests variable performance.
- Use the HTTP Status Checker to see whether slow responses involve redirects.
Worked Example
Is a website slow or just variable?
You are comparing two regions' response times for a site. The values below are an illustrative sample.
Input
Target: example.com
Illustrative output
HTTP latency test
Minimum: 58 ms
Average: 81 ms
Maximum: 142 ms
Packet Loss: 0%
This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.
A minimum of 58 ms against a maximum of 142 ms means at least one request was far slower than the fastest. That pattern is typical of connection setup: the first request has to pay for DNS, TCP and TLS, while later requests can reuse work already done. The average of 81 ms is pulled up by that one slow sample, so the minimum is the better guide to the server's steady response time.
Zero failures means all four requests completed. If one request in four had timed out, "packet loss" would read 25%, meaning one of four HTTP requests failed, not that 25% of network packets were lost.
Interpreting Results
- Minimum
- The fastest of four responses; the best indicator of the unloaded response time from this vantage point.
- Average
- The mean of successful samples. It is sensitive to a single slow outlier with only four samples.
- Maximum
- The slowest sample, often the first one (connection setup) or a transient delay.
- Packet Loss
- Percentage of the four requests that failed (timeout or connection error). It is a failure rate for this test, not an ICMP measurement.
Troubleshooting
- The test failed completely.
- The server did not respond in time over HTTP/HTTPS. It may be down, blocking this tool's requests, or not running a web server on a standard port. A host can answer ICMP ping while its web service is down, or the reverse.
- Latency is high.
- Remember it includes DNS, TLS setup, and server processing, measured from this tool's location. Compare with the DNS Lookup and run a trace or ping from your own network for the path you care about.
- "This target cannot be tested."
- Internal, private, and loopback addresses are refused.
Limitations and Accuracy
- It is not ICMP ping and does not measure the network path, hop count, or MTU.
- Only four samples are taken, so the statistics are rough.
- Measurements come from this site's server location; latency from your location may differ greatly.
- Servers may rate-limit or treat repeated requests differently.
Data Handling
Uses server-side requests. The hostname or URL you enter is sent to this site's server function, which makes four requests to it.
Sent to: The web server you named. That server sees requests from this site's infrastructure.
Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.
Frequently Asked Questions
Why doesn't this use real ping?
Real ping uses ICMP, which cannot be sent from a web page or from the serverless environment this site runs on. An honest HTTP test is more useful than a fake ping.
Can I use this to test a game server or non-web service?
No. It only works for hosts that answer HTTP or HTTPS.
How do I do a real ping?
From your own machine: ping example.com (Windows, Linux and macOS), or traceroute/tracert to see the path. The connectivity guide shows how to interpret the output.