Ping Test
Measure your network latency in real time. See every ping result as it happens — minimum, maximum, average, jitter, and packet loss — with a live pulse chart. Works with or without a VPN. For consistency over raw speed, pair this with the jitter test.
Live latency test
Measures round-trip time to selected server · 100% client-side
Live ping chart
< 50ms
50–150ms
> 150ms
Timeout
--
ms current
Click Start Test to begin
--
Minimum
--
Maximum
--
Average
--
Jitter
--
Packet loss
Ping history
Results will appear here as pings complete
Ping quality guide — what your result means
< 50ms
Excellent
Best for all real-time uses
Gaming, video calls, trading. Responses feel instant. Any VPN adding under 50ms overhead is considered fast.
50–100ms
Good
Comfortable for most uses
Streaming, browsing, casual gaming. Video calls remain smooth. Competitive gaming may show slight input lag.
100–200ms
Fair
Acceptable for browsing
Web browsing works fine. Video calls may stutter. Online gaming will feel noticeably laggy. Investigate your VPN or ISP.
> 200ms
Poor
Problematic for real-time
Pages load slowly. Video calls drop. Gaming is unplayable. Check your VPN server location, router, or ISP congestion.
What affects your ping
Physical distance to server
Every 100km of cable distance adds roughly 0.5–1ms of latency. Connecting to a server on another continent always means higher ping — this is physics, not a bug.
Router and local network
An overloaded home router or a Wi-Fi signal competing with neighbours can add 5–30ms before your packets even leave your house.
VPN encryption overhead
WireGuard adds 1–5ms. OpenVPN adds 5–20ms. Choosing a VPN server close to your location keeps this overhead minimal and acceptable for most uses.
Server load
Overloaded servers — whether ISP, VPN, or game servers — add unpredictable latency. Evening peak hours often show 20–50% higher ping than off-peak tests.
Connection type
Fibre: 1–5ms base. Cable: 5–15ms. DSL: 10–30ms. 4G: 20–60ms. 5G: 5–20ms. Starlink satellite: 20–40ms — now fast enough for gaming and video calls.
ISP routing quality
Some ISPs use suboptimal routing paths that add unnecessary hops. A traceroute can reveal if your data is taking a 14-hop detour through another country.
What a browser-based ping test can and can't tell you
Every browser-based ping tool — this one included — works around the same sandbox limitation. Understanding what that limitation means makes your results far more useful to interpret.
This measures HTTP latency, not raw ICMP ping
Browsers have no access to raw ICMP (the protocol your OS's
ping command uses) for security reasons — JavaScript can only make HTTP requests. This tool times how long an HTTPS request takes round-trip using performance.now(), which is how every browser-based ping tool works, including major speed-test sites. It's a very close approximation, but expect it to read a few milliseconds higher than a terminal ping to the same server, since it includes TLS overhead that raw ICMP doesn't.The first ping in a run is almost always the slowest
Your first request has to resolve DNS, open a TCP connection, and complete a TLS handshake before any data moves — that's three round trips stacked before the "real" ping even happens. Subsequent requests reuse that same connection via HTTP keep-alive, so pings 2 onward measure much closer to pure network round-trip time. A single slow first bar isn't a sign of a bad connection.
Different targets aren't the same physical distance — even from the same location
Cloudflare, Google, Quad9, and DNS.SB each run their own global anycast network, and your ISP's routing table decides which physical edge node answers your request for each provider independently. It's entirely normal for one provider to route you to a node 50km away while another routes you to one 500km away, even though both claim global coverage. Comparing ping across targets tells you about routing quality, not just raw distance.
Why Cloudflare's target isn't perfectly comparable to the other three
The Cloudflare target hits a lightweight static trace endpoint, while the Google, Quad9, and DNS.SB targets hit live DNS-over-HTTPS query endpoints that perform actual resolution work server-side before responding. That extra processing time means Cloudflare will structurally tend to read a little lower than the others — the difference reflects endpoint design as much as network latency. Worth knowing if you're comparing targets directly rather than tracking one target over time.
"Packet loss" in a browser test isn't only dropped packets
A real ICMP ping reports loss when a reply never arrives. In a browser, a failed request can mean the packet was actually dropped — or that a CORS policy, an ad blocker, a browser privacy extension, or a corporate firewall rejected the request outright before it ever left your device. The Blocked label above the chart exists specifically to separate genuine network drops from local software interference; treat a high loss percentage as a prompt to check your extensions before assuming your connection is unstable.
Frequently asked questions
“Why is this called a "ping test" if it doesn't use real ICMP ping?”
Browsers can't send raw ICMP packets — it's blocked at the browser sandbox level for security reasons. This tool measures HTTP round-trip time instead, which is the standard approach every browser-based latency tool uses. It closely tracks true ICMP ping but typically reads a few milliseconds higher due to TLS handshake overhead.
“Why does the first ping in my test always look slower than the rest?”
The first request has to complete DNS resolution, a TCP handshake, and a TLS handshake before it can measure anything — three extra round trips bundled into that one result. Every ping after it reuses the same connection, so they measure much closer to pure network latency. This is expected and not a sign of a problem.
“Why do I get different ping results for Cloudflare vs Google vs Quad9?”
Each provider runs an independent global network, and your ISP's routing decides which physical server answers you for each one — the "closest" node can differ significantly between providers even from the same location. Cloudflare's target also uses a lighter endpoint than the DNS-over-HTTPS endpoints used for Google, Quad9, and DNS.SB, so it will often read a touch faster regardless of your network. Our DNS Lookup tool can show you which nameservers a domain actually resolves to if you want to dig into routing further.
“What does "Blocked" mean in my results, and how is it different from a timeout?”
A timeout means the request was sent and PrivacyTestLab genuinely never got a reply in time. "Blocked" means the request was rejected almost instantly — usually by an ad blocker, privacy extension, or firewall on your device — before it even reached the network. If you see mostly Blocked results, check your browser extensions rather than assuming your connection is bad.
“Does a VPN always increase my ping?”
Almost always, yes, but the amount varies a lot by protocol. WireGuard typically adds only 1–5ms of overhead; OpenVPN can add 5–20ms. Choosing a VPN server geographically close to you keeps the added latency small enough to be unnoticeable for most everyday use.
“Why does my ping vary throughout the day?”
Server load and network congestion both follow usage patterns — evening peak hours can show 20–50% higher latency than early morning, since more people are online competing for the same routing paths and server capacity. Run the test at different times if you want to understand your typical range rather than a single snapshot.
“Is HTTP latency the same thing as gaming ping?”
They're closely related but not identical. Most online games use UDP rather than HTTP/TCP, so their actual in-game ping can differ from what this tool reports — usually similarly, sometimes lower, since UDP skips TCP's connection-establishment overhead. This tool is a strong proxy for your general connection quality, but your game's own in-client ping display is more accurate for that specific game.
“How many pings should I run for an accurate result?”
20 pings gives a reasonable balance of speed and stability for a quick check. If you're trying to diagnose an intermittent issue or want a reliable jitter figure, run 50 or 100 — more samples smooth out one-off spikes from background traffic on your network. Pair this with the dedicated jitter test if consistency matters more to you than raw speed.