Skip to content
← All errors

Kicked from match

WARDOGS keeps kicking you out of matches

Published Updated Data as of Season 2 · 15 Oct 2026

This one is not your machine

A server-side fault with no working player-side fix. Launch Stability Hotfix #1 lists this exact symptom as addressed and the reports carried on after it, so the honest answer today is that Bulkhead has named it and not finished it.

Check whether WARDOGS is down right now →

What you see

You are in a match and the game puts you back on the main screen or the server browser before it ends — sometimes with a "kicked from match" message, sometimes at three minutes, sometimes every match in a row. Whatever you were carrying goes with it.

Also reported as: kicked from match · kicked out of match · removed from match · kicked from every match · kicked from server during play · disconnected mid match

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 Separate this from a kick at the join step

    Confirmed

    If the drop happens as you click a server rather than during play, it is a different fault with a different answer — error 1628505091 refuses the join outright, and the bounce straight back to the main menu has its own page. This page is for a match you were already in.

  2. 02 Make sure you are on the hotfix build, then stop troubleshooting

    Confirmed

    Steam → WARDOGS → Properties → Installed Files shows the Build ID; 25238722 or higher is Launch Stability Hotfix #1 or later. That update names "players being unexpectedly kicked from servers during play" as one of three things it addresses. If you are on it and it is still happening, nothing further on your machine has been shown to change it.

  3. 03 Check it is not a ban screen before you assume it is this

    Confirmed

    On launch night a wave of incorrect bans dropped players the moment they picked a server, with "Access denied - No license found" or a permanent-ban notice rather than a kick message. Bulkhead cleared those server-side. If there is a ban or licence wording on screen, you are on the wrong page.

  4. 04 Run Team17 support's checks once, and expect them to change nothing

    Reported

    The support thread asks for the usual sequence: verify integrity of game files, delete the EasyAntiCheat folder in the install directory, close overlays and monitoring software such as MSI Afterburner, then send a DxDiag. They are worth one pass because a genuinely broken install produces the same symptom, and no player has yet reported the sequence fixing this one.

  5. 05 Report it with the time and the server

    Reported

    This is the stage where a fault gets fixed by being counted. The Report a Problem board on Steam and the Discord developer forum are where Team17 and Bulkhead are reading; a post that carries the match time, the region and whether you were in a vehicle is worth more than ten that say it happened again.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

There is no fix on this page, and that is the finding rather than a gap in it. What exists is a fault Bulkhead has named, a patch that claimed it, and a stream of reports that did not stop when the patch landed.

What is known

The studio named the symptom. Launch Stability Hotfix #1, at 20:20 UTC on 10 September, lists three things it addresses, and the second is players being unexpectedly kicked from servers during play. That is as close to an acknowledgement as this fault has.

It is older than the launch. During Closed Beta 02, on 4 September, a player wrote that every second match ended with a "you get kicked out from match" message, and another answered within the minute to say the same. Whatever this is, it survived the beta, the launch build and the hotfix.

It costs you the run. The reports that carry detail describe being dropped partway through and losing what the match had earned — loot and money from that session, repeatedly, across matches played normally.

Reports continued after the hotfix. Players who took the 20:20 UTC update were posting the same thing through the night and into 11 September, in runs of five to ten minutes, some of them every match.

What is not known

Nobody outside Bulkhead has a cause, and the guesses circulating are worth naming only so you can stop chasing them. That the kick follows a particular kind of kill, that it is mouse or peripheral software, that it is the ban wave catching people a second time: none of these has more than a handful of posts behind it, none has been tested against a case where it did not happen, and no developer has endorsed any of them.

The one connection with anything behind it is the ban wave, and it is a connection of timing rather than of cause — the incorrect bans and the mid-match kicks both peaked on the same night, and the ban wave has an answer while this does not.

Still happening on 12 September

The reports on the tracker did not thin out over the weekend. Players on 12 September described a kick every ten minutes whatever the server or region, EU West and Central dropping them about ten minutes in, three kicks in three matches with nothing in common, and one player fine on Asian servers and kicked on an American one at around 250 ms. Several put the cost in cash: thousands lost in a day.

The kick also has a second half now. Back on the main menu, the game hangs on "fetching data" or "Logging in", then refuses the login with error 1147405308, and relaunching several times is what gets people back — that lockout has its own section.

Two things from the same weekend do not explain it. The single server Bulkhead took down on 12 September was dropping players at the join step, not partway through a match. And Patch 0.11, scheduled for 08:00 UTC on 14 September, names the server browser, cash exploits and GPU crashes, not this.

Automatic kicks on official servers

Unconfirmed. A separate complaint has started alongside the mid-match drops: being removed from an official server by the game itself rather than by a fault. On 12 September a player in Brazil described being kicked from US servers every time since the latest update, and put it down to a ping check treating a high but playable ping as a violation. Nobody else has shown that a ping limit exists, and Bulkhead has not mentioned one.

What does exist is an inactivity kick. Patch 0.11 lists "AFK kicking during seeding disabling" among the features in the pipeline, which means idle players are currently removed while a server is still filling. If you were dropped from a near-empty server after standing still in the warmup, that is the likelier cause, and it is working as built.

Neither of these loses a match you were playing. If the kick came mid-fight with no message, the sections above apply.

What to do in the meantime

Play in shorter sessions if you can choose, because the loss is the run rather than the account, and watch the tracker for the next hotfix. Bulkhead shipped one inside five hours on launch day and said the team would be working through the night; a second patch naming this symptom again is the thing to wait for, and this page changes the day it arrives.

If a kick took more than that match's earnings, cash you had before it started, that is a separate bug: lost money after a crash or disconnect.

If that did not do it