Measure browser ping to a nearby edge or selected AWS regions. Shows median, p95, jitter, timeouts and the fibre-distance floor.
Runs in your browser
HTTPS round trips to Cloudflare and AWS endpoints. Nearby runs 20 or 50 samples; World fans out to selected regions.
What this measures
This is an HTTPS round trip, not an ICMP ping. TLS setup, browser timing and server handling add a few milliseconds, so treat it as the latency your web apps feel.
Target
Nearest Cloudflare edge
Nearby uses responseStart timing when the browser exposes it.
A/B comparison
Save two nearby runs to compare Wi-Fi, cable or VPN routes.
Browser ping versus command-line ping
This page measures an HTTPS request and response, not an ICMP echo. That makes it honest about what your browser can see: the latency your web apps actually experience.
What counts as a good ping
Below 20 ms feels excellent for fast games. Up to 50 ms is still comfortable for most online play and video calls. Past 100 ms, interaction starts to feel delayed even when throughput looks fine.
Why world latency differs so much
Distance sets a hard floor. The fibre floor on this page makes that lower bound visible, and everything above it is routing overhead or queueing.
How to use
Start with Nearby to see your median latency and jitter to the closest Cloudflare edge.
Switch to World to compare selected AWS regions and sort them by median latency.
Use Save as A and Save as B to compare two nearby runs, such as Wi-Fi versus cable.
Read the fibre floor before concluding that a route is “bad”. Distance still matters.
FAQ
Is this the same as `ping` in the terminal?
No. Terminal ping uses ICMP. This page uses HTTPS because browsers cannot send raw ICMP packets.
Why does World use AWS regions?
They provide stable public endpoints spread across continents, which makes relative route comparison possible.
Why are distance columns sometimes hidden?
Because the page could not confirm which edge location you actually used. A guessed floor would look precise while being wrong.