When ARC Raiders shows an “In Queue” message at launch, it’s signaling a temporary login gate. The game is limiting how many players can enter at once to protect back-end services that handle core features like party formation and voice chat. The login queue does not display a position or timer, and during these windows you can’t go Topside, manage inventory, or do any prep work in the hub.

Embark has described the measure directly: “The team has implemented a login queue as a temporary measure in order to mitigate issues related to forming parties and using voice channels which will make your matchmaking longer than usual.” The studio also acknowledged load-related disruption: “We are sorry for the disruption and we are humbled to see so many of you jumping into the game to the point that we need to temporarily limit the amount of players we can let back Topside.”

Why queues and matchmaking are longer right now

The spike is substantial. ARC Raiders has pushed past 330,000 concurrent players on Steam, peaking around 337,834 before dipping within the hour — and that doesn’t include consoles or other PC storefronts. Under that kind of demand, the systems that create squads and power in-game voice are the first to strain, which translates into:

  • Login gates that hold players outside the hub with a non-specific “In Queue” message
  • Matchmaking searches that linger 5–10 minutes or error out
  • Stalls that bounce you back to the start of the matchmaking flow

Some of the instability appears region-dependent at times, but enough players are impacted that queueing and slower matchmaking can appear broadly during peak hours.

What you can do if you’re stuck in the queue

There isn’t a guaranteed client-side fix for a server-side throttle, but a few approaches have helped some players get back in sooner:

  • Let the login screen sit. Leaving the client open has, at times, allowed the queue to clear and the hub to load without further input.
  • Be patient with pre-game queues. If you reach the hub, expect longer-than-usual waits when you queue for a match; some sessions do eventually form after an extended search.
  • Lightweight restart (anecdotal). A commonly shared workaround: with the “In Queue” popup visible, close the game window (Alt+F4) while keeping the launcher (e.g., Steam) running, wait 1–2 minutes, then relaunch. This isn’t official and won’t help in every case, but it has worked for some.

Note: Fully quitting and re-queuing repeatedly can land you back at square one if the login gate is active again. If you have time, waiting it out is the least disruptive option.

What to expect while the queue is active

  • Matchmaking will be slower. Even after you pass the login gate, the same back-end pressure that triggered the queue can elongate match searches.
  • Party and voice features may be limited. The throttle is specifically aimed at stabilizing party creation and voice channels, so features may behave inconsistently until load drops.
  • Behavior can be spiky. Player counts ebb and flow. Stability often improves off-peak, then tightens again during regional prime time, updates, or content drops.

Common symptoms

Symptom What it indicates What to try now
“In Queue” at game launch with no position or timer Login throttle is active to reduce load on party/voice services Leave the client open to auto-progress; if you prefer, try the light restart (Alt+F4, keep launcher running, relaunch after 1–2 minutes)
Matchmaking stuck on “Searching...” for 5–10 minutes Back-end under heavy demand, slower squad formation Allow a longer search window; if it errors out, re-queue once rather than restarting repeatedly
Returned to lobby after a stall or error Session creation failed mid-flow Queue again and give it time; if it repeats, step away and try off-peak

Will this keep happening?

Expect the login queue to return whenever demand spikes — launch weekends, major patches, or new content drops can all push concurrency high enough to trigger throttling again. These measures are temporary by design and typically ease once traffic normalizes.

If you only have a short window to play, it’s worth trying outside regional prime-time hours until the back-end stabilizes. If you’re already through the gate, stay in the hub between runs to avoid re-entering the login queue.

The immediate takeaway: the “In Queue” message isn’t a bug on your PC; it’s a controlled slowdown while servers catch up to a player surge. Waiting on the screen can work, and a lightweight relaunch may help some, but the most reliable fix is simply time — give it a few hours and try again when the rush has passed.