Rocket League FAQ — Ping, Servers, Network

Yes. PingAim auto-detects RocketLeague.exe and routes its traffic through the network interface you choose using a WFP kernel driver. It is fully compatible with Easy Anti-Cheat — PingAim operates at the Windows network stack level and does not modify the game client or inject into the game process.

Internet speed (bandwidth) and ping (latency) are different things. Rocket League uses very little bandwidth (~80-90 kbps in a 2v2). High ping is caused by your ISP routing packets through inefficient paths to i3D.net game servers. Even on a 1 Gbps connection, if your ISP sends packets through 15 hops instead of 5, your ping will be high. A traceroute to the game server IP can reveal where the delay occurs.

Below 40ms is ideal — prediction errors are minimal and gameplay feels responsive. 40-80ms is playable but you'll notice occasional phantom touches and slightly delayed ball contact on aerials. Above 80ms starts to significantly impact aerial accuracy and kickoff timing. Above 120ms makes competitive ranked very difficult due to frequent prediction corrections.

Rocket League predicts the ball's position ahead of time based on your ping. When the server sends a correction that differs from the prediction, the client snaps the ball to the correct position. This happens more often with high ping, jitter, or packet loss. A stable, low-ping connection minimizes prediction errors. Keeping Rocket League on a connection that isn't sharing bandwidth with streams or downloads stabilizes the round-trip time the client's prediction depends on.

There are no documented bans from Psyonix/Epic for using ExitLag, WTFast, Hone, or similar packet-routing tools, and EAC's published scope targets cheat software and DLL/process tampering, not network drivers. PingAim uses a WFP driver that operates at the Windows network stack level — outside EAC's game-process scope.