Ping Test: in-browser HTTPS latency to any URL
Free in-browser ping test. Measures HTTPS round-trip time to any URL with min, average, max and jitter. Use the quick presets (Google, Cloudflare, GitHub, AWS, OpenAI) or paste your own URL. Browsers don't expose raw ICMP, so this measures HTTP request latency — the closest browser-side equivalent.
| # | TIME | STATUS |
|---|
When to run an online ping test
Gaming latency
Measure the round-trip to game servers to pick the best region in your game's matchmaker. Under 50 ms is competitive; over 150 ms is rough.
Multi-region check
Run the global mode to ping a host from 40+ locations worldwide and find out where your service is fast and where it's slow.
Outage triage
If a site loads slowly only for you, run the global ping — if every region times out the site is down; if only your region is slow it's your ISP route.
Traceroute hops
See the network path packets take to a host across multiple regions — useful for diagnosing routing problems and peering disputes.
Port reachability
Confirm port 22 (SSH), 443 (HTTPS), 3306 (MySQL) or any TCP port is open from outside your firewall.
TTFB & TLS breakdown
The local mode shows DNS / TCP / TLS / TTFB timings from the Performance API — pinpoint exactly which phase is slow.
How to use the ping test tool
Pick a mode
From your browser = HTTPS ping from your device. Multi-region = global ping via check-host.net. Traceroute = network path. Port check = TCP port open?
Enter a URL or host
Local mode wants a full URL (https://cloudflare.com); global / trace / port modes take just the host (cloudflare.com) and an optional port.
Click Run ping
Local mode probes once every 200 ms. Multi-region mode submits to check-host.net and polls for completion across all 10–40 nodes.
Read the metrics
Min / Avg / Max / Jitter update live. The first sample is often higher due to TLS handshake; ignore it or run more probes for a stable average.
About ping, latency, jitter and traceroute
A ping measures the round-trip time between two points on the internet. Lower is better. The traditional ping command uses ICMP, which browsers can't send, so this online ping test uses HTTPS instead — a small HEAD request whose round-trip time is the best browser-side equivalent. For multi-region ICMP / TCP pings and traceroutes we route through the public check-host.net API which runs the real ping, tcping and traceroute commands from 40+ countries.
HTTPS ping vs ICMP ping
HTTPS round-trip times are usually 5–30 ms higher than ICMP because they include the TLS handshake on the first probe and TCP overhead on every probe. Subsequent probes reuse the connection and drop close to ICMP latency. The relative comparison is still meaningful: a 200 ms HTTPS ping vs a 80 ms one tells you the same story about which host is closer.
Latency, jitter, packet loss
Latency is the round-trip time itself. Jitter is the standard deviation — how spiky those times are. A steady 80 ms is far better for VoIP and games than a 50 ms average with 80 ms swings. Packet loss shows in the global mode as the loss ratio per node — anything over 1% on a wired link is broken.
Connection breakdown via the Performance API
When you ping a URL on your own origin or a CORS-enabled host, the browser exposes per-phase timings via performance.getEntriesByName(): DNS lookup, TCP connect, TLS handshake, request, TTFB (time-to-first-byte) and download. The connection-breakdown card under the metrics shows these for the last probe — perfect for spotting whether your slow ping is actually slow DNS or slow TLS.
Multi-region ping
Global mode sends one job to check-host.net, which fans out to 10–40 monitoring nodes (selectable: 5 fastest, 10, 20, or all 40+). You see per-region average RTT, loss, and the resolved IP — instantly revealing CDN routing issues, geo-restricted services and route blackholes.
Traceroute & port check
Traceroute reveals every router (hop) packets traverse from each test node to your target. Port check opens a TCP connection to host:port from each node — use it to verify 22, 443, 3306, 27017 or any custom port is reachable from outside.
Why browsers can't send ICMP
ICMP requires raw sockets, which web pages have never had access to for security reasons — otherwise any site could portscan your network. This is why every "online ping tool" you'll find either uses HTTPS (our local mode) or proxies through a server (our global / trace / port modes via check-host.net).
Ping Test — frequently asked questions
No — browsers don't expose raw ICMP. This tool measures HTTPS round-trip time, which is the closest equivalent. Each probe times a small HEAD request and ignores HTTP redirects.
HTTPS adds TLS handshake overhead on the first probe. Subsequent probes reuse the connection, so they're faster — that's why the first sample is often an outlier.
Yes. Enter any HTTPS URL. The tool issues a HEAD request and measures response time. A few servers block HEAD — in that case the probe still measures the time to the rejection.