Skip to content
A grimy CRT monitor on a scavenged desk showing a red 404 and a severed cable icon, beside a field telephone and a router with lit indicators, overlooking a ruined industrial skyline at sunset.

Live

WARDOGS server status: is it down?

Possible problems

3 players have reported a problem in the last 15 minutes — more than a normal quiet period, but short of an outage. Worth checking back.

Checked 12:48 UTC · this page is rendered fresh on every load

Is it broken for you? Tap what is failing

One tap. No account, no email. Reports are the only thing that tells the next player whether it is their connection or the servers — including when that player is you tomorrow.

Reporting needs JavaScript.

We store the category and the time. We do not store your IP address — it is hashed with a secret and today's date purely to stop one person filing fifty reports, and the hash cannot be reversed or matched to you tomorrow.

While you're here:Patch notes →Season 2 →Does Season 2 wipe progress? →Tier list →Error codes →

WARDOGS is live in Early Access

Early Access opened at 16:00 UTC on 10 September 2026, so there is a real service to be down and "cannot connect" is now worth reporting. In the first hours a queue, a capacity limit or a first-day patch is more likely than an outage — the reports below and the Steam count tell you which, and whether it is you or everyone.

Error codes, and the fixes players say worked →

Reports in the last 24 hours

13:00 UTC — 4 reports 14:00 UTC — 6 reports 15:00 UTC — 9 reports 16:00 UTC — 12 reports 17:00 UTC — 7 reports 18:00 UTC — 17 reports 19:00 UTC — 13 reports 20:00 UTC — 11 reports 21:00 UTC — 12 reports 22:00 UTC — 14 reports 23:00 UTC — 5 reports 00:00 UTC — 12 reports 01:00 UTC — 10 reports 02:00 UTC — 9 reports 03:00 UTC — 6 reports 04:00 UTC — 3 reports 05:00 UTC — 4 reports 06:00 UTC — 5 reports 07:00 UTC — 3 reports 08:00 UTC — 1 report 09:00 UTC — 6 reports 10:00 UTC — 4 reports 11:00 UTC — 7 reports 12:00 UTC — 7 reports
17
13:00 UTC12 hours agonow

187 players have reported a problem in the last 24 hours, peaking at 17 in a single hour. Each person counts once per hour, however many times they tap.

What people report

  • Server connection30%
  • Signing in30%
  • Something else21%
  • Crashing or freezing15%
  • Matchmaking or queue4%

What people are saying

Short notes from players in the last 24 hours. Say where you are, what you see on screen, or that it just came back — that is what tells everyone else whether it is them or the servers.

No links. Anonymous, no account. Keep it about the game.

Got an error code on screen? We have fixes for 42 of them. Find yours →

  1. Something else

    unable to launch Wardogserror code WD-L020-d6c681498c43

    1. Unable to launch error code WD-L020

      From this siteMatched on "wd-l020"

      WD-L020 has a confirmed cause as of 23 September: Windows 11 preview update KB5124010, per Team17 support. Uninstalling that update fixes it. WD-L004, WD-L006, WD-L007, WD-L010 and WD-L014 still have no published cause — repairing the anti-cheat from the game folder is what has worked most often for those.

      1. Unable to launch error code : WD-L006-0d1a073969ef how can i fix that

        1. Server connection

          код ошибки 1628505088

          From this siteMatched on "1628505088"

          The online services did not answer. It is a server-side fault, not your install: the login backend is saturated and the only thing that works is trying again. If you got as far as a server list and the join failed there, you are on the wrong code — the join timed out page has it.

          1. Signing in

            Failed to login to anti cheat code: 1628505086

            From this siteMatched on "1628505086"

            The online services did not answer. It is a server-side fault, not your install: the login backend is saturated and the only thing that works is trying again. If you got as far as a server list and the join failed there, you are on the wrong code — the join timed out page has it.

            1. Can’t pull my parachute on controller so I die everytime I drop in

              1. Server connection

                код ошибки 1628505086

                From this siteMatched on "1628505086"

                The online services did not answer. It is a server-side fault, not your install: the login backend is saturated and the only thing that works is trying again. If you got as far as a server list and the join failed there, you are on the wrong code — the join timed out page has it.

                1. failed to authenticate with online services wardogs, unsure if this is from my side but my wifi is completly fine, restarted pc and tried other things

                  From this siteMatched on "failed to authenticate with online services"

                  The login service refused your session, which nothing on your machine will change. If the screen also carries 1147405308, that code has its own page: on an out-of-date install it is a version mismatch that verifying fixes, and since launch it is more often the same refusal with a number attached.

                  1. Server connection

                    Has anyone encountered this before? What does this error mean?Code 1413677057 in WARDOGS — "An unexpected error has occurred."

                    From this siteMatched on "1413677057"

                    The game could not get an answer from the online services at load. It clustered on the busiest beta and launch days, and now also recurs in a sharp, roughly hour-long spike most Tuesday evenings around 6pm ET — timing that lines up with Steam's own maintenance window rather than anything WARDOGS-specific. Nothing about it points at your install.

                    1. Crashing or freezing

                      cant start game. error

                      1. cant launch error code WD-L020-5b699e18d0b2

                        1. FIX FOR WD-L020 ERROR:Open Settings → Windows Update → Update History.Find update KB5124010.Uninstall it.Restart your PC.After doing this, WARDOGS launched without any WD-L020 errors. It worked for me on Windows 11.

                          From this siteMatched on "wd-l020"

                          WD-L020 has a confirmed cause as of 23 September: Windows 11 preview update KB5124010, per Team17 support. Uninstalling that update fixes it. WD-L004, WD-L006, WD-L007, WD-L010 and WD-L014 still have no published cause — repairing the anti-cheat from the game folder is what has worked most often for those.

                          1. Error code: WD-L020-9eb42d7178eb. help me fix it please

                            1. Getting same code. Everything I am finding is saying Maintenance is being done. Also included it is supposed to take an hour but its been 6 hours since last notice. Servers are still down

                          2. Crashing or freezing

                            cant even start the game what....

                            1. Same here

                            2. If its after a recent windows update you need to uninstall the KB5124010 portion of it by doing Start → Settings → Windows Update → Update history → Uninstall updates → find KB5124010 → Uninstall

                          3. Something else

                            servers bugged? getting wiped after game now and same after next game

                            1. Crashing or freezing

                              Cant even launce the game get error code

                              1. Same

                              2. same for everyone rn

                              3. If you're getting the WD-L020 error when launching WARDOGS on Windows 11, check if you have update KB5124010 installed. Uninstalling that update fixed the issue for me immediately.

                            2. Something else

                              Unable to lauch

                              1. Server connection

                                how fuking long till servers are up.... save me jesus!!!!

                                1. 1 hour mate

                              2. 25/09/2026 Maintenace Window - 11:00 UTCWARDOGS will be entering a maintenance window at 11:00 UTC, estimated to last around 1 hour.Services, including logins, will be offline while we deploy a small number of security updates. We’ll post again as soon as everything is back on

                                1. Friday night, maintenance, really? yeh its not Friday night for everywhere but other games manage to do updates at times where it has minimal impact

                              3. what the hell is going on here?

                                1. idk

                              4. cant launch game from steam

                                1. It is most likely because the game's anticheat is blocking the latest Windows update. Try to uninstall KB5124010.

                              5. Server connection

                                Looks like half the west servers experienced some kind of disconnect. I was not refunded for my kit after the game had just started. I assume that's the case for everyone from that match. I went back to look at the server I was in (NA West #35) and there were 12 people in it

                                1. Servers tanked again. Checked a couple servers and game state was unchanged, team scores and such, but they maybe had ~20 players in it. 10 minutes into another match and the server disconnected again.

                              6. Signing in

                                wont let me sign in to the game i click on wardogs on steam then get an error WD-l020-a3ff4c3d68a4.

                                1. same still now

                                2. Had the same issue, uninstalled Windows Update KB5124010 and can log in now

                              7. Signing in

                                failed to sign in. wonder how long this is going to take and something to do with the update hmmm????????

                                1. Getting the same thing brother

                                2. Try Verifying game files then restarting steamWorked for me

                              8. Signing in

                                keep getting error code

                                1. Same

                              Players in game

                              222,307

                              Concurrent players on Steam right now. A real outage pulls this down within minutes, so a normal number alongside a flat report count usually means the problem is at your end.

                              Source: Steam GetNumberOfCurrentPlayers, app 1867240, cached 60s.

                              Full player count and trend →

                              Maintenance, queues and full servers

                              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.

                              WARDOGS error codes and crashes

                              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.

                              The full pages, with the steps and the sources →

                              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.

                              If it is only broken for you

                              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.

                              Official WARDOGS server status: where Bulkhead announces outages

                              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:

                              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.

                              Questions

                              Is WARDOGS down right now?
                              As of 12:48 UTC, 3 players have reported a problem in the last 15 minutes — counted as people, so repeat taps from one person do not inflate it. WARDOGS is live in Early Access. This page updates on every load.
                              Is WARDOGS down today, or is it just me?
                              Check the two numbers at the top. If reports are flat and the Steam player count is normal, thousands of people are playing fine and the problem is at your end — work down the checks on this page. If reports spike and the player count drops together, it is not you, and nothing you do locally will fix it.
                              Is WARDOGS down for maintenance?
                              Bulkhead has announced one maintenance window so far: Monday 14 September 2026 from 08:00 UTC, for approximately one hour, to deliver Patch 0.11. It went to the WARDOGS Steam news hub and to @WARDOGS on X, which is where every window is announced. Planned maintenance looks different from an outage here: reports climb steadily and stay flat for the length of the window, rather than spiking in one hour and decaying.
                              Is there a WARDOGS login queue?
                              Yes, WARDOGS queues players at login rather than refusing them, and on launch night that queue ran into the hundreds of thousands. Bulkhead said the queue issues should have passed as of 00:00 UTC on 11 September 2026, so most sessions now go straight in. A queue looks like a flat player count with a spike in matchmaking reports: the servers are up and full, not down, and waiting is the only fix. Restarting the client does not skip it — you rejoin at the back.When the queue is stuck, going backwards, or ends in a full server →
                              What is WARDOGS error 1147405300?
                              It appeared during the Closed Alpha on 7–9 August 2026 and it fails when joining a server rather than when starting the game. Both players who reported it were also placed in a region that was not theirs, which points at matchmaking. The whole public record is one thread from that day: this tracker has counted 126 reports naming a 1147405xxx code since, across both closed betas, and none of them is this number. Codes in the same family that end differently are separate faults with separate fixes.What the two reports said, and how far the circulating fix goes →
                              Why does WARDOGS crash on launch?
                              This was the most reported fault of the Closed Alpha and Bulkhead has said publicly that they are tracking it. What players report working: delete the EasyAntiCheat folder in the install directory, delete %LOCALAPPDATA%\Wardogs, reboot the PC, verify the game files through Steam, then let the shaders compile. The reboot is the step most people skip. If it still crashes, check %LOCALAPPDATA%\Temp for dump files beginning PACKER — an access violation c0000005 there is a client bug, not something reinstalling will fix.The full sequence, in order, and what to do when it fails →
                              Why does WARDOGS say "connection to server lost"?
                              That message means the client reached a server and then lost it, which is different from failing to connect at all. If the report count here is flat it is almost always local: verify the game files in Steam, restart your router, and drop any VPN. If reports are climbing, it is the servers and there is nothing to fix at your end.When the server browser comes up empty instead →
                              Does Bulkhead publish an official server status page?
                              No. Bulkhead has not published a status endpoint or a status page for WARDOGS, which is why community trackers exist for this genre at all. The nearest official signals are the WARDOGS Steam news hub and the @WARDOGS account on X, both of which are announcements rather than live status.
                              How does this tracker know?
                              It does not measure the servers — nobody outside Bulkhead can. It counts players reporting a problem, the same way an outage tracker for any service works, and it shows the Steam concurrent player count alongside, which falls sharply during a real outage. Two weak signals that agree are more useful than either alone.
                              Is "War Dogs" the same game?
                              Yes — WARDOGS is often written as two words, and this page covers both spellings. Note that War Dogs is also a 2016 film with Jonah Hill, which is what most search results for the two-word spelling are about. The game is by BULKHEAD, published by Team17, and is app 1867240 on Steam.

                              Incident history

                              Auto-logged from player reports over the last 30 days. An incident is a run of hours with at least six different players reporting in each — the same signal the verdict above responds to. Repeat taps from one person count once an hour, so no single frustrated player can put an incident on this list.

                              26 Sept, 11:002 hours · peak 7/hr · 14 players · mostly Server connection
                              26 Sept, 09:001 hour · peak 6/hr · 6 players · mostly Something else
                              26 Sept, 00:004 hours · peak 12/hr · 37 players · mostly Server connection
                              25 Sept, 14:009 hours · peak 17/hr · 101 players · mostly Signing in
                              25 Sept, 11:001 hour · peak 13/hr · 13 players · mostly Server connection
                              25 Sept, 01:002 hours · peak 6/hr · 12 players · mostly Server connection
                              24 Sept, 19:002 hours · peak 7/hr · 14 players · mostly Server connection
                              24 Sept, 07:003 hours · peak 9/hr · 22 players · mostly Signing in
                              23 Sept, 22:002 hours · peak 9/hr · 17 players · mostly Something else
                              23 Sept, 18:002 hours · peak 7/hr · 13 players · mostly Something else
                              22 Sept, 22:001 hour · peak 13/hr · 13 players · mostly Signing in
                              22 Sept, 20:001 hour · peak 7/hr · 7 players · mostly Signing in
                              18 Sept, 22:001 hour · peak 6/hr · 6 players · mostly Server connection
                              18 Sept, 16:003 hours · peak 7/hr · 19 players · mostly Server connection
                              16 Sept, 14:001 hour · peak 6/hr · 6 players · mostly Server connection
                              16 Sept, 00:001 hour · peak 6/hr · 6 players · mostly Server connection
                              15 Sept, 22:001 hour · peak 12/hr · 12 players · mostly Server connection
                              14 Sept, 14:001 hour · peak 6/hr · 6 players · mostly Signing in
                              14 Sept, 08:002 hours · peak 16/hr · 22 players · mostly Signing in
                              13 Sept, 23:001 hour · peak 6/hr · 6 players · mostly Server connection
                              13 Sept, 15:001 hour · peak 6/hr · 6 players · mostly Signing in
                              12 Sept, 21:001 hour · peak 6/hr · 6 players · mostly Server connection
                              12 Sept, 00:001 hour · peak 9/hr · 9 players · mostly Server connection
                              10 Sept, 20:005 hours · peak 24/hr · 65 players · mostly Server connection
                              10 Sept, 16:003 hours · peak 14/hr · 34 players · mostly Server connection
                              7 Sept, 15:001 hour · peak 6/hr · 6 players · mostly Server connection
                              7 Sept, 05:002 hours · peak 7/hr · 13 players · mostly Server connection
                              6 Sept, 08:0017 hours · peak 14/hr · 148 players · mostly Server connection
                              5 Sept, 23:001 hour · peak 7/hr · 7 players · mostly Server connection
                              5 Sept, 16:002 hours · peak 6/hr · 12 players · mostly Signing in
                              5 Sept, 08:001 hour · peak 6/hr · 6 players · mostly Server connection
                              4 Sept, 13:003 hours · peak 8/hr · 20 players · mostly Server connection
                              4 Sept, 02:002 hours · peak 8/hr · 15 players · mostly Server connection
                              3 Sept, 18:001 hour · peak 16/hr · 16 players · mostly Server connection
                              3 Sept, 13:003 hours · peak 7/hr · 19 players · mostly Signing in
                              3 Sept, 08:001 hour · peak 6/hr · 6 players · mostly Server connection

                              While you are waiting for it to come back