How to Fix Packet Loss in Apex Legends

Few things in Apex Legends are more frustrating than lining up a perfect Wingman shot, hearing the hit sound, and watching the damage number never appear. Or sliding behind cover only to get downed a full second later by bullets that should have missed. These aren't just "bad servers" in the abstract — they're the direct, measurable consequences of packet loss between your machine and Respawn's game servers.

Packet loss in Apex Legends manifests in several immediately recognizable ways. No-regs — shots that visually connect but deal no damage — are the most infamous. Your client registers the hit locally, plays the sound effect, and even shows a damage indicator, but the packets carrying your shot data never reach the server (or the server's confirmation never reaches you). The result: your opponent takes no damage and you lose a gunfight you should have won.

Rubber-banding is another telltale sign. You're sprinting through Fragment East, and suddenly your Legend snaps back to where they were half a second ago. The server never received your movement packets, so when it reconciles your position, it yanks you back. In a close-range fight, this is a death sentence. You may also see other players teleporting — stuttering across your screen in short jumps rather than moving smoothly. That's packet loss on their end, on the server's end, or on yours causing missing position updates.

Prediction errors appear when your client's simulation of the game world diverges too far from the server's. Apex's netcode uses client-side prediction to keep the game feeling responsive, but when packets go missing, those predictions become increasingly wrong. Doors that appear open are actually closed. Enemies are three meters from where you see them. The game world becomes a lie.

When things go wrong, you'll notice small icons appearing in the top-right corner of your screen. These are Apex's built-in connection indicators, and learning to read them is the first step to diagnosing whether your problem is packet loss, latency, or something else entirely. Before you blame the servers, blame your ISP, or blame the game — learn what your connection is actually doing.

Reading Apex's Connection Indicators

Apex Legends displays connection status icons in the top-right corner of your screen whenever it detects network problems. Each icon represents a different type of issue, and understanding them will tell you exactly what's going wrong. Here's what each icon means and when you should be concerned.

Prediction Error (Two Overlapping Squares)

This icon appears as two offset squares and indicates that your client's predicted game state has diverged from the server's actual state. When you see this, your game is showing you something different from what the server believes is happening. Small, occasional flashes of this icon are normal — Apex constantly reconciles prediction — but sustained or frequent appearance means the game is struggling to stay in sync. This typically results from a combination of high latency and packet loss, and it's the icon most directly associated with no-regs and enemies appearing to teleport.

Congestion (Speedometer Icon)

The speedometer icon signals network congestion — the path between you and the server is saturated or throttled. This often means a router somewhere along the route is dropping packets because its buffers are full. If you see this icon, someone on your network may be running a large download or upload, your ISP may be experiencing peak-hour congestion, or there's a bottleneck at a peering point between your ISP and EA's data centers. Congestion is one of the most common root causes of packet loss.

Packet Loss (Dotted Square)

A square made of dotted or dashed lines is the explicit packet loss indicator. When this appears, the game is detecting that packets between you and the server are being dropped. This is the most direct indicator that you have a packet loss problem. If it flashes briefly during a match, it may be a momentary blip. If it stays on or appears frequently, you have a persistent issue that needs troubleshooting. Even 2-3% packet loss in a fast-paced game like Apex is enough to cause consistent no-regs and rubber-banding.

Latency (Clock Icon)

The clock icon indicates high latency — your round-trip time to the server is elevated. High latency alone doesn't cause no-regs (Apex uses lag compensation), but combined with packet loss it makes prediction errors worse and widens the gap between what you see and what the server sees. If you only see the latency icon without the packet loss icon, your problem is distance or routing rather than dropped packets.

When multiple icons appear simultaneously, that's when gameplay suffers the most. Packet loss plus prediction error is the classic no-reg combination. Congestion plus packet loss means your connection is overwhelmed. If you're seeing these icons regularly, it's time to run a proper packet loss test using a tool like PacketProbe to get hard numbers before you start troubleshooting.

What Causes Packet Loss in Apex Legends

Packet loss in Apex has several potential sources, and pinpointing the right one saves you from wasting time on fixes that won't help.

Respawn and EA Server Infrastructure

Apex Legends has a well-documented history of server issues. The game runs on Multiplay (now part of Unity) hosted servers, contracted through EA. These servers operate at a 20Hz tick rate — meaning the server sends and receives game state updates 20 times per second. For context, Valorant runs at 128Hz and Counter-Strike 2 at 64Hz. This lower tick rate doesn't directly cause packet loss, but it means each lost packet carries more game state data and creates a larger gap in information. A single lost packet at 20Hz represents 50ms of missing game data compared to roughly 8ms at 128Hz.

Server-side issues are especially prevalent during new season launches, collection events, and limited-time modes when player counts surge. Respawn's servers have experienced widespread outages and degraded performance during nearly every major content update. When the servers themselves are struggling, no amount of client-side optimization will help.

Data Center Selection

Apex lets you choose your data center from the main menu, but the default behavior is to auto-select based on ping. This auto-selection doesn't account for packet loss — it may route you to a server that has low latency but drops packets along the way. Players in certain regions may find that a server with slightly higher ping but a cleaner route actually plays better. Understanding how to manually select your data center is one of the most impactful fixes available.

ISP Routing to EA Data Centers

Your packets travel through multiple networks between your home and the game server. If your ISP has poor peering arrangements with the networks hosting EA's servers, or if traffic is routed through congested exchange points, you'll experience packet loss that shows up only in Apex (while other games or speed tests look fine). This is frustratingly common and difficult to fix from your end, though changing data centers can sometimes route you through different network paths.

Wi-Fi and Home Network Issues

Wireless connections introduce packet loss that doesn't exist on wired connections. The 2.4GHz band is especially problematic — interference from neighboring networks, Bluetooth devices, and microwaves causes intermittent packet drops. In a game where fights are decided in fractions of a second, even occasional Wi-Fi packet loss can cost you gunfights. Every competitive Apex player should be on Ethernet. If that's not possible, a 5GHz connection with clear line-of-sight to your router is the minimum acceptable setup.

Cross-Play Server Selection

When playing in cross-play lobbies, server selection can behave differently. If you're partied with players from different regions, the game may place you on a server that's a compromise for everyone but optimal for nobody. Cross-play parties between console and PC players use PC servers, which can affect which data center pool you're drawn from. If you notice worse performance when playing with friends in other regions, this is likely the cause.

How to Fix Packet Loss in Apex Legends

Work through these fixes in order. Each one targets a different potential cause, and testing after each change will help you identify what's actually helping.

Manually Select Your Data Center

This is the single most impactful change most players can make. By default, Apex auto-selects a data center, and it doesn't always choose well. To access the data center selector:

  1. Launch Apex Legends and reach the title screen (the screen with the "Continue" or "Press to Play" prompt).
  2. Wait at least 60 seconds without pressing anything. This is critical — the game needs time to ping all available data centers.
  3. Open the Accessibility Options (the small icon in the bottom-left of the title screen).
  4. Close the Accessibility Options menu.
  5. Look at the bottom of the screen — you'll now see a "Data Center" option that wasn't there before. Select it.

You'll see a list of all available servers with their ping and packet loss percentage. Don't just pick the lowest ping. Choose a server that shows 0% packet loss with a reasonable ping (under 60ms is ideal, under 80ms is workable). A server with 45ms ping and 0% loss will play dramatically better than one with 20ms ping and 2% loss.

Use a Wired Ethernet Connection

If you're on Wi-Fi, switch to Ethernet before trying anything else. This eliminates the most common source of intermittent packet loss. If running a cable isn't feasible, consider powerline Ethernet adapters or MoCA adapters (which use your home's coaxial cable). Both are significantly more reliable than Wi-Fi for gaming. To verify the improvement, test your connection at PacketProbe on both Wi-Fi and Ethernet and compare the packet loss numbers.

Forward Apex Legends Ports

Port forwarding ensures that Apex's traffic isn't being filtered or delayed by your router's NAT. Log into your router's admin panel (typically at 192.168.0.1 or 192.168.1.1) and forward these ports to your gaming device's local IP address:

UDP ports: 1024-1124, 3216, 3478-3480, 8000-8999

TCP ports: 80, 443, 1024-1124, 3216, 8000-8999

If your router supports UPnP, Apex should handle port mapping automatically — but UPnP is notoriously unreliable on some routers, so manual forwarding is the more dependable approach. After forwarding, restart your router and verify the ports are open.

Flush Your DNS Cache

Stale or corrupted DNS entries can cause connection issues during server matchmaking. Flushing your DNS cache forces your system to get fresh records:

Windows: Open Command Prompt as Administrator and run ipconfig /flushdns

PlayStation: Rebuild your database from Safe Mode (option 5)

Xbox: Hold the power button for 10 seconds to fully power cycle, or go to Settings → Network Settings → Advanced Settings → Alternate MAC Address → Clear

This is a quick fix that occasionally resolves connection issues, especially after server maintenance or when EA's infrastructure changes.

Repair Game Files

Corrupted or incomplete game files can cause unexpected network behavior. In the EA App, right-click Apex Legends in your library, select "Repair," and let it verify all files. On Steam, right-click Apex in your library, go to Properties → Installed Files → Verify integrity of game files. This process checks every file against EA's servers and re-downloads anything that's damaged or missing.

Apex Network Settings and Common Myths

Apex has a few in-game settings that help you monitor your connection, and a few widely-shared "tips" that don't actually do what people think.

Enable Performance Display

Go to Settings → Gameplay and enable Performance Display. This adds a real-time overlay showing your FPS, ping, and packet loss percentage in the top-right corner of your screen during gameplay. This is far more useful than the connection icons alone because it gives you exact numbers. Watch your packet loss during matches — if it spikes during fights (when more data is being transmitted), that points to congestion. If it's consistently elevated, the problem is more fundamental.

The -tickrate Launch Option (Myth)

You'll find forum posts and YouTube videos claiming that adding +cl_updaterate 144 or -tickrate 128 to your Apex launch options forces a higher tick rate. This does not work. The server tick rate is set server-side and cannot be changed by clients. These are Source engine commands inherited from Titanfall's codebase, and Apex ignores them. The game communicates at 20Hz regardless of what launch options you set. Adding these commands is harmless but provides zero benefit — don't let anyone convince you otherwise.

Adaptive Supersampling and Perceived Lag

Adaptive supersampling resolution (found in Settings → Video) is a rendering setting, not a network setting — but it can contribute to perceived lag. When this setting is enabled, the game dynamically adjusts render resolution to maintain a target framerate. During intense moments (exactly when network issues also tend to spike), the resolution drops, the image gets blurry, and combined with any actual packet loss, the game feels significantly worse. If you're already struggling with connection issues, set your resolution scale to a fixed value that your hardware can maintain consistently. Eliminating frame drops removes one variable so you can accurately judge whether your problems are network-related or performance-related.

Other Useful Settings

Disable cross-play temporarily to test if your packet loss improves — cross-play matchmaking can route you through different server infrastructure. If you're on PC, make sure V-Sync is off or use a frame cap set slightly below your monitor's refresh rate. V-Sync adds input lag that compounds the feeling of network delay. Finally, check that Steam overlay or EA overlay isn't causing frame hitches that you're misattributing to network problems — disable both overlays and test.

Dealing with Apex Server Problems

Sometimes the problem isn't on your end at all. Apex Legends has a reputation for server instability, and knowing how to distinguish server-side issues from client-side ones saves you hours of unnecessary troubleshooting.

Check EA Server Status

EA's official server status page at https://help.ea.com/en/help/faq/connection-troubleshooting/ shows whether Apex's servers are experiencing issues. However, this page is slow to update and sometimes shows green even during widespread problems. For faster, more accurate information, check the r/apexlegends subreddit — if servers are having problems, you'll see dozens of posts about it within minutes. Third-party sites like Downdetector also aggregate user reports and can confirm outages faster than EA's official channels.

Server Maintenance Windows

Respawn typically deploys patches and performs maintenance on Tuesday mornings (Pacific Time). Major updates usually drop around 10 AM PT. During these windows, servers may go down entirely or experience degraded performance for 30-60 minutes. If you're experiencing sudden packet loss or disconnections on a Tuesday morning, check for patch notes before you start troubleshooting your home network.

Distinguishing Server Issues from Client Issues

Here's how to tell whether the problem is you or the servers:

When It's Your ISP

If your packet loss test to general servers looks clean but you consistently have loss to Apex specifically, your ISP likely has a bad route to EA's data centers. Run a traceroute to an Apex server and look for where packet loss begins. Armed with this data, contact your ISP and request they investigate routing to Multiplay or EA's hosting infrastructure. Some players have had success asking their ISP to route them through a different backbone — but this is ISP-dependent and not always possible.

For a deeper understanding of how packet loss works across any application, read our complete packet loss guide, which covers the fundamentals of packet loss, how to measure it accurately, and general strategies for fixing it regardless of which game or application you're troubleshooting.

Test Your Connection for Apex →