Test serverNearest Cloudflare data centre
Your providerShown when the test starts
Ready—ms
  1. Connect
  2. Latency
  3. Download
  4. Upload
  5. Packet loss
Latency (idle)
—ms
Jitter
—ms
Latency (download)
—ms
Latency (upload)
—ms
Packet loss
—
Download
—Mbps
Upload
—Mbps
Your test history

What this test measures

  • Idle latency (ping): 30 small requests to the nearest Cloudflare data centre, timed with your browser's network timestamps. The median is shown.
  • Jitter: the average change between consecutive latency samples.
  • Latency during download and upload: latency samples taken while the line is filled with data for 8 seconds in each direction.
  • Bufferbloat grade: how much latency rises under load compared with idle.

Because the connection is filled during the test, this test also reports download and upload speed, using less data than the full speed test.

How to read your result

MeasureGreatOKProblematic
Idle latencyunder 30 ms30–80 msover 100 ms
Jitterunder 5 ms5–20 msover 30 ms
Extra latency under loadunder 30 ms30–100 msover 100 ms

These ranges are rules of thumb for latency to a nearby server, not industry standards. See the methodology.

Why latency under load matters

Many connections show a great ping when idle, then lag badly the moment someone starts a download or a cloud backup. This effect, called bufferbloat, is caused by oversized queues in routers and modems. It can often be fixed by turning on Smart Queue Management (SQM) in your router.

Your ping to a game server can differ from this result, because game servers may be further away than the Cloudflare data centre used here. Read internet speed for gaming andwhat is jitter to learn more.