AL
Apex Legends
EA / Respawn
Battle Royale
20 Hz tick
...ms
Pinging...
Apex's low server tick rate makes ping consistency more important than raw value. High jitter ruins fights even at 50ms.
pong@pong-com latency/apex-legends$
Apex Legends Ping Test
Apex's low server tick rate makes ping consistency more important than raw value. High jitter ruins fights even at 50ms. We test ping from your browser to Pong.com edge nodes co-located with Apex Legends's server regions, so you see what your real in-game latency should look like before you queue.
Genre: Battle RoyaleTick rate: 20 HzRegions: 7
Pinging game-server regions...
// Server regions
NA-East (Virginia)
edge: speed-ewr.pong.com
NA-Central (Dallas)
edge: speed-dfw.pong.com
NA-West (LA)
edge: speed-lax.pong.com
EU (London)
edge: speed-lhr.pong.com
EU-Central (Frankfurt)
edge: speed-fra.pong.com
Asia (Tokyo)
edge: speed-nrt.pong.com
Oceania (Sydney)
edge: speed-syd.pong.com
// Latency thresholds for Apex Legends
Excellent
< 35ms
Pro-tier latency. You have a real edge in close trades and reaction-based plays.
Good
< 65ms
Competitive ranked is a fair fight. Most players will not notice a disadvantage.
Playable
< 100ms
Casual play is fine. Trades and timing-sensitive mechanics will go against you.
// How to reduce ping in Apex Legends
- Use Ethernet over Wi-Fi. Wireless adds 5 to 25ms of jitter even on a strong signal.
- Pick the closest server region in Apex Legends's settings. The lowest ping in the table above is your target.
- Enable QoS or SQM (cake, fq_codel) on your router. Bufferbloat is the number one hidden cause of in-game lag spikes.
- Run our bufferbloat test under load to confirm your router holds up when someone else streams or uploads.
- Avoid peak ISP hours (7pm to 11pm local) for ranked sessions if you share a connection. Schedule large downloads overnight.
// Frequently asked questions
?>What is a good ping for Apex Legends?
For Apex Legends, anything under 35ms is excellent and competitive. Under 65ms is solid for ranked or casual play. Up to 100ms is playable but you will feel the disadvantage in close fights. Above 100ms, you should switch server regions or troubleshoot your connection.
?>Why does my Apex Legends ping spike?
Common causes include Wi-Fi interference, bufferbloat on your router under load, an ISP routing change, the game matching you to a far-away server, congestion on your local segment during peak hours (7pm to 11pm), and background uploads (cloud sync, updates) saturating your upstream. Switching to Ethernet and enabling SQM on your router fixes most of these.
?>How does pong.com measure Apex Legends latency?
We ping Pong.com edge servers co-located in the same metro datacenters as Apex Legends's real server regions (NA-East (Virginia), NA-Central (Dallas), NA-West (LA), EU (London), EU-Central (Frankfurt), Asia (Tokyo), Oceania (Sydney)). Each region is pinged multiple times per cycle and we report the median round-trip time plus jitter. Browser HTTP RTT is typically 5 to 15ms higher than the in-game UDP ping you see, so treat this number as an upper bound.
?>Can I lower my ping to Apex Legends servers?
Yes. Use a wired Ethernet connection, pick the closest server region in Apex Legends's settings, fix bufferbloat with SQM or QoS on your router, switch to a fiber ISP if you are on cable or DSL, and avoid VPNs unless they have a node in the same metro as your game server. Closing background apps that consume upstream bandwidth also helps.
?>Why is the in-game ping different from this test?
Two reasons. First, browsers use HTTP, which adds 5 to 15ms over the UDP packets the game uses. Second, this tool pings the nearest Pong edge in the same metro as Apex Legends's server, which is a close proxy but not the exact route your game client takes. Use the result as a reliable upper bound and a way to compare regions.
// Related
- All games latency test Ping every supported game in one view.
- Fortnite ping test Battle Royale server latency.
- Call of Duty: Warzone ping test Battle Royale server latency.
- Valorant ping test Tactical FPS server latency.