How to Fix Apex Legends Error Code 100: Unable to Connect to EA Servers

You launch Apex Legends, ready to drop into the Outlands, and instead of the lobby you get a login error: Error Code 100, unable to connect to the EA servers. Sometimes it appears the moment you press Continue, sometimes it spins for a while and then fails, and sometimes it only shows up at peak hours — right when you actually have time to play. The message gives you no useful detail, just a number.

In plain English, error code 100 means your game could not complete its connection to the EA servers during login. Apex reached out to start a session, but the handshake failed somewhere along the way, so the game cannot verify your account or load your profile and stops at the login screen. The good news: this is a connection problem, not an account problem, and it is almost always fixable. The fixes below are ordered from the quickest wins to the deeper connection repairs, so start at the top and stop when the lobby loads.

What does error code 100 actually mean?

Every time you log in, Apex Legends has to do a small but strict dance with the EA servers: prove who you are, pull your profile, and open a session on the matchmaking service. Error code 100 fires when that dance breaks down before the session opens. It is deliberately vague — the game knows the handshake failed, but not always why — so the same code covers a wide range of causes, from EA-side outages to your own router.

This distinction matters because it tells you where to look first. If the servers are down, nothing on your machine will help, and every fix you try will fail for the same reason. If the servers are healthy, the fault is local: your connection, your cache, your DNS, or something between you and EA. Fix 1 exists specifically to separate those two worlds before you touch a single setting.

What causes Apex Legends error code 100?

The usual suspects, from most to least common:

• EA server outages or maintenance — the single most common cause during season launches, big updates, and peak hours.
• A stuck game session or temporary connection state — the previous session never closed cleanly, and the new login collides with it.
• Router or modem trouble — stale NAT entries and routing state that block the login handshake.
• Corrupted cache — stale or damaged session data in the EA app or the game itself.
• DNS problems — an ISP DNS server that resolves EA's login servers slowly or incorrectly.
• VPNs, proxies, or security software — tools that intercept or reroute the login handshake.
• Strict NAT or blocked ports — a router setup that will not let the game open the session it needs.
• Corrupted game files — the least likely cause, but the one a reinstall fixes.

1Check the EA servers first

Before you change anything on your side, check the EA server status page and the Apex Legends service status, plus community reports on outage trackers. Error code 100 spikes during season launches, major updates, and scheduled maintenance, and in those windows the only fix is patience. If the servers are reported down or degraded, close the game, wait an hour or two, and try again. If the servers are green and healthy, move on — the problem is on your side, and the rest of this guide applies.

2Restart the game and your device

The classic fix works here more often than players expect. Close Apex Legends completely — on PC, make sure no Apex or EA app process is still running in the background — then restart your PC or console. A full restart clears the stuck session and the temporary connection state that so often triggers code 100, and it is the fastest way to rule out a one-off glitch. Launch the game fresh after the restart and try logging in before changing anything else, so you know whether the restart alone did it.

3Restart your router and modem

Your router keeps a table of active connections, and a stale or corrupted entry can block the Apex login handshake indefinitely. Power off your router and modem for a full minute — not just a quick reboot, a real power-off — then power them back on and wait for the connection lights to stabilize. This clears stale NAT entries and forces a fresh route to EA's servers. Once your internet is back, launch Apex and try again. If you are on Wi-Fi, also try moving closer to the router for this test, since a weak signal can produce the same intermittent handshake failures.

4Clear the game and launcher cache

Corrupted cached session data is one of the most common local causes of code 100. On PC: open the EA app settings and use the option to clear the cache, then delete the Apex Legends local cache files from the game's saved-data folder. On PlayStation or Xbox: fully power down the console, unplug it for a minute to flush the system cache, then power back on. On console you can also clear the alternate MAC address from the network settings, which forces a fresh network identity. After the cache clear, launch Apex and log in fresh — a clean session with no stale data to trip over.

5Switch to a public DNS

Some ISP DNS servers resolve EA's login servers slowly, incorrectly, or not at all, and the game reports that failure as code 100. Switching to a public resolver removes that failure point entirely. Set your DNS to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1) — on PC in your network adapter settings, on console in the network configuration screen. Flush your DNS cache afterwards (on PC, run ipconfig /flushdns in a command prompt), then try logging in again. If the login suddenly works, your ISP's DNS was the culprit all along, and you can simply leave the public DNS in place.

6Try a wired connection and check your ports

Wi-Fi introduces packet loss and interference that can break a strict login handshake, so if you can, switch to a wired Ethernet connection for this test. Then check your NAT type: on console it is shown in the network settings, and a Moderate (Type 2) or Open (Type 1) NAT is what you want. A Strict (Type 3) NAT often blocks the session Apex needs. Enable UPnP on your router if it is off — that lets the game open the ports it needs automatically — and avoid double-NAT setups (a router behind another router) if you can. If the wired connection with an open NAT logs in fine, the problem was your network path, not the game.

7Disable VPNs, proxies, and security software temporarily

VPNs, proxies, and third-party firewalls or antivirus tools sit between Apex and EA's servers, and they can intercept or reroute the login handshake in ways the game does not tolerate. Turn off any VPN or proxy completely and try logging in on your normal connection — many players find code 100 vanishes the moment the VPN goes off. If you run a third-party firewall or antivirus, temporarily disable it (or add Apex and the EA app to its allowed list) and retest. If the login works with the software off, you have found the culprit: either leave it off while playing or configure an exception for Apex and the EA app.

8Reinstall the game as a last resort

If every fix above failed, go for the clean slate. Uninstall Apex Legends completely, restart your device, and install it fresh from your launcher or store. A clean install replaces any corrupted core files that cache clears cannot reach, and it is the definitive test for file corruption. Your account progress, skins, and stats live on EA's servers, so a reinstall loses nothing — you will log back into the same account. And if code 100 still survives a clean install on a healthy connection with the servers up, it is time to contact EA Help with your platform, region, and the exact time the error appears; that combination points to an account-side or regional routing issue only EA can see.

Quick checklist to keep error code 100 away

• Check the EA server status first whenever code 100 appears — do not troubleshoot a server outage.
• Restart the game and your device fully after updates; half-closed sessions are a classic trigger.
• Keep your router firmware updated and reboot it occasionally — stale NAT state causes silent login failures.
• Use a public DNS if your ISP's resolver has ever caused trouble; it costs nothing and removes a failure point.
• Play on a wired connection when you can, and keep your NAT at Moderate or Open.
• Turn the VPN off before launching Apex — it is the most common self-inflicted cause of code 100.

Frequently asked questions

For most players, error code 100 ends at Fix 1, 2, or 3 — a server check, a restart, or a router reboot, and the lobby loads again. The lesson worth internalizing: this is a connection problem, not an account problem, so do not panic about your progress or reinstall the game before working through the quick fixes. And while you wait out a server outage, the free browser games here on GameAdda need no login at all. 🎮