Apex Error Code Guides
What each code actually means, and the fixes worth your time.
code:net
Apex Legends code:net means your connection to the game server was interrupted. Here's what causes it and the fixes that actually work, plus how to tell when it's EA's servers and not you.
code:leaf
Apex Legends code:leaf means the game failed to reach a server at all. Causes, working fixes, and how to tell a local problem from an EA outage.
code:100
Apex Legends code:100 means the game couldn't complete a connection to the EA servers — usually an account sign-in problem. Step-by-step fixes for PC, PlayStation, Xbox, and Switch.
code:wheel
Apex Legends code:wheel is a party and matchmaking connection error. What causes it, and the fixes that get your squad back into games.
code:snakeBan-related
Apex Legends code:snake is widely associated with account restrictions and matchmaking flags. What it means, what we know, and how to check whether an account was banned.
code:cloud
Apex Legends code:cloud means the game couldn't reach EA's online services. What causes it, how to tell an outage from a local problem, and the fixes that work.
code:shoe
Apex Legends code:shoe is a client error commonly tied to anti-cheat or corrupted game files. Here's what players have found causes it, and the fixes that clear it.
game logic error
"Encountered a game logic error and must shut down" in Apex Legends: what triggers this crash, and the fixes that actually stop it — on PC, PlayStation, and Xbox.
infinite loading
Apex Legends stuck on an infinite loading circle at the lobby or into a match? The causes — from server trouble to corrupted caches — and the fixes in the right order.
Getting errors out of nowhere? Before troubleshooting your own setup, check whether the problem is on EA's side — outage waves produce every code on this list at once. Our status page shows whether our own tracking of the Apex API is currently healthy, which is a good proxy for EA's backend.
Stuck on an error? Ask the server
Outages get confirmed in the Discord within minutes — see whether everyone is hitting the same code before you spend an hour troubleshooting your own setup.