ARSB0003 is a backend service communication error that often appears with "online services unavailable" or queue failures. It indicates the game client could not reach or complete a handshake with Embark's online services. Restart the game, check arcstatus.com for live status, and wait during high-load events like patch days or expedition launches.

ARRT0003 is another backend service error that can appear alongside ARSB0003 when online services are unavailable or queues are failing. Both indicate server-side or backend communication issues rather than matchmaking (ARMR) or in-raid (AREX) failures. Check live status and retry after a short wait.

Difference between ARSB and ARMR errors?

ARMR errors are matchmaking handshake failures (e.g. ARMR0002) that block you from finding a match. ARSB and ARRT errors are broader backend/service communication errors that can cause "online services unavailable" and queue failures before or during login. Both can occur during server load; ARSB/ARRT are often tied to service availability rather than matchmaking specifically.

🔌

Arc Raiders ARSB & ARRT Error Codes

Online services & queue failures

ARSB0003 and ARRT0003 often appear alongside “online services unavailable” and queue failures. These are backend service communication errors—distinct from matchmaking (ARMR) and in-raid (AREX) failures. The game client cannot complete communication with Embark’s online services layer.

ARSB0003

Backend service communication failure; often seen with “online services unavailable” or when the queue fails to connect.

Fix: Restart the game. Check live status on the homepage. During high-load events (patch days, expedition launches), wait 10–15 minutes and retry.

ARRT0003

Similar backend/service communication error; can appear with ARSB0003 when online services or queue are failing.

Fix: Same as ARSB—restart game, check arcstatus.com for active incidents, and wait during peak load (patches, expedition windows) before retrying.

Quick fix steps

Restart the game and launcher.
Check the homepage live status for active outages or degradation.
During high-load events (patch days, expedition launches), wait 10–15 minutes and try again—backend capacity often recovers.

For matchmaking-specific errors, see ARMR0002. For in-raid disconnects, see AREX errors. For general fixes, see Common Fixes.

← Common Fixes · Live status