Arc Raiders AREX Error Codes — In-Raid Disconnect Fix
Stop mid-raid disconnects and protect your loot
AREX errors are in-raid connection failures. Unlike ARMR errors (which block you from matchmaking), AREX errors happen during an active raid and may result in loot loss. Your local client keeps running but the server drops the session—your character stays “alive” on the server but unresponsive, and ARC enemies will keep attacking your paralyzed character. This is the most feared error category for experienced players.
AREX0001
Meaning: Session lost. Server dropped the instance.
Usually a server-side issue.
Fix: Check arcstatus.com homepage for active outages before requeuing.
AREX0003
Meaning: Network timeout. Connection between client and server timed out.
Fix: Check for ISP throttling, switch from WiFi to ethernet, disable VPN, check Windows firewall isn’t blocking the game.
AREX0024
Meaning: Severe packet loss causing session termination.
Fix: Run a ping test to game servers, contact ISP if packet loss is above 2%, check router QoS settings, try flushing DNS (ipconfig /flushdns).
Do I lose my loot after an AREX error?
Embark has rollback protection but it is not guaranteed during severe outages. Whether you recover loot depends on how quickly you can reconnect and whether Embark issues a rollback. For full details on server vs client crashes and the reconnect window, see our crash loot survival guide.
How to reduce in-raid disconnects
- Use ethernet over WiFi whenever possible.
- Set DNS to 8.8.8.8 / 8.8.4.4 (Google) or 1.1.1.1 (Cloudflare).
- Port forwarding basics: forward the ports Arc Raiders uses (check Embark’s support docs) if you’re behind a strict NAT.
- Disable background downloads (Steam, Windows Update) during raids.
Live status · Matchmaking issues · ARSB/ARRT (online services)