Loading…
code:leaf appears when Apex can't establish a connection to a game server in the first place — as opposed to code:net, which is losing a connection you already had. It's most common right at matchmaking or on the loading screen into a match.
code:leaf hits everyone during EA-side incidents. If social feeds and outage trackers show a spike right now, the only fix is patience. Check before spending an hour on local troubleshooting.
On the lobby screen, open the datacenter list and look at ping and packet loss per region. If the auto-selected one looks wrong, pick another nearby datacenter and queue again — failing into one bad datacenter is the most common non-outage cause.
Fully close Apex and the EA app (or your console), then relaunch. Connection tokens go stale, and a fresh login clears them.
On Steam: Properties → Installed Files → Verify integrity. On the EA app: use Repair. A half-applied update can leave the client unable to negotiate a server connection.
Switch to a public DNS (1.1.1.1 or 8.8.8.8), and if your NAT type is strict, enable UPnP on the router. Both problems present exactly as "can't reach server" while the rest of the internet works.
code:leaf means the game failed to connect to a server; code:net means an existing connection was interrupted. Same family of causes, different moment of failure.
Either. If it started suddenly and other players are reporting it too, it's almost certainly EA-side. If it's just you, check your datacenter selection, DNS, and NAT type.
Respawn doesn't publish an official meaning for most of these codes. These guides are written from community troubleshooting and the patterns we see across tracked accounts. Your progress through the steps is saved on this device.