New — Now with actual evidence

It wasn't you.It was the lag.

Your IP. Your ping. Your speed. Measured live, presented beautifully — so the next time you go down, you have proof.

The pre-game network check.

Idle ping, jitter, packet loss, download and upload — the full check in a single run, before you queue.

Measured: round trips from your browser to Cloudflare edge nodes and game regional entry points — not the server of the match you are about to play.

Shared resultSomeone sent you their lag evidence. Run your own test for a fresh ruling.
🔒 IP & Location hidden by default (Click to expand)
—
Ping
—
Jitter
—
Packet loss
—
Download
—
Upload
Ready0%
Awaiting evidence.
Generate my innocence certificate Get an excuse instead
Not sure what to do with this result? Advanced troubleshooting — the Lag Clinic
Advanced test — latency under load (Bufferbloat)

Idle ping can look fine while games still stutter — background downloads and uploads push latency up. This test saturates your connection in both directions and measures how much the latency grows.

About 35–50 seconds and roughly 30 MB of data (varies with your speed; hard cap ≈ 99 MB). The test talks to Cloudflare, and when it finishes the module may send the results to Cloudflare for aggregate statistics — this site receives nothing.

How the verdict works

The lag is guiltyPing ≥ 90 ms, or Jitter ≥ 25 ms, or Packet loss ≥ 3%, or Download < 5 Mbps, or Upload < 3 Mbps.
The lag is plausiblePing ≥ 45 ms, or Jitter ≥ 12 ms, or Packet loss ≥ 1%, or Download < 15 Mbps, or Upload < 5 Mbps.
Connection flawlessNone of the warning thresholds above are hit.
Bufferbloat guiltyIf the loaded-latency test pushes latency more than +60 ms over idle, the verdict is sabotage from within — no matter how clean idle looks.

What this measures: round trips from your browser to a Cloudflare edge node (plus download/upload throughput) — not your game server’s actual ping. It shows the state of your connection to the public internet; it cannot prove what caused the lag in one specific match.

You are (approximately) here—
Placed by IP — roughly where your provider sits, not GPS. Tiles come from Esri (fallback OpenStreetMap); opening the map sends tile requests to them.

Ping everything.

Game servers and the usual suspects — one panel, two tabs.

Game servers.

Pick a game and a region — measure the trip from your browser to that region before you queue.

—
Pick a region to measure.
Game servers don't answer web pings, so this times your browser's HTTP round trip to the region's game-cloud hub (AWS DynamoDB) in the same city — warmed up first, then 6 samples, median shown. Different games in the same city share the same hub, so identical numbers across games are expected — not a bug. It is not the ping you see inside the game: match traffic also crosses the publisher's own network and servers. It usually reads about 15–25 ms above the in-game UDP number — trust the ranking between regions, not the absolute value.

Numbers are only half the story. To feel what they do to your aim, try the Lag Simulator.

Slow hands, or bad ping?

Five rounds of pure reaction plus a regional entry-point ping reading — one verdict that splits the blame between your hands and your network.

Take the reaction test
Just for fun — this one is about your hands, not a network test.

Innocence, worded.

If the numbers ever betray you, rhetoric has your back. One tap, ready to paste into team chat.

"I didn't miss. The server did."
Get it in writing — Certificate of Innocence
—
tests run
site-wide
—
of tests ruled
"it was the lag"
—
certificates of
innocence issued
How we count: first-party counters, no cookies. Each completed full test adds 1; the percentage is the share ruled “it was the lag”. Development and test traffic is included.

Privacy, in plain terms

What actually happens to your data on this site — checked against the code, not marketing copy.

🚫 No Cookies 🔒 IP Hidden by Default 💻 Local History Only
View the full privacy details

Speed and ping tests run in your browser against Cloudflare’s edge and the public entry points of each site or game region. Your results live in your browser’s local history only; this site does not store your scores.

When a test finishes, your browser sends this site a counting signal with only an event name and a verdict level (no numbers, no IP, no location). Those counters power the totals above.

Your IP and rough location come from Cloudflare as it serves the page. They are hidden by default. Only if you turn on the switch does the site send your IP to proxycheck.io (fallback: ip-api.com) for a proxy/VPN risk lookup — off means it is never sent.

The map’s tiles come from Esri (fallback: OpenStreetMap). If you open the map, your browser requests tiles from them directly, so they see your IP and the area you view.

Certificate sharing does store data: the certificate image plus the name, game and ping you typed are kept for 180 days, and anyone with the link can view them. Jury votes also store the voter’s IP, only to cap each certificate at 3 votes per IP.

This site is hosted on Cloudflare, so every request passes through Cloudflare’s infrastructure under its policies. We only promise what is listed above — nothing more.