WARDOGS server status: what is published, and what to try

A helicopter flying low over forested hills toward a tower on a ridge
Screenshot: WARDOGS, via its Steam store page. © BULKHEAD / Team17.

Status right now

The newest notice BULKHEAD has published is "WARDOGS | SEASON 02 IS NOW LIVE", posted October 15, 2026. It says: "We have now released Update 0.2.0. Servers are back online." Nothing newer has been posted to the official Steam news feed, which was read in full on October 27, 2026.

BULKHEAD has not published a live status page, and the official site wardogs.com has no status section, so this page cannot tell you whether the servers are up at this minute. It can only tell you the last thing BULKHEAD itself published, and how to check for anything newer.

Three things to try before anything else.

  1. Read today's notice on the Steam news hub.

    Open the WARDOGS Steam news hub and look at the newest post. If it announces a maintenance window and you are inside the hours it names, the servers are offline on purpose — wait it out. If the newest post is still the October 15 notice above, no newer outage has been announced.

  2. Restart the game so it can download a client update.

    Launch Stability Hotfix #1 (September 10, 2026) needed the game to be restarted before the client update would download. Quit WARDOGS completely, reopen it, and let Steam finish any pending download before you try to join again.

  3. Verify your game files in Steam.

    Verify Integrity of Game Files is Steam's own repair tool for damaged or missing files. In Steam, go to Library → right-click WARDOGS → Properties → Installed Files → Verify integrity of game files, and let it finish before launching.

Still stuck after those three? The sections below split the problem by what you actually see — a maintenance notice, a join that fails, a queue that says it is full, an error code, or a server list with nothing in it. Find the one that matches and stop there.

Where to check the status yourself

BULKHEAD posts its announcements, including every maintenance window below, on the WARDOGS Steam news hub. That hub is the only place this page could verify. The official site, wardogs.com, was checked on October 27, 2026 and has no status page, no announcements section and no support link, so it cannot tell you whether the servers are down.

Read the hub itself rather than a repost of it. A copied notice keeps yesterday's wording after BULKHEAD has already posted that the servers are back; the hub shows the newest post first, so the top one is the current word.

Maintenance windows

BULKHEAD has not published a standing maintenance schedule. What it has published are four windows, each tied to one specific deployment. During an announced window the servers are offline on purpose, so a failed connection inside those hours is the maintenance itself and not a fault with your game or your connection. The wording below is copied from the announcements.

DeploymentWhat BULKHEAD wroteAnnounced
Patch 0.11 "We will be taking the servers down temporarily on Monday September 14th for approximately 1 hour" — listed in the post's own table as Monday 08:00 UTC. September 12, 2026
Update 0.1.2 "WARDOGS will be entering a maintenance window today at 8:00 UTC, estimated to last 1 hour. Services will be offline while we deploy update 0.1.2." September 30, 2026
Security & Stability Hotfix "A hotfix is planned for tomorrow, Friday 2nd, at 08:00 UTC … Expected downtime is one hour." October 2, 2026
Season 02 (Update 0.2.0) "There will be a scheduled maintenance window on October 15th between 08:00 and 09:30 UTC. We estimate roughly 90 minutes of downtime before the new season goes live." October 14, 2026

The October 15 window is the most recent, and the notice posted once it ended says "Servers are back online." Whether another window is happening today is not something this page can know — that is what the Steam news hub is for.

Can't join a server, or "failed to join"

"Can't join" and "failed to join" are the same complaint: you picked a server and never got in. At launch this was a known, widespread problem — not being able to join servers, being kicked mid-match, and long login queues were what Launch Stability Hotfix #1 (September 10, 2026) was intended to address. BULKHEAD's own word was "intended to address", and the fix only arrived after restarting the game to download the client update. Work through the three checks in order.

  1. Is a maintenance window open? Check the Steam news hub first. Passed: the newest post does not name a window covering right now. Failed: it does — you are in the "Services will be offline" case, and nothing on your end will connect until it ends.
  2. Did the join actually start? Since Update 0.1.2 (September 30, 2026), clicking Join shows that you are connecting and then your place in the queue if there is one. Passed: you see "connecting" or a queue position, which means the server accepted the attempt. Failed: you see neither and land straight back where you started — restart the game so any pending client update downloads, then try again.
  3. Are you in the right list? Hit DEPLOY and the game offers four lists: Official, Community, Infantry Mode and Low-Level. Passed: the server you wanted is in the list you opened. Failed: it is not — it is in one of the other three, and the list you are staring at will never show it.

If all three pass and you still cannot get in, you are into something BULKHEAD has not documented. The two error codes players actually report are covered further down this page.

"Server queue is full"

Not stated by BULKHEAD. No announcement in the official Steam news feed, read in full on October 27, 2026, explains what "server queue is full" means or what a player should do when a server reports it. This page will not invent a meaning for it.

What BULKHEAD has said about queues is limited to two statements from the launch period, and neither is a standing rule:

  • The official @WARDOGS account posted: "We are continuing to let players through the queue in waves. We are being cautious to ensure server stability."
  • Community Manager LOSSY wrote, in the official WARDOGS Discord and quoted here via BisectHosting: "We are currently seeing thousands of players in the login queue, slowly filtering into the game and into servers as they scale. However - Some players are being put to the back of the queue - sincere apologies for this. The response is much, much larger than the Beta. Please hang tight whilst we resolve these issues."

Both describe BULKHEAD letting players in gradually while servers caught up. Neither says that a full queue clears on its own, or that switching servers avoids it. The only related behaviour the patch notes document is from Update 0.1.2: after you click Join, the game shows that you are connecting and then your place in the queue if there is one — so a queue position on screen means you are in line, not rejected.

The two error codes players ask about

Both codes below are player-reported. No BULKHEAD announcement mentions either number — the official Steam news feed was read in full on October 27, 2026 — so the official explanation of each is: not stated by BULKHEAD. What follows is the message the game shows and where players say they see it.

1628505091

Official explanation: not stated by BULKHEAD. What players report: the game shows "JOIN TIMED OUT — ERROR CODE: 1628505091 — Failed to connect to the server in a reasonable time." It appears after you select a server and the join does not finish in time, and players have reported getting it on every attempt to join (one report in the "NO SERVERS?" discussion thread, September 10, 2026). What to do: nothing officially documented. The three checks at the top of this page — the news hub, a full restart, verifying the game files — are the only steps backed by official sources, and none of them names this code.

1147405308

Official explanation: not stated by BULKHEAD. The code number appears in no official post. What players report: the game shows "ACCESS DENIED — ERROR CODE: 1147405308 — Failed to authenticate with online services." It was widely reported at the Early Access launch on September 10, 2026, including by players who had waited through the login queue, reached the front, and were sent back. What to do: nothing officially documented for the code itself. What BULKHEAD did say that day, through Community Manager LOSSY, is quoted in the queue section above: thousands of players were in the login queue and some were being moved to the back of it while the servers scaled.

Servers not showing up

An empty server list has happened in two documented ways, and they are different problems.

Before the servers are live. On August 21 a player asked "why is the server browser just empty?" and developer KingHoward answered: "17:00 UTC Servers go live." An empty browser before the stated go-live time meant exactly that — there was nothing to list yet. The same logic applies to a maintenance window: while services are offline there are no servers to show.

After launch, with the servers supposedly up. Players have reported the official server browser showing no servers at all, regardless of which region is selected (the Steam discussion "BUG REPORT: Official Server Browser Completely Empty"). No official cause and no official fix has been posted for that report, so this page will not supply one. The one official behaviour worth knowing is that the browser is split into lists: since Update 0.1.2, DEPLOY offers Official, Community, Infantry Mode and Low-Level separately, so a server can be absent from the list you have open while present in another.

When it is not a crash, and when it is not maintenance

Two mix-ups account for most of the wrong fixes.

Maintenance is not a crash. If the Steam news hub shows a maintenance window covering the current time, the servers are offline because BULKHEAD said they would be — "Services will be offline while we deploy" is the exact phrasing from the Update 0.1.2 notice. Verifying files or reinstalling changes nothing while that window is open, and the connection comes back when the window ends, as it did on October 15 when the follow-up notice said "Servers are back online."

A failed join is not maintenance either. Outside an announced window, "can't join", "failed to join" and a long queue are connection problems, not downtime. At launch those were widespread enough that Launch Stability Hotfix #1 was shipped the same day specifically to address them. One more case that looks like a connection fault but is a rule: since Season 02 went live on October 15, 2026, official servers enforce a maximum ping per region, and "players who consistently exceed a server's ping limit over a sustained period will be automatically kicked" — then "unable to rejoin the same server until the next map transition." The patch notes give no number for that ping limit.

Crashes proper — WD-L020, a crash at startup, a freeze mid-session — are a different subject, handled on the WARDOGS help page.

Related pages

  • WARDOGS game overview — what the game is, how a match works, and where the servers, cash economy and factions fit in.
  • WARDOGS help section — the WD-L020 crash on Windows 11, launch-day crashes, and which reported errors still have no official fix.
  • WARDOGS updates & release — when the PC version launched, the full list of official updates since, and the 2028 window for PS5 and Xbox.

Sources

Official (BULKHEAD / Team17 / Steam)

Player reports (not official fixes)

Last checked against BULKHEAD's Steam announcements on October 27, 2026. This page is updated when a newer official announcement changes the status, the maintenance windows, or either error code.