Skip to content

What's My Ping?

Measure your own connection: latency, jitter and failed samples, from your browser to the nearest Cloudflare edge. Nothing to install.

Looking for the latency to a particular server instead? Use the Ping Test, which measures from our server to a host you choose.

How this test works

Your browser opens a WebSocket to the nearest Cloudflare location and sends 30 small timestamped messages, roughly one every 100 milliseconds. Each message is echoed straight back, and your browser times the round trip. The first three samples are discarded before anything is calculated, because the first few round trips on a new connection are always slower — TLS setup, the TCP congestion window, the browser scheduling the first frame — and counting them would inflate every average shown here.

What it does and does not tell you

This measures the application round trip between your device and the edge of Cloudflare’s network: your Wi-Fi or Ethernet link, your router, your ISP’s access network, and the first hop or two of the public internet. That is the part of the path you can actually do something about, and it is where most latency problems live.

It is not your ping to a game server, which sits somewhere else entirely and will be higher. It is not a measurement of your ISP’s backbone, and it is not ICMP — it is a browser network request, which carries a little more overhead than a raw ping and is affected by what else your browser is doing. Any tool that promises you a single number for “your internet ping” is simplifying something that genuinely depends on where you are pinging.

Reading the numbers

Ping is the average round trip. Under 20 ms is excellent, 20–50 ms is good, 50–100 ms is fair, and above 100 ms starts to be noticeable in anything interactive.

Jitter is the average difference between one round trip and the next. Under 5 ms is excellent and above 30 ms is poor. Jitter is the metric most people have never heard of and the one that actually explains a bad video call: consistently slow is workable, unpredictably variable is not.

Failed samples is the share of messages that never came back within a second. Anything above about 2.5% is a real problem and usually shows up as stalling video and dropped call audio.

If the result is worse than you expected

  • Low ping but high jitter is the classic Wi-Fi signature. Packets arrive quickly when they arrive, but not at a steady rate. Try the same test on a wired connection before blaming the ISP.
  • Everything high often means the connection is simply busy. A large upload, a game patch downloading, or a household streaming in 4K will all show up here.
  • A VPN or corporate proxy changes the answer completely, because your traffic reaches Cloudflare from wherever the VPN exits, not from where you are sitting.
  • Failed samples with a fine average points at an unstable link — a marginal Wi-Fi signal, a failing cable, or congestion in your ISP’s access network at peak time.

Run it a few times, at different times of day. A single test is a snapshot; the pattern is the diagnosis. If you need the latency to one specific host rather than to the edge, the Ping Test measures that from our server to a target you choose.