Co-op and Disconnect Issues#

ARC Raiders is an always-online extraction shooter: matchmaking, raids and progress sync all run on Embark’s online services — a disconnect does not just waste the run, it can take your loot with it. This page walks through co-op setup, error codes, disconnect recovery and server status checks in that order. Information verified on 2026-10-15.

Co-op Basics: Who You Can Play With#

Squads support up to three players, with PC, PS5 and Xbox fully cross-platform and enabled by default; a single instance holds roughly 12 to 18 players, and console co-op requires the relevant subscription.

ARC Raiders is developed by Embark Studios and launched worldwide on 2025-10-30 for PC (Steam, Epic Games Store) and PS5, Xbox Series X|S. The co-op fundamentals are listed below:

For squad roles and extraction coordination itself, see the dedicated Three-Player Squad Coordination page — it is out of scope here.

Turning Crossplay On and Off#

The toggle sits under Settings > Gameplay > Online > Crossplay and is on by default; turning it off restricts matchmaking to your own platform, and there is no “consoles only” style filter — it is either fully on or fully off.

A few practical notes:

• Just leave it on: crossplay matchmaking puts players from all three platforms in the same raids, which means faster queues and a livelier encounter ecosystem; unless you specifically want to match only players on your own platform, there is no reason to switch it off;
• The cost of turning it off: the matchmaking pool shrinks. It barely matters during peak hours, but queues get noticeably longer off-peak;
• There is no middle ground: there is no “console players only” or “controller players only” filter — on and off are your only two options for controlling the matchmaking pool.

Cross-Progression and Account Sync#

Progress, unlocks and gear sync across platforms through your Embark ID; every platform requires a separate purchase except Xbox, and Epic and Steam players can play together normally.

• Progress sync (cross-progression) and save sync (cross-save) are both tied to the Embark ID account, so logging into the same account on another platform carries over your character progression and stash;
• Each platform requires its own copy of the game; the Xbox version falls under the “Play Anywhere” policy, so one purchase covers both Xbox consoles and Windows PC — the only exception;
• Epic and Steam players can team up, since the account systems are unified under Embark ID; note, however, that Embark’s official support docs name Steam, PS5 and Xbox without explicitly mentioning Epic — trust your actual in-game experience;
• Progress from the earlier Server Slam open test does not carry over, but participants who verified their Embark ID email can claim the Server Slammer backpack charm.

Error Code Quick Reference: The Prefix Points the Way#

Error codes fall into five categories by phase — matchmaking, in-run, login, anti-cheat and online services; once you recognize the prefix, you know whether to check your network, your files or just wait on the servers.

A quick mnemonic: if it starts with ARAV, check your files and anti-cheat; AREX means check your local network; ARMR and ARSB mean suspect the server side first.

Handling Matchmaking Failure (ARMR0002)#

Wait about 15 minutes before queuing again — most matchmaking failures come from server congestion or protection policies; if it keeps happening, run through these five steps.

1. Wait about 15 minutes: failures caused by protection policies or matchmaking peaks usually clear themselves within a quarter of an hour;
2. Calibrate system time: set Windows time synchronization to automatic — a community-verified offbeat fix, since clock drift against the servers breaks the matchmaking handshake;
3. Reinstall anti-cheat: force a reinstall of the Easy Anti-Cheat service to rule out anti-cheat component issues;
4. Restart the game and your router: clear leftover local sessions and routing tables;
5. Check server-side status: read announcements on the official Discord or status trackers to rule out a widespread outage — if it really is the servers, no local fix will help.

Troubleshooting In-Run Disconnects (AREX Series)#

AREX codes are mostly local network issues: switch to a wired connection first, change DNS, flush the DNS cache and stop background downloads; if packet loss stays above 2%, call your ISP.

Work through them in order:

1. Switch from wireless to a wired connection — extraction shooters are extremely sensitive to packet loss, and a split-second spike can cut you off from the servers;
2. Change DNS to 8.8.8.8, 8.8.4.4 or 1.1.1.1 to bypass resolution problems on your ISP’s default nodes;
3. Run Command Prompt as administrator and execute ipconfig /flushdns to clear your local DNS cache;
4. If you are behind a strict NAT, set up port forwarding for the game to improve the connection success rate with the servers;
5. Close background downloads such as Steam updates and Windows Update so nothing eats your bandwidth;
6. Check that your firewall and security software are not blocking the game executable;
7. If packet loss stays above 2%, the fault is most likely on your ISP’s line — file a support ticket before tinkering with anything else.

Will You Lose Your Loot After a Disconnect?#

There is rollback protection, but it is not guaranteed during major server incidents; click Reconnect Available the moment it appears, because once the window closes the run cannot be recovered.

The mechanics and what to do about them:

• Rollback protection works like this: the server keeps a record of your progress before the drop, and restores the state to the last valid checkpoint on reconnect or settlement, avoiding the double loss of “connection gone, gear gone too”;
• But it is no absolute guarantee — Embark explicitly does not promise rollback during large-scale server incidents;
• Do not rush to close the game: when the “Reconnect Available” prompt appears, click it immediately. Once the reconnect window closes, the run cannot be recovered;
• Practical rule for squads: if someone drops, the rest hold position and stay alert, waiting out the reconnect window before deciding whether to keep looting or extract early — never drag a three-stack through a high-risk zone half-strength.

Server Regions and Latency Optimization#

You can switch server regions manually in-game to cut latency; with most servers hosted overseas, players in mainland China usually need an accelerator when latency runs high and unstable.

• Region switching: the toggle sits in the same settings area as crossplay; switch regions and watch how matchmaking latency and in-run packet loss change. Embark has not published a full server region list, so testing is the only way to know which node suits you best — play one raid per region, log the latency readings and feel, then lock in the best one;
• The reality on mainland networks: high latency and jitter can cause loading stutter, black screens and even crashes; accelerator pages such as NetEase UU and Thunder all recommend running this game through an accelerator — note that those pages are commercial promotions, so take the mechanism descriptions as reference and never trust the performance promises;
• Choosing an accelerator: judge it against three points based on how this game is built — whether it has dedicated ARC Raiders nodes (rather than a generic route), whether it offers a free trial period so you can measure latency yourself, and whether login or matchmaking actually gets worse after enabling it (if you start getting login authentication errors with it on, turn the accelerator off and compare once to rule out server risk control on that node).

The above covers general fixes; issues specific to ARC Raiders are best confirmed through official announcements.

Is It Your Network or the Servers?#

Start with official channels, then cross-check with third-party probes: all systems showed normal as of the verification time (2026-10-15); if probe reports spike, it is a widespread outage, so just wait for the fix.

How to tell:

1. Official channels: the official X account (@ARCRaidersGame) and official Discord are the first-hand sources for maintenance downtime and server faults;
2. Third-party probes: ArcStatus (arcstatus.com) probes every service once every 60 seconds; Downdetector’s page for this game aggregates voluntary player reports; several gaming media outlets also maintain aggregate status pages worth cross-referencing;
3. How to read it: multiple probes reporting trouble at once alongside a surge in player reports means a server-side outage; if everything reads normal and only you dropped, go back to the local network steps above.

Verification results as of 2026-10-15: ArcStatus reported all systems nominal; Downdetector showed no concentrated reports in the past 24 hours, with its historical report breakdown at 43% server connection, 38% game launch and 16% latency — connection issues lead, which fits an always-online game where one run equals one save.

A few server incidents worth remembering:

Also, slower matchmaking on patch days, weekends and evening peaks is normal; do not treat it as a fault, and do not keep reinstalling the game over it.

Co-op Quick Answers#

Related Guides#

• Three-Player Squad Coordination: queue differences across solos, duos and trios, plus the three-person role model;
• System Requirements and Performance Optimization: the current state of each platform version and how to tune for smoothness;
• FAQ: concentrated answers to the questions new players ask most;
• Extraction Mechanics Explained: extraction rules and how to make extraction decisions;
• Update Timeline and Seasonal Content: patch cadence and content updates at a glance.