Ping Test: Continuous Latency, Jitter and Packet Loss Test
Free continuous ping test: check latency, jitter and packet loss to Cloudflare 1.1.1.1, Google 8.8.8.8, mes.fm or any website, with a live chart, ping-style log and plain-word verdicts for gaming, calls and streaming. Nothing to install.
How this works: a web page can't send real ping (ICMP) packets, so this test sends tiny web requests instead and times the round trip. The numbers are usually a few milliseconds higher than the ping command shows, but slow, uneven or lost replies show up the same way. Nothing is uploaded.
Is my connection good enough?
Start the test to see.
| Target | Last | Min | Avg | Max | Jitter | Lost | Warm-up |
|---|
Times in milliseconds (ms). Warm-up = the first request to each place, which also has to look up the name and open a secure connection.
Round-trip time
Red marks along the top = lost requests. Hover or touch the chart to read the times.
Log
A continuous ping test in your browser
This page does what ping 8.8.8.8 -t does in a terminal: it keeps checking how long it takes to get an answer from a server, and shows every reply, the lowest, average and highest time, the jitter (how uneven the times are) and how many requests got lost. You can ping several places at once (Cloudflare, Google, Google DNS 8.8.8.8, mes.fm or any website you add) and watch them on one chart.
Why the times are a little higher than real ping
Real ping uses ICMP packets, which web pages are not allowed to send. This test times small HTTPS requests instead. Each reply has to go through the browser and the web server, which usually adds a few milliseconds. The very first request to a place also looks up its name (DNS) and opens a secure connection (TCP and TLS); that is shown on its own as the warm-up and left out of the averages. After that the browser reuses the connection, so the times are close to the true network round trip.
What the numbers mean
- Round-trip time (latency)
- How long a request takes to get there and back, in milliseconds. Under 30 ms is excellent, under 60 ms is good for most things.
- Jitter
- The average change from one reply to the next. High jitter makes calls choppy and games feel laggy even when the average looks fine.
- Lost (packet loss)
- Requests that got no answer before the time limit. Even 1-2% loss can cause freezes in calls and games.
Questions
Why is one target much slower than the others?
Distance. Cloudflare and Google have servers in most big cities, so they usually answer fastest. A website hosted far away can't answer faster than light travels there and back.
My ping is fine but calls still freeze. Why?
Look at jitter and loss, not only the average. Wi-Fi far from the router, a busy network (someone downloading or streaming) or a weak mobile signal usually show up as spikes on the chart. Try a cable, move closer to the router, or test again when nobody else is using the connection.
Does this test my download speed?
No. Speed (megabits per second) and latency are different things. This page only measures latency, jitter and loss.
Why does a website I added say unreachable?
Some sites block requests from other pages or don't answer on https. Try its main address (example.com) or another site.