WARDOGS: "Failed to authenticate with online services"

Two separate faults print almost the same sentence, which is why this error is so badly answered everywhere else. One shows a long numeric code alongside the text — that is error 1147405308, which is a mismatch on your machine only when your build is out of date, and which since launch has also meant the backend refusing players on the current build. The other is the login service turning your session away under load, which carries no code and has no client-side fix at all. The number on screen is the whole diagnosis.

The second one is what most people hit. The Closed Beta peaked above 105,000 concurrent players and the authentication step was the bottleneck: Bulkhead's own answer in the Steam thread was that they were letting in as many players per second as they could. Players who reached the front of the queue were bounced back to five figures by this exact panel, repeatedly, over the course of an hour. That is the same underlying problem as the queue that never moves, seen from the other end.

There is a third case worth ruling out. If you are on Linux or a Steam Deck and the session runs for a few minutes before dropping you with "Authentication timed out (1/3)", that is the Proton fault and it is unrelated — the anti-cheat, not the login service. And if the failure happens before you ever reach a queue, with the anti-cheat refusing to install or log in, start at Anti-Cheat Login Failed instead.

It came back on 10 September, as expected

Early Access opened at 16:00 UTC and this panel was the defining fault of the evening. WARDOGS peaked at 337,157 concurrent players, more than three times the beta, and the pattern was exactly the August one at a larger scale: clear a six-figure queue, hit "Failed to authenticate" at the front of it, and land at the back of a longer one. Players logged 70,000 to 168,000, 90,000 to 280,000, 116,000 to 350,000, several of them more than once in the same evening.

At 20:20 UTC Bulkhead shipped Launch Stability Hotfix #1, which names extended login queue times among the things it addresses. It is a client update: close WARDOGS, reopen it, take the download. Everyone goes back into the queue afterwards by design, and the studio said it would readmit players in controlled batches, widening them as servers filled successfully.

The advice on this page does not change — there is still nothing on your machine to repair — but the restart is now worth doing once, because the build you are queueing on is the one the hotfix replaces. If you clear the queue and then cannot join any server, you have moved on to a different fault: error 1628505091.

The wording changes; the fault does not

The panel is not consistent, and players pasting it into a search box are pasting four different sentences. Failed to authenticate with online services and failed to authenticate with online servers are the same screen. FAILED TO AUTHENTICATE TO SERVERS, in capitals, is what the client printed for the people who sat through a twenty-minute queue in August and got thrown out at the end of it. Failed to connect to online services is the same event described one step earlier. None of them carry a code, and none of them have a fix on your machine.

The one wording that is not this page is anything naming the anti-cheat. If the failure happens before you reach a queue at all, with Easy Anti-Cheat or Elytra in the sentence, the login service never saw you: start at Anti-Cheat Login Failed, or at the anti-cheat refusing the executable if the game will not start at all.