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.

Generate an excuse

Proof, at full speed.

Ping, jitter, download and upload — measured against the Cloudflare edge, the moment you ask.

Your IP addressDetecting…

Location—

Cloudflare node—

Session00:00

IP scoreScoring…

IP type—

Proxy / VPN—

Provider—

—

Ping

—

Jitter

—

Packet loss

—

Download

—

Upload

Ready0%

Awaiting evidence.

Generate my innocence certificate

How the verdict works

The lag is guiltyPing ≥ 100 ms, or Jitter ≥ 30 ms, or Download < 10 Mbps, or Upload < 5 Mbps.

The lag is plausiblePing ≥ 50 ms, or Jitter ≥ 15 ms, or Download < 50 Mbps, or Upload < 10 Mbps.

Connection flawlessNone of the warning thresholds above are hit.

You are (approximately) hereLocating…

Placed by IP address — roughly where your internet provider sits, not GPS. Only you can see this, and nothing about it is stored.

The usual suspects.

Live latency from your browser to the sites everyone actually uses. Green across the board? Then it really was a skill issue. All red? Case closed — it was the lag.

Not yet measured.

Each site is warmed up once (DNS + TLS), that first sample is discarded, then measured 4 more times. The number shown is the median.

Game servers.

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

Game

—

Pick a region to measure.

Game servers don't answer web pings, so this times your browser's round trip to the game's regional entry point in the same city — the same network distance your game traffic travels.

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."