Endpoint Latency Test
Measure real round-trip latency to any host or URL — three live requests, timed server-side.
What this test measures
Enter a host or URL and our server sends three HEAD requests to it, timing each one from start to response. You get each sample, the average, and the fastest and slowest. A HEAD request asks for headers only, so the numbers reflect connection setup and server response time, not download speed.
Reading the result
The times are measured from our server, not from your computer, so they show how quickly the target answers a well-connected client. Big gaps between the three samples usually mean the target is slow to respond under load or sits behind a rate limiter. A request that fails entirely is shown as unreachable.
To judge a proxy, compare the same target with and without it from your own machine: the difference is what the proxy adds. Our guide to testing proxy speed walks through measuring latency and success rate properly.
Questions
Is this a bandwidth test?
No. It times requests that return headers only, so it measures latency, not throughput.
Why are my numbers different at home?
These requests start from our server. Your own times add the distance between you and the target, and your connection's own latency.
Related guides
- How to Test Proxy Speed: Latency, TTFB and Success
A reproducible way to benchmark any proxy: curl timing, a Python script and the metrics that matter. Test providers fairly before you spend.