Players are running into long login queues, failed matchmaking, and occasional crashes as Arc Raiders handles a surge of people trying to get in. The most common symptom is a “Matchmaking has failed” error with code ARMR0002. Others are seeing a perpetual “in queue” message on launch, or waits of five to ten minutes before the Spaceport queue moves. Some sessions are dropping players back to menus after a crash or a group bug.

What’s causing Arc Raiders ARMR0002 and long queues

The current failures are tied to server load and the systems that form parties and handle voice. A login queue has been turned on to reduce strain, which means you may wait longer than usual to enter the game and to find a match. During spikes, matchmaking can stall, return ARMR0002, or bounce you back to the start of the process. It’s not typically something you can fix locally, but a few choices can keep you from making it worse.

Symptoms and what they mean

Symptom What it means right now What to try
“Matchmaking has failed” (ARMR0002) Matchmaking services are overloaded or briefly unavailable. Retry once and wait. If it fails again, back out to the main menu and give it a few minutes before re-queueing.
Launch shows “in queue” and doesn’t load Login queue is active; slots are opening slowly. Stay on the queue screen for 5–10 minutes. Avoid restarting the game repeatedly.
Spaceport queue sits for 6+ minutes Match pools are backed up; expect delays. Let the timer run. Many players get placed after several minutes without touching anything.
Kicked to menu after a crash Your session ended and the server can’t immediately reassign you. Relaunch and allow the pre-game queue to complete once. If you see ARMR0002 again, wait a few minutes before re-trying.
Can’t leave group / stuck squad state Party services are unstable under load. Restart the game once to clear party state, then queue again. Avoid rapidly reforming squads.

Fix “Matchmaking has failed” (ARMR0002)

  • Retry once, then wait: If you see ARMR0002, select matchmaking again a single time to rule out a transient error. If it reappears, stop and give it a few minutes before trying again.
  • Don’t bounce in and out of queues: Backing out, relaunching, and spamming the button increases your odds of landing in a stalled state or getting pushed back into the login queue.
  • Let the queue sit: Many players report being placed after five to ten minutes without interaction. Staying put is often faster than restarting.
  • Reform only if your party is clearly bugged: If the UI shows you in a squad you can’t leave, do a single client restart to reset party state, then try again.

Note: These errors are not usually tied to your network or hardware. Unless you’re seeing separate connectivity issues elsewhere, local tweaks won’t move the needle during a server surge.

Stuck on “in queue” at launch

When the game shows “in queue” on the initial launch screen, it’s holding you in the login queue. That can take several minutes when traffic spikes.

  • Wait it out for up to 10 minutes. Progress often happens in bursts.
  • If nothing changes after a long wait, perform one clean relaunch and try again. Avoid repeated relaunch loops.
  • Once you’re in, expect longer-than-normal matchmaking times in Spaceport as well.

Quick checklist that avoids the worst loops

  • Stay on the queue screen; don’t alt-f4 every few minutes.
  • Retry ARMR0002 once, then wait several minutes before the next attempt.
  • If your squad is stuck, restart once to clear it—don’t shuffle party members repeatedly.
  • Prefer solo queue during surges; invite friends later once you’re in a stable session.

What to expect next

Server-side work is ongoing, and queues are a deliberate throttle to keep things running while party and voice features are stabilized. That means patience usually pays off more than tinkering. If you’re repeatedly landing in ARMR0002 or an “in queue” loop during busy hours, stepping away and trying again later often results in a faster path to a match.