Four wordings, none of them official
This is the only string in this section where the sources disagree about what the message says, and that disagreement is worth more to a reader than any of the individual wordings. If you searched the number and found a page whose title does not match your screen, this is why: nobody is quoting the client, because nobody has published what the client says. Every row below is somebody's report, and BULKHEAD and Team17 have printed none of it.
| Wording | Where it was published | When |
|---|---|---|
| “The timeout period has expired.” | Steam thread opened with the code as its title | 10 Sep 2026, 12:48 PDT |
| “Join Timeout” | Steam thread title, four minutes later | 10 Sep 2026, 12:52 PDT |
| “Can't connect on time” | Steam thread listing three codes together | 10 Sep 2026, 11:25 PDT |
| “Failed to connect to the server in a reasonable amount of time” | Third-party fix videos, not cited here | c. 11 Sep 2026 |
Twenty people inside four minutes, which is the one thing the record does establish
At 12:48:43 PDT on launch day a player posted a single sentence — “The timeout period has expired. Error 1628505091.” The first reply arrives at 12:49:01, eighteen seconds later. Twenty replies follow in roughly four minutes and almost all of them are one word: same, same here, yep, me too. That pattern does not tell you what the error is. It tells you what it is not: whatever was happening at 12:48 PDT on 10 September 2026 was not happening to one machine's install. A failure that reproduces for twenty strangers simultaneously is a server-side event, and this is the one page in this section whose evidence establishes that much on its own rather than by inference.
- String: “The timeout period has expired.”, per the thread's opening post
- First dated public report: 10 September 2026, 12:48:43 PDT
- 20 replies in roughly four minutes, first at 12:49:01
- Cause: not published by anyone
Not the launch queue, and not 1147405316
Three connection failures from the same week get merged constantly. The launch queue is the admission line before the servers — “You are in the queue to join WARDOGS” — and it is the one BULKHEAD explained itself. 1147405316 is a specific server refusing a join with “Server queue is full”, reported against a listing showing 43 of 100 players. 1628505091 is a timeout: nothing refused you and nothing admitted you either, and one of the two reports describes it happening after the join as well, as an immediate kick. If your client is counting down a queue position, that is the first page. If a server said no, it is the second. If nothing said anything and the attempt simply expired, you are on the right one.
What nobody has published, and what this page will not borrow
No BULKHEAD or Team17 text checked for this section prints a numeric WARDOGS error code, and this one is no exception. LagoFast's table — the fullest public third-party list, and the one most other sites are working from — covers 1147405308, 1147405309 and 1628505085 and does not carry 1628505091. The fourth wording in the table above comes from fix videos published in the days after launch; they are named there for completeness and they are deliberately not cited as sources, because a channel that titles a video with an error string has demonstrated that people are searching for it and nothing else. There is no official cause, no official fix, and no numbered step list here, because there is nothing to print that would not be invented.
Common questions
What is WARDOGS error 1628505091?
A connection timeout reported on launch day, 10 September 2026. The thread that names it verbatim gives the message as “The timeout period has expired.” Other reports call the same code “Join Timeout” and “Can't connect on time”. No official BULKHEAD or Team17 text mentions the code, so what it means beyond a timeout is not established.
How do you fix WARDOGS error 1628505091?
Nobody has published a fix and this page will not invent one. What the record does show is that twenty players hit it within about four minutes of each other on launch day, which is the signature of a server-side event rather than anything on your machine — so checking whether other people are reporting it right now is worth more than changing your install.
Why does every site give a different message for 1628505091?
Because nobody is quoting the client. Four different wordings have been published — “The timeout period has expired.”, “Join Timeout”, “Can't connect on time” and a longer sentence used in fix-video titles — and all four are reports rather than a screenshot or an official string.
Is 1628505091 the same as the WARDOGS launch queue?
No. The launch queue is the admission line between Steam and the servers, and BULKHEAD explained it in a launch recap. 1628505091 is a timeout at or just after the join, and no official text mentions it.
Sources & verification
Each source below carries its own read date and its own boundary note. A Steam thread establishes that a string exists and when it was first reported; it does not establish a cause.
| Source | Type | Read |
|---|---|---|
| Steam · “Error 1628505091”, WARDOGS discussions, 10 September 2026Opened 12:48:43 PDT on launch day. The opening post is one sentence — “The timeout period has expired. Error 1628505091.” — and the first reply lands at 12:49:01, eighteen seconds later. Twenty replies follow, almost all of them one word, inside roughly four minutes. Cited for two things and no more: the verbatim wording, and the fact that it reproduced for twenty strangers simultaneously. It says nothing about why. | Unverified | 2026-09-18 |
| Steam · “Error “1628505091” Join Timeout”, WARDOGS discussions, 10 September 2026Opened 12:52:57 PDT, four minutes after the thread above, and titled with a different name for the same code: “Join Timeout”. Body: “keep on getting this error everytime I try to join a server or I get kicked as soon as i join.” Cited because the disagreement between the two titles is the thing this page is about, and because it adds the detail that the failure was also happening after a join, not only instead of one. | Unverified | 2026-09-18 |
| Steam · “Error Codes??”, WARDOGS discussions, 10 September 2026Opened 11:25:58 PDT on launch day. The opening post is the only dated public text found that pairs 1147405316 with words: “Server queue is full, with 43/100 players(1147405316). Can't connect on time(1628505091). Failed to join(1147405300).” It establishes that the string existed on 10 September and what a player read on screen. It establishes nothing about the cause, and the wording is one player's transcription rather than a screenshot of the client. | Unverified | 2026-09-18 |
| BULKHEAD · “WARDOGS | Launch Day Recap”, 11 September 2026Published 22:30:21 UTC. BULKHEAD says Hotfix #1 renewed expired Steam login tickets at the front of the queue, admission proceeded in 10,000-player waves, the launch queue reached zero, and sales reached 1.5 million. This is a dated launch recap, not a live server-health reading. | Publisher stated | 2026-09-12 |
| LagoFast · “All WARDOGS Error Codes: How to Fix 1147405308, 1147405309, 1628505085, and More”, updated 26 August 2026The fullest public WARDOGS error table, and the one whose interests need declaring twice. It is published by a ping-booster vendor whose recommended first step for the login codes is its own paid product; it is dated to the closed-beta window rather than the shipping build; and it attributes three rows — 0xc0000142, 0xc000007b and the shader crash — to Easy Anti-Cheat, prescribing “Repair EAC”. Steam’s listing names Elytra. It is the only public source for 1628505085. | Unverified | 2026-09-13 |