Kickoff hits zero, you dodge in — and the ball ghosts through your car into your net. Rocket League’s physics live on the server, so your spikes don’t hide: they replay as teleports everyone in the match can see. 60 ms is the practical line, and a steady line beats a fast-but-jumpy one every kickoff. Run the 25-second test below — it counts the spikes your average ping is hiding.
Under 60 ms and flat. That’s the threshold LagScope scores Rocket League against in its per-game readiness chips — under it, your inputs reach the server fast enough that the ball behaves the way your screen promised. Between 60 and 90 ms the game is playable but aerials and 50/50s get coin-flippy: your car reacts on time, the ball’s position is already stale. Past 90 ms you’re defending against physics from the recent past. What separates Rocket League from most games is how little you can hide: the ball is server-authoritative, so a single 300 ms spike doesn’t just cost you the touch — it shows the whole lobby a teleport. Jitter is the quiet killer too: a line bouncing between 25 and 80 ms plays worse than a locked 70, because your muscle memory calibrates to a delay that keeps changing. The test above measures all four numbers — average, jitter, loss, spikes — because the average alone lies.
| Average ping | Verdict for Rocket League |
|---|---|
| Under 60 ms | Competitive-ready. Kickoffs, flicks and 50/50s resolve the way they look. Blame the whiff, not the wire. |
| 60–90 ms | Playable, not ideal. Ground game fine, aerial timing borrowed. You’ll lose some 50/50s you clearly won on your screen. |
| Over 90 ms | Rough. The ball lives half a second in the past. Fix the connection before the next ranked session. |
Because the server owns the truth. Your client predicts the ball locally so the game feels instant, but the authoritative position comes from the server — when your updates arrive late or go missing, the client snaps the ball to where the server says it really is. That snap is the teleport, the ghost hit, the demo that didn’t register. Three network patterns cause it: spikes (a sudden 300–800 ms jump — one bad second, one conceded goal), packet loss (your inputs never arrive, so the server simulates a car that did nothing), and jitter (constantly shifting delay that keeps breaking the prediction). Psyonix built diagnostics right into the game for this — the Connection Quality Indicators flag high ping, packet loss and server health mid-match, and Epic’s own Rocket League connection guides walk the same checklist we do. What the in-game icons can’t tell you is whether it’s been happening all evening or only when the house is busy — that’s what the timestamped log is for.
Run the 25-second test above. No spikes, no loss, while every car in the match teleports? That’s the server having a bad night — check Psyonix/Epic’s status channels. Spikes or loss at the exact moments the ball ghosted through you? That’s your connection — usually Wi-Fi, a loaded line, or the wrong region.
Four usual causes: the matchmaking region set wrong (or Recommended guessing badly), Wi-Fi interference, bufferbloat when the line is busy, or bad ISP routing. Because the ball is server-authoritative, even small spikes show up as visible teleports — so a spike-counting test finds it faster than an average.
Casual, survivable; ranked, a liability. Rocket League shows you your Wi-Fi problems more honestly than most games — every micro-spike becomes a ball teleport or a ghost hit. Ethernet removes the whole class of problem, and a quick A/B of your own link proves it in minutes.
The 25-second test is a snapshot. The full LagScope monitor watches your connection for as long as you play — lagspikes, outages, bufferbloat, 24-hour history — and builds a timestamped evidence report you can show your ISP. Free, no signup, runs in your browser.
Open the full monitor