How to Test Ping, Jitter and Packet Loss
The three numbers that matter are ping (average round-trip time), jitter (variation between round-trips), and packet loss (percentage of packets dropped). Measure all three over a five-to-fifteen minute window against the game server, not google.com. Free tools — WinMTR, mtr, Waveform bufferbloat — are the standard.
Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.
What you're actually measuring — and why
Ping is the average round-trip time in milliseconds. It measures how long the network takes to acknowledge a small packet. Ping alone is not enough.
Jitter is the variation between one ping and the next. Two 40 ms averages can feel completely different depending on jitter. Competitive play tolerates almost none.
Packet loss is the percentage of packets that never arrive. Any sustained loss is a problem. Loss is the metric that causes rubber banding and missed hits, not ping.
The measurement stack — free and reliable
- WinMTR (Windows) — continuous per-hop trace with rolling loss and jitter. Run for 5–15 minutes.
- mtr (macOS/Linux) — same as WinMTR from the terminal: mtr -rwc 300 <target>.
- PathPing (Windows built-in) — a shorter one-shot diagnostic; usable if WinMTR is unavailable.
- Waveform Bufferbloat Test — the fastest way to check whether your line goes to pieces under load.
- Fast.com or Cloudflare Speed Test — for baseline throughput; not gaming-relevant on their own.
A repeatable test procedure
- Wire in. Ethernet is the only baseline that removes wireless variability.
- Pause every upload — cloud sync, streaming, patch downloads.
- Identify the game server or datacentre IP for your region.
- Run WinMTR / mtr for at least five minutes. Note per-hop loss and jitter.
- Repeat at a different time of day. Peak-hour numbers are what matter.
- Take a second measurement over Wi-Fi to attribute how much variance is wireless.
- Save the output. This is the evidence to attach if you contact your ISP.
Common measurement questions
- What is the best free tool to test gaming ping and jitter?
- For Windows, WinMTR is the standard — it runs a continuous mtr trace to any host and reports per-hop loss and jitter over time. For macOS and Linux, use mtr from the terminal. Waveform's bufferbloat test is the fastest way to check bufferbloat specifically.
- How long should I run a ping test?
- Minimum five minutes for a reliable sample; ten to fifteen minutes if you're diagnosing an intermittent problem. Anything shorter is dominated by warm-up and can miss the pattern you care about.
- What is a good ping and jitter for gaming?
- Ping under 40 ms feels excellent in competitive shooters; up to 80 ms is playable in most modern games. Jitter under 5 ms is competitive-grade; over 15 ms is visibly disruptive. Packet loss should be effectively zero — anything sustained above 0.5% will be felt.
- Should I test against the game server or a public target?
- Against the game server IP if you can find it — it is the path that actually matters. If you can't, test against the game's login endpoint or the datacentre region a public looking glass tells you the game uses. Testing google.com tells you nothing useful about gaming.