WARDOGS Server and Queue Status: After 400,000 Players Broke Launch

The short version: the launch login queue meltdown is fixed, but it owned WARDOGS’ entire first week of headlines. On September 10 the queue collapsed under a login surge and an overactive anti-cheat system; the developer shipped Launch Stability Hotfix #1 the same day, forcing every client to restart and letting players in batches. On September 14 an hour of maintenance delivered Patch 0.11 and rebuilt the server browser.

As of 2026-09-18 the Steam all-time score is Very Positive (about 80.2% of 67,518 reviews positive), and the last 30 days of English reviews sit at 84.9% positive. One caveat: high-demand community features like team switching controls are still on the developer’s pending list.

What actually happened in those 48 hours

The root cause was not “not enough servers”. Two things collided. In the words of UI/UX Director Howard Philpott, the anti-cheat system was aggressive enough that it started banning the studio’s own legitimate alpha testers — including Shroud and Summit1g while they were streaming — while “hundreds and thousands” of players hit the login queue at once. His summary of the moment: “We either fix the queue now, or we’re f*ed.”**

Credit where it is due: most studios would have posted “we are aware of the issue” and gone quiet. This one shipped a client hotfix the same day.

What is already fixed

• The login queue itself. When you now reach the front of the queue, you are handed a fresh ticket from Valve’s login system rather than having the ticket you opened the game with validated. That was the core hotfix change.
• The server browser. Patch 0.11 split the browser into Community and Official. The official browser dropped filters it no longer needed, while community servers gained text search, reliability fixes and persistent server IDs you can join directly.
• Crashes and exploits. Patch 0.11 fixed multiple cash exploits and more GPU crashes. The Season 1 changelog separately fixed two frame-generation crash paths, an off-thread network call crash and several buildable crashes.
• Regional capacity. The developer increased server capacity in Asia and said it would keep treating the region as a core part of the player base.
• Voice and reporting. Season 1 fixed voice permanently cutting out after a failed join, stale channel rejoins, push-to-talk targeting and re-login recovery, and added a report tracking system with weighted reports.

What is still missing: the developer’s own to-do list

Patch 0.11’s “Upcoming Features” section lists what is scheduled but not ready:

• Community server favouriting
• Tiered priority queues
• Message of the Day
• Improved warmup activities
• Disabling AFK kicks during seeding
• Team switching controls

The developer also states these quality-of-life fixes do not consume Season 2 content work — they are short-term reactive fixes. In plain terms: the server browser layer got meaningfully better, but the community governance layer is still coming.

Three checks before you log in

1. Confirm your client is current. The forced update on launch day was not punishment, it was stopping stale clients from clogging the queue. After Patch 0.11 the build number is 0.11.
2. Tell “queued” apart from “cannot connect”. A moving progress bar means queuing; an outright error means checking whether maintenance is scheduled. The Patch 0.11 window was published two days early in a UTC table covering every region.
3. Verify through a second route. If you suspect a regional problem, try a community server or another region once. Community admins have console access and can deal with troublemakers on the spot.

What the various camps say

The developer is owning it. Philpott says “there is no excuse”, and later that “everyone was in game and we could actually open a champagne bottle”.

Media are consistent: the failure was real and so was the response. PCGamesN called it a rare example of effective crisis handling; PC Gamer and GamesRadar+ logged the 300,000-player queue and the review bombing, and also logged Team17’s clarification that “these issues are affecting players across the board” and streamers simply had no priority access.

Players are split along a timeline. The all-time score is still held down by those first hours, but recent English reviews are back to 84.9% positive. One widely quoted review puts it plainly: “reviews were from children not being able to play immediately due to a 400,000+ player influx blowing their servers up at first… it’s all good now.”

A note on the numbers

Peak concurrents come in several versions: the official announcement says 400,000, a SteamDB news item says 428k, GamesRadar+ cited SteamCharts at 340,171 on September 11, and PCGamesN reported “over 365,000” on September 12. Sales diverge too: the official figure on September 11 is 2 million copies, updated to 2 million on September 15, and PCGamesN reported 1.5 million on September 12 — now an outdated figure. This page uses the official figures and lists the media numbers alongside — better to show you that the number is contested than to hand you a fake precise peak.

Sources and boundaries

Launch Stability Hotfix #1 (September 10), 1.25 MILLION COPIES SOLD! (September 11), 2 MILLION COPIES SOLD (September 15), SCHEDULED MAINTENANCE & PATCH 0.11 (September 12) and the Season 1 changelog (September 9) all come from the Steam announcement feed. The developer’s post-mortem comes from the PCGamesN interview, and the launch queue and review bombing from PC Gamer and GamesRadar+. Review data was read from the Steam reviews API on 2026-09-18. The embedded video is the developer’s own launch-day studio recap (240spQbhgIA).

This page promises nobody a specific queue time and does not promise zero crashes; maintenance windows follow official announcements. For the buying decision see the pre-purchase checklist, and for cheat policy see cheaters and anti-cheat.