WARDOGS server status: live players, maintenance and release evidence

Dated release evidence, not a green “all services healthy” badge

Use three separate signals: official notices, Steam activity and your exact symptom. A dated announcement confirms an event. A fresh player count measures activity. Neither alone proves that every login service, region or individual server is reachable now.

Confirmed release event

Season 2 releasedThe October 15 notice said its release maintenance ended.

Last reviewed release build

Update 0.2.0Some database fields are individually marked older references, not a single global catalogue version.

Official-source snapshot

October 26, 2026 · 20:29:00 UTCThis timestamp is a source review, not the time of the Steam reading below.

Season dates

Season 2: October 15Season 3 is scheduled for November 12 in the October 23 developer reply; its exact hour is not stated.

Live Steam activity is a separate signal

The count, ranking and leaderboard peak below come through the existing Steam-data service. Each reading keeps its own observation time. A usable earlier reading stays labelled as such after a request failure and expires after 30 minutes; a missing or expired reading is not displayed as a real zero.

This compact view requests only the current reading, not the archive. Open player-count history for the observed 24-hour and daily charts, their gaps and response-generation window. Population is not a login-service health check, and even a real zero is not enough to identify one outage cause.

The October 15 maintenance window is in the past

The Season 2 release notes scheduled October 15 maintenance for 08:00–09:30 UTC. The subsequent release notice said Update 0.2.0 was out and servers had reopened. That statement is historical evidence, not a current incident banner or a new maintenance window.

The October 16 developer post then removed the Lonestar bonus and addressed Driver progression/exploit issues. It was not a fresh global outage notice. The later November 12 Season 3 schedule is also separate: do not reuse October's maintenance hours for the next season. See the reset and Season 3 guide for the limits of that announcement.

Pick the route that matches the failure

• WD-L020 on launch: the historical Update 0.1.2 notes report a fix for the KB5124010-related crash. A new occurrence is not proof of a global server outage. Use the error-code guide; do not remove Windows updates merely because an older post mentions one.
• Empty list or failed login: check version, Official versus Community, filters, region and the precise stage. Use server-list and connection diagnosis.
• Startup or shader crash: follow the startup or shader route instead of assuming an outage.
• Voice only: device, permissions or channel can fail while a match remains accessible. Use the voice-chat checks.

These are diagnostic categories, not a claim that all listed issues are active incidents today.

Check the build before treating a rule as a failure

The reviewed Season 2 release describes region-specific sustained-ping limits, ping tags and a rejoin restriction until the next map after a high-ping kick. The joining/team-switch condition can also leave the map obscured until the control zone is reached. These rules can explain a specific rejection without establishing that the whole game is down.

Compare the selected server with your client version. The reference build here is not an automated detector for every later hotfix. Read the Season 2 hub and current official notices before inferring a cause.

Is this a wider incident or your route into the game?

1. Read the latest official notice. If maintenance or an incident is announced, avoid random local changes while waiting for the stated update.
2. Inspect the activity timestamp. Active Steam players provide context but do not rule out login, matchmaking or regional failures. An unavailable count is unknown, not confirmation of a shutdown.
3. Record the symptom. Save the client build, exact error, server ID, region and time. Compare a suitable second server and dated reports before blaming one component.
4. Use a reversible test. Start with the matching diagnostic path rather than reinstalling, deleting files or weakening security on speculation.

The source-review timer only ages this page's evidence. It does not fetch new announcements, reset itself when a player refreshes or silently certify current uptime.

Common status questions