WARDOGS is live in Steam Early Access

15 October: Season 02 live after extended maintenance

BULKHEAD said maintenance began at 08:00:02 UTC. At 09:39:08 UTC, nine minutes after the scheduled finish, it extended the window and said existing servers would restart across regions, without a revised ETA or technical cause. At 10:00:10 UTC, WARDOGS Updates said Season 02 was live and services were back online; @WARDOGS repeated that at 10:01:51 UTC. The recovery posts record those moments and do not guarantee uninterrupted access afterward.

Read the Season 02 maintenance timeline and patch notes →

2 October: scheduled hotfix hour passed without a visible recovery post

BULKHEAD scheduled a hotfix for 08:00 UTC on 2 October to address minor security and stability issues affecting some players, with one hour of expected downtime. At 09:38 UTC, the complete Steam News feed and public @WARDOGSUpdates timeline still showed no start or recovery notice. That absence does not prove whether work ran or what is online now; the notice names no symptoms, build number, code changes, platform, region or service component.

Read the hotfix scope and status boundary →

30 September: Update 0.1.2 maintenance completed at 09:01 UTC

BULKHEAD scheduled services offline at 08:00 UTC for an estimated one-hour window while Update 0.1.2 was deployed. At 09:01 UTC, @WARDOGS said the maintenance window was over and told players to close the game, update to the latest client and then join servers. The recovery post records that instruction at that moment; it does not prove uninterrupted service afterward.

Read the complete Update 0.1.2 timeline and notes →

25 September: services returning after security maintenance

WARDOGS Updates scheduled an 11:00 UTC maintenance window estimated at around one hour, with services offline while a small number of security updates were deployed. At 11:42 UTC, it said services were coming back online. No patch number, client download, security detail or affected-platform list was published. The recovery wording records that moment rather than guaranteeing uninterrupted service afterward.

Read the official recovery update →

24 September: network disruption outside the EU

At 21:36 UTC, WARDOGS Updates said services were experiencing network disruption in non-EU regions, primarily North America. It warned that players may see connection issues while the team worked to mitigate the disruption. The notice names no cause, affected service component, workaround or restoration time. No official recovery notice was visible when checked at 00:46 UTC on 25 September, so this records an acknowledged active incident at that check — not proof that every non-EU player was affected or that EU service was fault-free.

Read the official disruption notice →

24 September: incorrect Steam build marked resolved

At 09:18 UTC, WARDOGS Updates said an incorrect build had been pushed to Steam that morning and had affected a small number of players. Its instruction for anyone still in the queue was to close the game and redownload it through Steam; the stated download was approximately 16 GB. At 09:29 UTC, the account replied that the incident had been resolved. The studio did not publish a build number or list of code changes, and the 16 GB incident download is not a new storage requirement or a normal patch-size baseline.

Read the official resolution →

Patch 0.11 maintenance completed

At 07:53 UTC on 14 September, @WARDOGS said temporary downtime was imminent while the team ran maintenance and delivered an update. At 09:06 UTC, the account said the servers were back up after the short maintenance window. Patch 0.11 separates Community and Official server browsers, adds community-server text search and persistent IDs, addresses more GPU crashes and increases Asia capacity without publishing a numeric regional limit. The recovery post records one moment; it does not promise uninterrupted service afterward.

Read the recovery timeline and every Patch 0.11 change →

Read the detailed client changes

The dated patch archive now lists Season 1 XP bands, vendor and track prices, unlock moves, vehicle changes, voice and stability fixes. Launch Stability Hotfix #1 separately tells players to restart, update and rejoin controlled admission queues.

Read the full official patch breakdown →

Released on Steam

The Steam store now offers purchase and immediate Early Access. It lists the game as released on 10 September 2026. That establishes release availability; it does not establish that every player can connect to a server.

Published launch time and the date in Singapore

BULKHEAD’s 9 September global release map set the unlock for 10 September at 16:00 UTC. Singapore is UTC+8, so that is midnight on 11 September. This was an official announcement by launch day, although the same hour had previously circulated only as a SteamDB estimate. We did not record the exact minute the storefront switched, so the table is the published schedule, not measured login availability.

Launch Stability Hotfix #1

BULKHEAD published its first launch stability hotfix on 10 September at 20:20 UTC, or 11 September at 04:20 SGT. The notice identifies failed server joins, unexpected kicks and extended login queues. It says a client update was released and players would be admitted in controlled batches while the team monitored results.

1. 01

   Restart WARDOGS

   The hotfix notice instructed logged-in players to close and restart the game.

2. 02

   Install the client update

   Allow Steam to download the latest update before relaunching.

3. 03

   Rejoin the login queue

   The notice says all players return to the queue, with admission increased in controlled batches as servers fill successfully.

What the 19-hour launch recap says happened

BULKHEAD says the queue asked Steam for a login ticket when a player joined it, but long waits let tickets expire before players reached the front. The studio describes sending 100 login requests per second while only 10 succeeded, leaving 90% blocked. Hotfix #1 changed the flow so a player obtained a fresh ticket at the front of the queue. BULKHEAD then admitted players in 10,000-player waves and says the launch queue eventually reached zero. Those numbers describe the launch incident, not present capacity or current uptime.

The publisher release reports a 428,666 Steam peak

BULKHEAD and Team17’s 15 September press release reports an all-time peak of 428,666 concurrent players on 13 September and attributes that measurement to SteamDB. The publisher statement supersedes the earlier rounded 400,000 milestone, but the underlying peak remains a third-party continuous measurement. This site’s direct Valve API sample reached 425,674 at 19:27 UTC that day. None of these figures is a live count, server-capacity measure or sales total.

The separate incorrect-ban notice

A pinned Steam discussion post from a developer-tagged BULKHEAD account says the team rescinded a batch of incorrect bans and asked affected players to try the game again. The wording is deliberately narrower than “all bans restored”: the notice gives no total, does not say every disputed ban was reversed and does not explain whether every case had the same cause.

What changed since the beta

The 9 September Season 1 changelog covers server-browser filters, voice reliability, crash fixes, XP curves and item unlocks. Beta prices and levels on this site remain labelled with their original build; they are not automatically valid in the released game.

Where to check the next service update

Use BULKHEAD’s Steam announcements, @WARDOGSUpdates, @WARDOGS and official Discord for current service notices. The newest material notice at this page’s 10:28 UTC check said Season 02 was live and services were back online at 10:00 UTC after an extended maintenance window. That is not a continuous health measurement.

Every maintenance time in one table

The scheduled windows recorded above — start, BULKHEAD’s estimate, how far ahead it was announced and the first back-online post — are collected in one table, with each start converted to your own time zone.

What time WARDOGS updates go live, in your time zone →

Common questions