Skip to content
WARDOGSSOURCED GAME GUIDESON STEAM
FIELDGUIDE /ERROR CODES

ERROR CODE

“Your connection could not be verified so your session has been terminated.”

Kicked mid-match with “Your connection could not be verified”? The full message, the 1 October reports, the next-day hotfix, and what nobody has explained.

THE STRING

Your connection could not be verified so your session has been terminated.

View the source
First public report
Where it fails
Mid-match, minutes after you join
Cause established
No — reports only

A kick that says your earnings were kept

Unverified

The message has two sentences, and players usually quote only the first. The one full quotation located, posted on Steam on 1 October 2026, reads: “Your connection could not be verified so your session has been terminated. All cash/XP earned this session has been saved.” That player saw it prefixed “KICKED Caution”, on their third match in a row. The second sentence is a claim about what you earned during the session. It says nothing about what you spent, and the players reporting losses describe purchases: one had spent 30k on a purchase, was kicked about ten minutes later, and calls it “a loss of 30k”. No official text describes a refund for a kick of any kind.

1 October: two threads titled with it inside an hour

Unverified

The earliest public reports located are both from 1 October 2026. A thread titled “CONNECTION VERIFY FAILED KICKED” opened at 12:59 UTC and reached 71 posts. Six minutes later a second thread, titled with the message itself, opened with “After 3–5 minutes on the server, I get kicked”. The replies describe the kick repeating: three matches in a row, again on rejoining, unchanged after swapping servers, on OCE servers. One player notes servers sitting at 40/100 or 60/100 as “massive amounts of people” were booted. A reply on the Update 0.1.2 announcement thread blames that update, which had gone live the previous morning. Nobody from BULKHEAD or Team17 replied on any of the thread's five pages, read on 10 October.

The next day's hotfix notice: timeline, not cause

Publisher stated

At 00:13 UTC on 2 October, roughly eleven hours after the first reports, BULKHEAD published a Security & Stability Hotfix notice. It scheduled maintenance for 08:00 UTC that day, with about an hour of downtime, “to address minor security and stability issues affecting some players”. The notice names no symptom and no message. Nothing published connects it to this kick, so this page records it as the nearest official event in time and nothing more.

The 2 October hotfix notice in full →

Not the heartbeat kick, and not a ban

Unverified

Two neighbouring messages are easy to confuse with this one, and each has its own page. All three end your session, but they appear at different moments and were first reported on different days. The players in the 1 October threads joined new servers and were kicked again. That is how a kick behaves, not a ban, though nothing official says either way.

“KICKED: no valid heartbeat within window” →

MessageWhen it happensFirst public reportWhere it lives
“Your connection could not be verified…”Mid-match, minutes after joining1 Oct 2026This page
“KICKED: no valid heartbeat within window.”Mid-match20 Sep 2026The heartbeat kick page
“The timeout period has expired.” 1628505091While joining, or on arrival10 Sep 2026The 1628505091 page

What is not established

Unverified

BULKHEAD and Team17 have not said what is being verified, whether the check belongs to the anti-cheat, the servers or the account service, or why it failed for so many players at once on 1 October. Nothing says whether the 2 October hotfix changed it. There is no published rule for refunding a loadout lost to any kick, so the message's promise covers earnings only. How often it happens since 1 October is not published either. If you see it, note the time in UTC and the server region. That is what would let a later report be matched to an official one.

Common questions

What does “Your connection could not be verified” mean in WARDOGS?

That the game ended your session mid-match because a verification of your connection failed. That much is in the wording. BULKHEAD and Team17 have not said what is verified or why it fails. The first public reports are from 1 October 2026, when two Steam threads titled with it opened within an hour.

Do you lose your cash when you are kicked for “connection could not be verified”?

The message says that all cash and XP earned that session has been saved. It says nothing about money you spent: players kicked on 1 October report losing what they had spent, one of them 30k on a purchase. No official text describes a refund after a kick.

Was the “connection could not be verified” kick fixed?

Nothing official says so. BULKHEAD published a security and stability hotfix notice at 00:13 UTC on 2 October, about eleven hours after the first reports, for maintenance at 08:00 UTC. That notice names no symptom, so it cannot be read as a fix for this message.

Sources & verification

Each source below carries its own read date and its own boundary note. A Steam thread establishes that a string exists and when it was first reported; it does not establish a cause.

SourceTypeRead
Steam · “CONNECTION VERIFY FAILED KICKED”, WARDOGS discussions, 1 October 2026Opened 12:59 UTC; 71 posts when read. Replies report the kick repeating across servers, after rejoining, and on OCE servers, and one reports a 30k purchase lost to a kick. No developer reply on any of its five pages.Unverified2026-10-10
Steam · “wardogs your connection could not be verified so your session has been terminated”, WARDOGS discussions, 1 October 2026Opened 13:05 UTC and titled with the message: “After 3–5 minutes on the server, I get kicked with this error: ‘Your connection could not be verified so your session has been terminated’”.Unverified2026-10-10
Steam · a reply on the Update 0.1.2 announcement thread, 1 October 2026The one located quotation of the message in full: “KICKED Caution: ‘Your connection could not be verified so your session has been terminated. All cash/XP earned this session has been saved.’ This is the 3rd game in back to back matches.” A second reply in the same thread blames the update: “its seems they broke the game with last update, keep kicking out off game mid session - connection could not be verified”. Both read from Steam's own discussion search on 2026-10-10 (docs/optimize/2026-10-10/raw/kw-research/steamsearch_connection_could_not_be_verified.html).Unverified2026-10-10
BULKHEAD · Security & Stability Hotfix notice, 2 October 2026Published at 00:13:55 UTC. BULKHEAD scheduled a hotfix for 08:00 UTC on 2 October, with one hour of expected downtime, to address minor security and stability issues affecting some players. At 09:38 UTC, the complete Steam News feed and public @WARDOGSUpdates timeline showed no start or recovery notice. The post publishes no symptoms, build number, code changes or affected-platform list.Publisher stated2026-10-02
BULKHEAD · WARDOGS Update 0.1.2, 30 September 2026Published at 06:57:06 UTC. Schedules an 08:00 UTC maintenance window estimated at one hour and publishes the complete 0.1.2 change list: a fix for the recent KB5124010-linked WD-L020 crash, named cash and XP exploit changes and enforcement, a four-way Deploy flow, browser/admin controls, stability, Havoc, buildable, throwable, crosshair and localisation fixes. The maintenance window is an announcement, not a live recovery signal.Publisher stated2026-09-30

Related