Error code 1147405308 means the client failed to authenticate with WARDOGS online services. More precisely, the authentication server did not process your login request — even when your access is completely valid.
It is usually a server-side problem, not something wrong with your machine. Reinstalling the game will not fix it, and during high-load periods the correct response is often to wait rather than to troubleshoot.
AI concept artWhat the error actually means
The accompanying message is typically “Failed to authenticate with online services”, and some players see it presented as Access Denied. Both describe the same failure.
The important nuance is that this is not an entitlement check failing. Your account can have perfectly valid access and still hit this code, because the failure is in the authentication service processing the request rather than in the answer it would have given.
That is why the error feels so arbitrary — nothing about your account or install has changed between the attempt that worked and the one that did not.
Why it happens
The dominant cause is load. Login queues buckle when concurrency far exceeds what the authentication system was provisioned for, creating a bottleneck at exactly the moment the most people are trying to get in.
This is consistent with when players encountered it: test windows opening, launch day, and other moments of coordinated mass login. Recent player reports point at server queues and connection handling rather than local configuration.
A game that peaked above 219,000 concurrent players during a playtest is exactly the kind of title where login infrastructure becomes the constraint.
First: work out whose problem it is
This single question determines whether you should act or wait, and getting it wrong wastes a lot of time.
Check the official Steam Community Hub announcements before doing anything else. If the developer has acknowledged a service incident, there is nothing on your end to fix.
Another useful signal is whether other players are reporting the same code at the same moment. A widespread simultaneous failure is a server incident by definition.
If it is server-side
Wait. Service is restored when the operator fixes it, and your client will connect normally once it is.
Do not reinstall. A 50GB download cannot repair an authentication service running on someone else’s infrastructure, and you will still be facing the same error afterwards.
Retrying periodically is reasonable, but hammering the login button during a queue backlog contributes to the congestion causing the problem.
Reinstalling the game is the most common wasted effort with this error. It fixes nothing when the cause is server-side.
If it is local
Restart Steam completely, then relaunch. A stale Steam session is the most common local contributor and the cheapest thing to rule out.
Confirm you actually hold the access you are trying to use. During the beta period this mattered a great deal, because players without a selected Request Access invitation could not authenticate into a test build.
Verify the game files through Steam, and check your own network — a VPN, a restrictive firewall or an unstable connection can all interrupt the authentication handshake.
AI concept artWhen anti-cheat is the real culprit
There is a mirror-image mistake to reinstalling unnecessarily: waiting for servers to recover when your Easy Anti-Cheat installation is actually broken. In that case nothing improves no matter how long you wait.
The distinguishing signal is consistency. A server incident affects everyone at once and then resolves; a broken anti-cheat installation fails for you specifically and keeps failing.
The repair is to delete the EasyAntiCheat folder from the game directory and use Steam’s verify integrity option to restore it.
Related error codes
Adjacent codes such as 1147405309 and 1147405316 belong to the same family, covering the online services and authentication chain. Codes like 1628505085 have also been catalogued alongside them.
If you are switching between codes in this range across attempts, that pattern is itself evidence of a service-side problem rather than several unrelated local faults.
Errors such as 0xc0000142 and “missing game executable” are a different category. Those are Windows-level or installation problems and should be handled as launch failures rather than authentication ones.
Quick reference
In order, this is the shortest path from the error to a resolution.
- 1 — Check the official Steam announcements for an acknowledged service incident.
- 2 — If acknowledged, wait — do not reinstall.
- 3 — If not, fully restart Steam and try again.
- 4 — Confirm your account actually has access to the build you are launching.
- 5 — Verify game files through Steam.
- 6 — Repair Easy Anti-Cheat if the failure persists only for you.
- 7 — Check your network, disabling any VPN before retrying.
Why this error was so common
The context explains the frequency. The playtest peaked at 219,762 concurrent players, and test windows open at a scheduled moment, so a very large number of people attempt to log in within the same few minutes.
Authentication is the narrowest point in that sequence. Every client must clear it before doing anything else, which makes it the first system to buckle when concurrency spikes.
This is also why the error clustered around specific times rather than appearing randomly. If you hit it at the exact moment a test window opened, you were almost certainly queuing behind everyone else.
What the message does not mean
It does not mean your account lacks access. The error can appear on an account with entirely valid entitlement, because the failure is in processing the request rather than in the verdict.
It does not mean your installation is corrupt. That is a different failure mode which presents as a launch crash rather than an authentication code.
It does not mean you have been banned or blocked, despite the Access Denied wording some players see. That phrasing describes the failed handshake, not a moderation action.
Error code questions answered
Short answers for the variations that bring people to this page.
- What does 1147405308 mean? — Authentication with online services failed.
- Is it my fault? — Usually not. It is most often a server-side capacity problem.
- Should I reinstall? — No. Reinstalling cannot fix a server-side authentication failure.
- Is 1147405309 the same problem? — It belongs to the same online services and authentication family.
- What about 0xc0000142? — Different category — that is a Windows-level launch problem.
- How long until it works? — When the service recovers. Check the official announcements for incident status.