Why Ping Hits Harder in Apex Legends Than in Other Shooters

Apex Legends runs its servers at a 20Hz tick rate, meaning the server only processes and broadcasts game state 20 times per second — once every 50ms. Compare that to a 64-tick or 128-tick shooter, where the server updates every 15ms or less. That gap matters more than most players realize: on a low-tick server, every millisecond of your ping gets added on top of an already wide 50ms window, so the total delay between "you pull the trigger" and "the server registers it" stacks up fast. A 20ms difference in ping is a much bigger deal in Apex than the same 20ms would be in a 128-tick game, because the interpolation window games use to smooth other players' movement has to be wider to compensate for the slower tick — and a wider window means more guessing about where an enemy actually is right now.

This also amplifies peeker's advantage — the edge a player gets by being the one who initiates a peek around cover, since their client sees the fight start before the defender's client does. On a 20Hz server, the peeker's head start is longer, and high ping on top of that stretches it further. If you feel like you are consistently losing fights against players who "saw you first," tick rate combined with your own latency is very often the real explanation, not aim.

Ideal Ping Ranges for Apex Legends

Ping	Rating	What You'll Notice
0-30ms	Ideal	Movement tech (tap-strafes, wall bounces, super gliding) lands consistently; hit registration feels instant
30-60ms	Good	Comfortable for the vast majority of players; close-range trades still feel fair
60-90ms	Playable	Occasional delayed knocks and slightly spongy hit reg in close-range 1v1s
90-120ms	Risky	Regular rubber-banding, movement tech becomes unreliable, close fights favor the enemy
120ms+	Problematic	Frequent "I shot first" deaths, delayed ability activations, visible desync in firefights

Movement-heavy plays are the first thing to break down as ping rises, because tap-strafes and wall bounces depend on precise, low-latency input timing being reflected on the server almost immediately. If your inputs feel "correct" locally but the server keeps rejecting them, ping — not input lag — is usually the cause.

The Data Center Picker: Your Most Underused Tool

Most players never open Apex's server list, which is a mistake, because it shows real per-data-center ping and packet loss before you queue into a match. To open it, go to the lobby or main menu and press and hold the button or key bound to "Data Center" (on PC this is usually held on a specific key shown in the corner of the lobby screen; on console it is a held button prompt in the same spot). Holding it — rather than tapping — brings up the full list of available data centers with a live ping number and a packet loss percentage next to each one.

Read the list like this:

Ping column: pick the lowest number available, but do not chase a 5ms difference between two nearby data centers — it will not be noticeable in a match.
Packet loss column: treat any consistent loss above 0-1% as a bigger red flag than a slightly higher ping. Loss causes stutter and dropped inputs in a way that a stable extra 10-15ms of ping does not.
"Auto" or default selection: Apex's automatic matchmaking sometimes prioritizes fill speed over your best ping, especially off-peak. Manually locking a specific data center with a low ping and clean packet loss almost always beats leaving it on auto.

Set your preferred data center manually whenever the numbers support it, and re-check the list periodically — routing and server load both change over time, so what was the best pick last month may not be the best pick today.

Why You Sometimes Get Placed on a Far-Away Server

Even with a manually selected data center, you can still end up in a match that plays laggy, and the usual reason is matchmaking population, not your connection. Apex's matchmaker balances two competing goals: finding you a low-ping server and finding you a match with players close to your skill rank, fast enough that you are not stuck in a long queue. At very high or very low ranks, or during off-peak hours in your region, there simply may not be enough players near your skill level connected to your nearest data center. When that happens, the matchmaker widens its search — sometimes across regions — to keep queue times reasonable, and you get placed on a server farther away than usual.

This is more common late at night, during off-peak weekday hours, and at the top and bottom of the rank distribution, where the player pool is thinnest. If your ping is consistently higher during specific hours or specific ranked splits but fine otherwise, population — not your network — is the likely cause, and there is no local fix beyond queuing at busier hours or manually locking a data center that trades a few extra ms for a deeper player pool.

Reading the In-Game Performance Display

Apex includes a network HUD you can enable in the settings menu that shows live ping and connection-quality icons during a match. Turn it on before you troubleshoot anything else — it tells you what is actually happening on your connection in real time, rather than relying on how the match "feels."

Ping number: updates continuously; watch for sustained spikes during fights rather than the number at spawn, since that is when latency actually costs you.
Packet loss / connection icon: a warning icon or colored indicator appears when loss is detected. Any time this icon shows up during a firefight you lost, packet loss — not aim — is a very plausible explanation.
Server tick indicator: some display modes also show frame or update irregularities, which is useful for telling apart local hardware stutter from network-caused stutter.

Compare what the in-game display shows against an independent ping test run around the same time. If the browser test looks clean but Apex's own HUD shows high ping or loss, the problem is specific to the data center or route Apex is using — not your general internet connection. You can also use the Apex Legends ping test to check estimated latency to each regional data center before you even launch the game.

Fixes, Ranked by Actual Impact

Work through these roughly in order — the first two typically produce the biggest, most reliable improvement:

Pick the right data center manually. This is the single highest-impact change available, since it directly addresses both the ping and packet loss numbers Apex itself reports. Re-check it periodically rather than setting it once and forgetting it.
Get on Ethernet. Apex's low tick rate exposes every Wi-Fi timing spike far more than a high-tick game would, because there is less server-side smoothing to absorb it. See our Wi-Fi vs Ethernet for gaming comparison for the numbers behind why this matters.
Kill background bandwidth. Game updates, cloud saves, streaming services, and a second device downloading in the background all add latency and jitter under load, even on a fast connection. Pause everything non-essential before ranked sessions.
Enable QoS or fix bufferbloat on your router. If your ping jumps specifically when something else on the network is uploading or downloading, your router is likely queuing too much data before sending it. Quality of Service settings or Smart Queue Management fix this by giving game traffic priority.
Prioritize jitter over average ping. A stable 45ms connection beats an unstable connection that averages 25ms but spikes to 90ms during fights. If you have low average ping but still rubber-band, check jitter specifically — our jitter vs ping guide explains why variance breaks hit registration more than a steady delay does.

If you have worked through all of the above and Apex still feels inconsistent, run a broader diagnostic — packet loss on your line, not just in-game, is a common hidden cause. Our guide on what causes high ping covers the network-side culprits worth ruling out before you assume it is Apex's servers.