Error code 1628505091 is the join timeout. It appears as "Join Timed Out", usually with wording about WARDOGS having failed to connect to the server in a reasonable time, and it means your client asked to enter a server and did not get in before the attempt expired.
It is a capacity failure at the moment of joining, not a fault in your installation or your network. BULKHEAD listed "players unable to join servers" as one of the three problems targeted by Launch Stability Hotfix #1 on 10 September 2026, which places this code on the service side alongside the login queue and the mid-match removals.
The three names for one error
This single failure reaches people under several different phrasings, which is why it can look like several separate bugs. The numeric code, the on-screen heading and the explanatory sentence are all describing the same event.
If you searched any of these and landed here, you are in the right place. There is no separate "reasonable time" fault to diagnose apart from the join timeout.
| What you saw | What it is |
|---|---|
| Error code 1628505091 | The numeric identifier for the join timeout |
| Join Timed Out | The on-screen heading for the same event |
| Failed to connect to the server in a reasonable time | The explanatory line shown with it |
| Failed to join | A shorter variant of the same message |
Why a server with free slots still refuses you
The most confusing part of this error is hitting it against a server that openly advertises space — a browser entry reading 50/100 will still time you out. That looks like a lie, but it is a timing artefact rather than a wrong number.
The slot count in the browser is a snapshot. Between that snapshot being drawn and your client completing its handshake, the server is working through everyone else who asked at the same moment. At launch scale the remaining slots were consumed inside that window, so the figure you clicked was simply stale by the time you arrived.
This is the mechanism players on the official discussions converged on independently: the queue releases more people toward a server than the server can admit in the time your client is willing to wait. Nothing about your machine changes the outcome.
A free slot in the browser is a snapshot from a moment ago, not a reservation. It cannot be held for you while you connect.
What BULKHEAD has actually confirmed
Launch Stability Hotfix #1, posted to the official Steam announcements on 10 September 2026, names three symptoms together: players unable to join servers, players being unexpectedly kicked from servers during play, and extended login queue times. Grouping them in one announcement signals a shared cause on the service side rather than three unrelated faults.
That hotfix was a forced client update, so applying it pushed everyone back through the login queue — which is why a wave of join timeouts followed the patch itself rather than preceding it. Players were then readmitted in controlled batches.
The follow-up is Patch 0.11, announced for scheduled maintenance on 14 September 2026, with roughly an hour of downtime. BULKHEAD states plainly that "Community Servers have been underserved and the server browser experience as a whole has been poor", and the patch targets server browser and community server discoverability — the same surface where this error is felt.
What actually helps, and what does not
There is no local repair for a capacity failure, so the useful actions are about picking a better moment rather than changing your setup. The list below separates the two.
- Retry promptly — Attempts are cheap and slot availability turns over constantly. Repeated attempts are the single most effective response.
- Pick a less contested server — Avoid the fullest entries in the browser. A server at moderate occupancy has a wider admission window than one near its cap.
- Avoid regional prime time — US and EU evening hours are when the capacity ceiling is lowest. The same join succeeds readily outside them.
- Check whether others are affected — If the official discussions are busy with the same code at the same moment, it is an incident and waiting is correct.
- Do not reinstall — Reinstalling cannot change a server-side admission decision, and it costs you the time in which a slot might have opened.
- Do not verify files for this code — File integrity is unrelated to a join timeout. Reserve that step for launch failures and crashes.
Telling this apart from the other launch errors
WARDOGS produced four distinct launch-period failures that people frequently mistake for one another. The stage at which each one stops you is the reliable way to tell them apart.
If you never reached a server list, you have an authentication or queue problem. If you reached the list and could not enter, this is your page. If you were already playing and got thrown out, it is the removal fault.
| Where it stops you | Which fault it is |
|---|---|
| At login, with a wait and a position | The login queue |
| At login, with code 1147405308 | Failed to authenticate with online services |
| At the server browser, with code 1628505091 | This join timeout |
| Mid-match, after you were already playing | Removed from the match |
Why launch produced this at scale
The context is the volume. BULKHEAD announced 1.25 million copies sold on 10 September 2026, the same day Early Access opened, and every one of those buyers attempted to reach a server inside the same few hours.
Joining is a narrow step by design. Authentication has a queue in front of it that can absorb pressure, but server admission has no equivalent buffer — you either get a slot or your attempt expires. That makes the join the first place a concurrency spike becomes visible to players.
It also explains why the error clusters rather than appearing randomly. If you hit it, you hit it alongside a very large number of people at that exact moment.
Join timeout questions answered
Short answers for the variations that bring people to this page.
- What does error 1628505091 mean? — Your request to join a server timed out before the server admitted you.
- Is "join timed out" the same error? — Yes. It is the on-screen heading for code 1628505091.
- Is it my internet connection? — Usually not. It is a capacity failure at the server, and it affects many players at once.
- Why did it fail on a server showing free slots? — The slot count is a snapshot. Those slots were taken while your client was connecting.
- Should I reinstall or verify my files? — No. Neither can change a server-side admission decision.
- Is this the same as 1147405308? — No. That one stops you at authentication, before you reach a server list.
- What actually works? — Retrying, choosing a less crowded server, and avoiding regional prime time.