“Failed to authenticate with online services”

Three numbers, and they are not interchangeable

The authentication codes get quoted as one problem and they describe two different stages. 1147405308 and 1147405309 are reported as the login itself being refused — access denied, invalid game version, failed authentication. 1628505085 is reported as “Failed to initialise player session with online services”, which is a later stage: the login succeeded and the session did not. Knowing which one you have is the difference between waiting and looking at your install.

What the dates say

The plain-text string “Failed to authenticate with online services” has a Steam thread opened 24 August 2026, during the closed beta, with two replies and no fix — one of which points out it was a beta weekend. 1147405308 appears in the 21 August queue thread, reported by a player after the queue cleared. Both predate Early Access. That does not mean the launch build cannot produce them; it means the string is older than the paid game and a launch-only explanation does not fit the record.

1628505085 is the thinnest-evidenced string on the site

Exactly one public source documents it, and that source is a ping-booster vendor's error table whose first recommended step for the login codes is its own paid product. It is named here because a gap in the family is more confusing than a thin entry in it — but one source with a commercial interest is what the evidence amounts to, and even that source's own advice for this code is a caution rather than a remedy: do not reinstall before checking server and login status. That is consistent with the rest of the family and it is as far as the record goes.

Check whether it is you before you change anything

An authentication failure that is actually a server-side refusal looks identical from your machine to one caused by your install, and the second is the one that tempts you to reinstall. The cheap check is whether other people are reporting it at the same time. BULKHEAD's own account of launch day describes exactly this class of failure being server-side — expired Steam login tickets, not player installs — which is the strongest available argument for checking before touching anything.

What BULKHEAD said the login failures were →

“ACCESS DENIED” is two different screens, one digit apart

ACCESS DENIED is what the client actually prints, and the number under it decides whether you are waiting or appealing. Four dated threads print it above 1147405308 — the authentication failure this page is about, where the servers would not complete your login. Five more, all on the Ban Appeals board, print the same two words above 1147405307 with a stated reason of Cheating and a duration of Permanent. Read the last digit before you do anything: one of these is a connection problem and the other is an account decision, and no amount of verifying your install touches the second.

What the 1147405307 reports do and do not establish

Five ban appeals between 17 and 20 September 2026 name the code in their titles or opening posts, which establishes that the string exists, that it carries a cheating reason and a permanent duration, and that it was being served in that window. It establishes nothing else. Every one of those posts is a player saying the ban is wrong, and this site takes no position on any individual appeal. No BULKHEAD or Team17 text checked for this page names 1147405307, explains what triggers it, or documents an appeals route, so what the detection is and how long a review takes are not established here. If you have this code, the appeal board is where the reports go; nothing on this page is a way around it.

What is actually disclosed about the anti-cheat →

Common questions