WARDOGS server status: is it down?

Three different things get reported as "WARDOGS is down", and only one of them is an outage. They look different on the chart above, which is the fastest way to tell them apart.

Is WARDOGS down for maintenance today?

The first announced window is Monday 14 September 2026 at 08:00 UTC, for approximately one hour, to deliver Patch 0.11. That is 01:00 in Los Angeles, 04:00 in New York, 09:00 in London, 10:00 in Berlin and 18:00 in Sydney. Bulkhead publishes no status endpoint, so the Steam news hub and @WARDOGS on X are where a window shows up first.

Scheduled maintenance reads differently here from a failure. Reports climb steadily and stay level for as long as the window lasts, because everyone hits the same wall at the same time and keeps hitting it. A real outage spikes hard in one hour and then decays. Anything announced in advance is mirrored into the news timeline with a timestamp.

A login queue is not an outage

WARDOGS queues players at the login step rather than turning them away, and on launch night that queue was the whole story. It reads on the chart above as matchmaking reports climbing while server-connection reports stay low, and on Steam as a player count that goes flat instead of dropping: the servers are up and full. Waiting is the only fix. Reinstalling, verifying files and restarting your router do nothing to a queue.

Queues on the first weekend of a paid Early Access launch are ordinary. ARC Raiders peaked at 481,966 concurrent players sixteen days after release; capacity is the thing that gives way first when a launch goes well.

How long is the WARDOGS queue right now?

For most players, there is no longer one. Bulkhead posted that the queue issues should have passed as of 00:00 UTC on 11 September 2026, the morning after launch. Launch night itself is the high-water mark to measure against: Early Access opened at 16:00 UTC on the 10th, positions in the hundreds of thousands were normal all evening, and by 23:00 UTC the studio counted 135,000 players through the queue and in game — still admitting people in waves while it watched the servers hold.

A queue that is counting down is working, however slowly it does it. What is not ordinary is a position that has not moved in fifteen minutes, one that jumps backwards, or a server-full panel at the front of it. Those are three different faults and the queue page tells them apart.

Do not restart the game to get through the queue faster

Closing the client and reopening it puts you at the back, not the front. Bulkhead's own wording for the launch hotfix was that everyone in game would be logged out and, on booting back in, put into the server queue: the place is held server-side and it does not survive the client. The one time restarting is the right move is when the game has already thrown you out with failed to authenticate with online services, because at that point you are not in the queue at all.

When a failure to connect is worth reporting

Early Access opened at 16:00 UTC on 10 September 2026, so there is a live service to be down and "cannot connect" is now worth reporting rather than expected. The hours after a patch are when a tracker like this one earns its keep — queues, capacity limits and server restarts all land at once, and the first sign of each is a wave of reports rather than an announcement. What the two Closed Betas were covers what came before.

The queue was the one system Bulkhead said Closed Beta 02 existed to break, and it broke again at launch scale: a peak of 340,171 concurrent players is more than three times what the beta tested it against. That is the pattern to expect from the next content patch too — the first hour is a capacity test, not an outage.

Every code and crash we have a fix for has its own page under errors and crashes, one URL per thing you can paste out of a dialog box. The one most people are holding is 1147405308, which reads as access denied and has three separate causes behind it, only one of them on your machine; the screen that says failed to authenticate with online services and carries no code is a different fault, and a server-side one.

If what you would type is a sentence rather than a code — cannot join a server — then five faults answer to it and they have five different fixes. The triage page asks the one question that separates them: how far did you get, the browser, the click, the loading screen, or the match itself. And if the game never opens a window at all, that is the launcher rather than a crash: the WD-L codes are the ones that stop it before it starts.

Below is the alpha-era record from 7–9 August 2026, kept separate because those faults are not the beta's.

WARDOGS error 1147405300

Thrown when joining a server, not when starting the game: the client is up and the connection attempt is what fails. Both players who reported it during the alpha also described being placed in the wrong region — one in the EU queued into a North American server — which points at matchmaking rather than at the machine it happens on.

It is worth knowing how thin that is. The whole public record is a single thread from 7 August, and this tracker has counted 126 reports naming a 1147405xxx code since — across both closed betas — without one of them being this number. The page for 1147405300 sets out what the two reports said and grades the circulating fix accordingly. If your code starts 1147405 and ends differently, it is one of the three that players are actually hitting: 1147405308, a version mismatch printed as access denied; 1147405309, the servers refusing the login rather than failing it; or 1147405316, a server queue that is full.

WARDOGS crashes on launch

The most reported alpha fault, and the only one a developer has spoken to publicly. A Bulkhead staff account replied in the community thread to say they are tracking the issue ↗, and it has not been fixed in a published patch. The sequence players report working — the EasyAntiCheat folder, %LOCALAPPDATA%\Wardogs, the reboot most people skip, then verifying files — is written out in order, with what to do when it fails, on the crash on launch page.

If you are on a VPN, turn it off first

One alpha player worked through verifying files and a full reinstall before finding the cause was a VPN left running. It costs nothing to rule out and it is the single most common self-inflicted connection failure in this genre.

Most "is it down" moments are not outages. Work down this list before assuming the servers are the problem — it is ordered by how often each one turns out to be the answer, not by how easy it is.

Check the report count above first

It costs nothing and it settles the question. A flat count and a normal player number means thousands of people are playing fine, and everything below is worth your time. A spike means it is not you and none of it is.

Verify the game files

In Steam, right-click WARDOGS → Properties → Installed Files → Verify integrity. A partial patch is the single most common cause of a game that launches and then fails to connect, and it is invisible otherwise. This is also the first thing support will ask.

Restart the whole chain, in order

Game, then Steam, then router. People almost always do the first and skip the third, and a stale NAT table on a router that has been up for six weeks produces exactly the symptom people report as "servers down" — the client connects, then times out joining a match.

If you see "connection to server lost"

That wording matters. It means the client reached a server and then lost it, rather than never reaching one — so the network path works and something further along broke. Verify the files, then restart the chain below. If the report count above is climbing at the same time, stop: it is the servers, and nothing local will fix it.

Rule out the obvious network causes

A VPN will fail matchmaking far more often than it fixes it. So will a strict NAT type, and so will a corporate or campus network that blocks the UDP ports a game server needs. If you are on a network you do not administer, that is the likely answer.

Then treat it as a crash, not an outage

If the game starts and dies rather than failing to connect, the cause is local and usually graphics drivers or overlay software. WARDOGS is running 100 players on a destructible map, which is the hardest case for an unstable overclock — and a machine that is stable everywhere else can still fail here.

There is no official WARDOGS status page. Bulkhead has not published one, and neither has any studio in this genre — Embark has not for ARC Raiders either, which is the reason third-party trackers exist at all. When something is genuinely broken, it is announced in one of two places and nowhere else:

• The WARDOGS Steam news hub ↗ — where maintenance and patches are posted, and the only channel that is archived.
• @WARDOGS on X ↗ — faster during an incident, but posts scroll away and are not a record.

We mirror anything that lands in either into the news timeline with a source link and a timestamp, so an announcement that has scrolled off X is still findable a month later.