Internet health check

One minute, four measurements, and a plain answer about whether your connection is healthy.

Packet loss โ€“%
Ping โ€“ms
Jitter โ€“ms

Each tick is a packet. Taller ticks took longer. Red marks are packets that never came back.

Test length

Sends 3000 small UDP packets to your nearest Cloudflare edge and back.

Updated

What a healthy connection looks like

A speed test tells you how big your pipe is. An internet health check tells you whether the pipe leaks, and how evenly things flow through it. This one measures four things in a single 60-second run over UDP: packet loss (packets that never arrive), ping (how long a round trip takes), jitter (how much that ping varies) and stability (how many seconds in the run spiked or dropped). Those four decide whether calls sound clear and games feel responsive, and none of them is visible in a download speed.

A healthy home connection, tested on a cable or good wifi, shows zero or near-zero loss, a ping that sits within a few milliseconds of its minimum, single-digit jitter, and no more than one spiky second a minute. The verdict list under the result compares your run to the needs of gaming, voice calls, video meetings, streaming and browsing, because a connection can be healthy enough for one and not the other.

Health check results, explained

MeasureHealthyWorth checkingUnhealthy
Packet loss0 to 0.5%0.5 to 2%Over 2%
PingWithin your line type's normal range2 times the minimumOver 150 ms
JitterUnder 5 ms5 to 30 msOver 30 ms
Spiky seconds (per minute)0 to 12 to 45 or more

A wifi health check

Most connection problems at home are wifi problems, and the same test doubles as a wifi health check. Run it once next to the router on wifi, then in the room where you usually have trouble. If loss and jitter climb as you move away, the signal is not reaching that room well enough, and a better router position, a mesh node or a cable will fix it. If the result is bad even next to the router, the channel is crowded or the router itself is struggling.

For a definite answer, run it once on wifi and once on an Ethernet cable plugged into the same router. If the cable run is clean and the wifi run is not, the wifi is the whole story. The wifi versus ethernet guide explains what to change for each result.

When the check fails

  • Loss on a cable too. Restart the modem and router, check the cables, then contact your provider with the copied result.
  • Healthy on a cable, unhealthy on wifi. Move the router into the open, change the wifi channel, or add a mesh node. See how to fix packet loss.
  • Healthy in the morning, unhealthy at night. Evening congestion at your provider. Your options are a complaint with evidence, a different plan, or a different provider.
  • No packets at all. UDP is blocked on your network. See what to do when UDP is blocked.

Frequently asked questions

How do I check my internet health?

Run a test that measures packet loss, ping and jitter over at least 60 seconds, ideally once on wifi and once on a cable. Near-zero loss, steady ping and low jitter mean a healthy connection.

Is a speed test enough to check my connection?

No. Speed tests measure capacity for a few seconds and hide loss and spikes. A connection can pass a speed test easily and still drop calls because of loss or jitter.

How often should I run an internet health check?

Whenever something feels wrong, and after any change: a new router, a new provider, moving the router. Running it at the same time of day each time makes the results comparable.