Loading…
code:net is Apex's generic network interruption error: the game lost its connection to the match or lobby server mid-session. It says nothing about whose fault it is — it fires the same way for a dropped home connection, a routing problem between you and the datacenter, or an EA-side outage.
If code:net appeared out of nowhere and you changed nothing, check server status before touching your own setup. When EA's services are degraded, no local fix will help — wait it out. A quick search for current Apex outage reports, or asking friends on the same region, settles it in a minute.
The classic fix for a reason: it clears stale NAT sessions and forces a fresh route to the datacenter. Power the router off for 30 seconds, restart Apex fully (not just to the lobby), and rejoin.
code:net is frequently just packet loss. Ethernet removes the single most common source of it. If you must stay on Wi-Fi, move closer to the router and get other heavy traffic (streams, downloads, cloud backups) off the network while you play.
From the title screen, wait on the lobby and open the datacenter list (it appears at the bottom of the screen after a moment). If your usual datacenter shows abnormal ping or packet loss, manually pick the next-closest one — a bad route to one datacenter often leaves others fine.
VPNs add hops and are regularly the whole problem. Turn the VPN off, make sure Apex and the EA app are allowed through your firewall, and if you use strict NAT, consider enabling UPnP or forwarding Apex's ports.
In an admin command prompt: ipconfig /flushdns, then ipconfig /release and ipconfig /renew. Cheap to try and occasionally clears a poisoned resolver entry that keeps steering you to a dead route.
It means the game lost its network connection to the server. It's a generic interruption error — the cause can be on your side, on the route in between, or on EA's servers.
No. code:net is purely a connection error and has nothing to do with account standing. Ban-related disconnects typically show different messaging.
Repeated code:net on every match usually means sustained packet loss — either your local network (fix: wired connection, router restart) or a bad route to one datacenter (fix: manually select a different datacenter). If it started suddenly for you and your squad at once, it's most likely an EA-side problem.
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.