WARDOGS servers: official versus community, the three hosting partners, the browser split in patch 0.11, capacity, and the launch-day queue

Patch 0.11 describes them by what they lack: 'Removed unnecessary filtering from Official Servers. In its current state, filtering is not necessary for Official Servers as we do not have Official modified game modes. Filters have been removed from the Official browser.' The same post admits the browser model itself is a compromise for a game this size: 'A game with this many players realistically should be using matchmaking, and server browsers aren't massively fit for purpose.' Official servers exist in regions — the post announces 'increased the server capacity in the Asian region' — and the maintenance table lists fourteen zones from US Pacific to New Zealand.

Anti-cheat runs on both kinds. The enforcement policy: 'It applies to all online play, on official servers and on community servers alike.' The 'Show Empty/Full' toggle added to the browser quick bar in 0.11 applies to the list as a whole.

BULKHEAD's 8 September post: 'Community Hosted Servers are available to pre-order now through our 3 Approved Hosting Partners; QONZER, BisectHosting and xREALM.' wardogs.com's server hub page lists the approved partners and a 'Server Admin Hub' Discord. The studio's case for them is anti-cheat: 'for the ultimate protection, play on community hosted servers where admins can instantly ban bad actors.' Patch 0.11 goes further — 'Community Servers are the lifeblood of FPS games like ours… They're the lifeblood of the community who keep a game running well beyond its peak player days.'

Hosting prices, slot counts and admin tools are on the partners' sites, not in any BULKHEAD post, so we do not quote them. What the studio has published is the rule set: server names must sort 'alphabetical regardless of special characters and numbers' and may not use more than one consecutive space; each server has a persistent unique ID that is 'much longer for security reasons'; and until about 19 September, community servers pay a 5% end-of-match cash bonus.

Why three hosts and not self-hosting: BULKHEAD's 11 August post noted it had been 'capped on how many Steam Keys we can send externally', and the approved-partner model keeps server binaries with vendors the studio has vetted. The 8 September post's phrase 'available to pre-order now' means community servers were sold before launch; the 0.11 admission that the browser did not surface them means many were empty in the first days.

GamesBeat's Dean Takahashi (7 September 2026) reported the BisectHosting partnership with two quotes that describe the infrastructure. BULKHEAD: 'Wardogs has specific requirements, and we weren't willing to compromise on them to fit a standard hosting mold. BisectHosting understood what the game needed and built their infrastructure around it.' BisectHosting CEO Max Podkidkin: 'Nearly half a million players showed up for the beta. When that community starts launching up their own servers, the infrastructure underneath them needs to perform flawlessly.' The article says BisectHosting runs '2+ million game servers across 20+ global locations' and that reservations opened at bisecthosting.com/wardogs-server-hosting; it gives no prices, slot counts or admin-tool details, and neither does BULKHEAD.

The 'nearly half a million' beta figure is the hosting CEO's; BULKHEAD's own posts give no beta player total, and PCGamesN's 245,000 is a concurrent peak, so the two numbers measure different things.

'Split front end into two browsers, Community and Official.' 'Improved reliability of filtering in Community Servers.' 'Added text based search to Community Servers.' 'Community Server IDs now persist between matches and restarts… so players can join via ID.' 'Added Show Empty/Full to browser quick bar.' 'Updated Host button to direct to the correct location.' Before 0.11, the Season 1 changelog had already 'reworked server browser filtering' and fixed 'community server images scaling incorrectly' — evidence that the browser was being rebuilt twice in five days.

Practical use: to find a specific community server, use the Community tab's text search or its ID; to play official, use the Official tab, which has no filters to set. 'Wardogs not showing servers' — a live search — is most likely the pre-0.11 browser or the launch-day queue; after 14 September, the two-tab browser is the current state.

Patch 0.11 set the first published rules for community servers. They are short enough to list.

BULKHEAD had tested the login queue in Closed Beta 02 ('areas of the game that only break at scale, such as… our login queue'). It broke anyway. PCGamesN's account, with BULKHEAD staff on record: the beta had opened its firing range six hours early so players 'filter in more gradually'; at launch everyone arrived together; a stats screen in the studio showed 45,590 in game and 168,000 queued; and because login tickets expired while players waited, 'out of the 100 players per second that should have been let through the gate, just ten of them were.' UI/UX Director Howard Philpott: 'We knew in the moment: we either fix the queue now, or we're f***ed.'

The fix, Hotfix #1 at 20:20 UTC: every client forced to restart and update, everyone back to the queue, then admission 'in controlled batches' — 'sets of 10,000', per Production Director James Tatum-Dean, who called it 'a one-shot thing'. The mechanism was to hand each player 'a fresh ticket from Valve's login system' at the front of the queue instead of the stale one. The queue reached zero that night. Executive Producer Joe Brammer also admitted jumping 'about 11' streamers ahead: 'That's on me… It is a bit unfair.'

Patch 0.11: 'We have increased the server capacity in the Asian region to support the interest coming from that region. Thank you to our players across Asia who have shown interest and continued to play the game. We will be putting more focus into supporting Asia as an important part of the worldwide Wardogs playerbase.' The 14 September maintenance table gives local times for Thailand, Vietnam, Indonesia, China, Taiwan, Korea, Japan, Eastern Australia and New Zealand alongside the Americas and Europe, which is the clearest official map of where BULKHEAD runs or expects players. Peak concurrency was 400,196 on 12 September (SteamDB); the live count is on the player-count page.

Russian-language community guides about 'zapret' and 'вход из РФ' indicate connectivity problems from Russia specifically; no BULKHEAD statement addresses that region.

One so far: Monday 14 September 2026, 'approximately 1 hour', starting 08:00 UTC — 01:00 PDT, 04:00 EDT, 09:00 BST, 10:00 CEST, 16:00 China, 17:00 Japan, 18:00 AEST. BULKHEAD posted it two days ahead with a fourteen-zone table, which is the pattern to expect for future windows; the patch-notes hub carries each new post.

Every server has proximity voice and squad voice; the Season 1 changelog added 'a visible communication status' and fixed voice failing after a bad join. Reports made in game go to BULKHEAD regardless of server: the player-safety page says 'Reports come to us, not to the server you were playing on', that a report 'may include a short extract of the recent text chat from that session, currently up to the last 50 messages', and that 'most reports are dealt with within a few days, and serious ones sooner'. Reporters are not identified to the reported player. Community admins act separately and immediately on their own servers, which is what BULKHEAD's 'ultimate protection' line means.

Two community-run resources were trending on Steam's guides list: 'KOTH Community | WARDOGS' and 'dog-tags WARDOGS Clan Finder – Find a Squad or Recruit Players'. We cite the titles as evidence that clan and community-server organisation started in week one; we have not vetted either.

From the enforcement policy: cheating, tampering, macros, anti-cheat interference, exploiting bugs, win trading, account sharing, ban evasion and abuse are all bannable on official and community servers alike, and 'the account holder is responsible for any infraction on the account'. Reports go to BULKHEAD, not to the server host — the player-safety page: 'Reports come to us, not to the server you were playing on' — and may include up to the last 50 text-chat messages from the session. Community admins can additionally ban from their own servers, which is the 'ultimate protection' the 8 September post refers to.