Skip to content
← All errors

Server queue

WARDOGS puts you in a queue that never moves

Published Updated Data as of Season 1 · 10 Sept 2026

This one is not your machine

Server-side, and on launch day it sits in front of the main menu rather than in front of a server — so there is nothing to switch to. Bulkhead shipped a hotfix naming extended queue times at 20:20 UTC on 10 September.

Check whether WARDOGS is down right now →

What you see

You are placed in a login or server queue that stops moving, sometimes with a queue position in the hundreds of thousands.

Also reported as: stuck in queue · login queue · queue error

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 Work out which queue you are in

    Confirmed

    They are not the same fault. During the betas the queue sat in front of a SERVER, so picking another one got you past it. Since Early Access opened, the queue sits in front of the MAIN MENU — players describe waiting at six figures before the game will draw its own interface — and there is nothing to switch to from there. Everything below is split on that line.

  2. 02 Launch queue: restart once to take the hotfix, then wait

    Confirmed

    Launch Stability Hotfix #1 went out at 20:20 UTC on 10 September and names extended login queue times as one of the things it addresses. It is a client update, so it only arrives by closing WARDOGS and reopening it. After that the waiting is the process: Bulkhead said it would readmit players in controlled batches and widen them as servers filled.

  3. 03 Launch queue: do not requeue to escape an error

    Confirmed

    Reaching the front and hitting an authentication failure sends you to the back, and on launch evening the back was a much longer queue than the one you joined — players logged 70,000 to 168,000, 90,000 to 280,000, 116,000 to 350,000. That is the fault described on the authentication page rather than this one, and quitting to dodge it costs you the position you already paid for.

  4. 04 Server queue: join a different server

    Confirmed

    The beta-era workaround, and it still applies to a queue in front of a single server. It is not a fix, but it gets you into a match.

  5. 05 Server queue: try a neighbouring region

    Confirmed

    The fault clustered on EU Central during the beta while EU East stayed healthy. This is a property of a per-server queue, and it does nothing for a login queue that has not drawn the menu yet.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

Nothing on your machine causes this and nothing on your machine will fix it. Verifying game files, reinstalling and resetting your network are all wasted effort here, which is the reason this page exists separately from the crash pages.

The scale is worth understanding. The Closed Beta peaked at 105,774 concurrent players and the login queue was, in Bulkhead's own words, getting hammered — an issue they said did not appear during the Closed Alpha purely because the volume of logins was lower. A fix was said to be in progress ahead of Early Access.

What happened on 10 September

It did not hold. WARDOGS peaked at 337,157 concurrent players on launch day, more than three times the beta figure, and the queue behaved differently at that size: it moved in front of the main menu. Players were waiting at 40,000, then 100,000, then 250,000 and past 350,000 before the game would draw its own interface, which is why the beta advice to pick a quieter server does not reach the launch version of this fault — you cannot see a server list to pick from.

Bulkhead cleared the queue outright at one point during the evening to restart the login service, kicking everyone waiting in it, and its CEO pointed publicly at Steam's capacity allocation for the game as part of why the queue ran as long as it did.

At 20:20 UTC the studio shipped Launch Stability Hotfix #1, which lists extended login queue times among the things it addresses, alongside players unable to join servers and players being kicked mid-match. It forces every logged-in player to restart and collect a client update, and puts everyone back into the queue afterwards by design, with access reopened in controlled batches. The studio said it would be working through the night.

In the two hours after the hotfix the queue did something the betas never did: it went backwards. Players reported dropping five thousand places in ten minutes, sitting on the same number for a quarter of an hour, and reaching 290,000 having already cleared the queue once that evening. That is what batched readmission looks like from inside a queue position, and it is not your client. Restarting to fix it puts you at the back for certain.

Two related faults are worth separating from this one. If you reach the front and get thrown back by an "Access Denied" panel, that is failed to authenticate. If you clear the queue and then cannot join any server, that is error 1628505091.

Source

WARDOGS Launch Stability Hotfix #1, Steam, 10 September 2026 ↗

If that did not do it