Apex Legends FAQ — Ping, Servers, Network

Yes. PingAim auto-detects r5apex.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 any code into the game process.

Internet speed (bandwidth) and ping (latency) are fundamentally different. You can have 1 Gbps download speed but still have 100ms ping if your ISP routes packets through 15 hops instead of 5 to reach the AWS datacenter. After the April 2025 AWS migration, server locations changed — your ISP may now route differently to the new datacenter locations. Use the Data Center menu to check your ping to each server.

Below 40ms is the target for competitive play with consistent hit registration. 40-80ms is playable but you may experience occasional no-regs and get killed behind cover more often. Above 80ms, the 20 Hz tick rate compounds the problem — rubber-banding and hit registration issues become frequent. Above 120ms, competitive play is severely impaired.

No-regs happen when your client registers a hit (showing damage effects) but the server disagrees and awards zero damage. This is caused by the combination of client-side hit registration, lag compensation, and the 20 Hz tick rate. Higher ping increases the chance of no-regs because there is more time for the target to move between when your client registered the hit and when the server validates it. Bringing ping down is the most effective fix.

Yes. In April 2025, Respawn migrated all Apex Legends servers from Multiplay (Axiom) infrastructure to Amazon Web Services (AWS GameLift). Server locations changed: London was removed, some NA servers were consolidated, and all servers now use AWS region codes (e.g., us-east-1, eu-central-1). This may have changed which server gives you the best ping — check the Data Center menu.