Security & Stability Hotfix: scheduled window passed
BULKHEAD scheduled a security and stability hotfix for 08:00 UTC on 2 October, with one hour of expected downtime. By 09:38 UTC the estimated hour had passed, but no official start or recovery notice was visible; the post still publishes no symptoms, client build or code changes.
Read BULKHEAD’s original announcement ↗The estimated hour passed without a visible recovery post
BULKHEAD published the notice at 00:13:55 UTC on 2 October. It scheduled the hotfix for 08:00 UTC the same day and said expected downtime was one hour. The source calls that day “tomorrow, Friday 2nd”; this page uses the explicit date and UTC time rather than extending the relative wording.
This was a schedule, not confirmation that services went offline at exactly 08:00 UTC or returned at 09:00 UTC. At 09:38 UTC, the complete Steam News feed and public @WARDOGSUpdates timeline still showed no start or recovery notice. That absence does not establish live service health.
Read the dated service record and current-source checklist →Minor security and stability issues affecting some players
That phrase is the complete published scope. The announcement does not name an error code, exploit, affected feature, platform, region, server component, security vulnerability, client version or individual fix.
It therefore does not establish that a particular crash, kick or connection problem is caused by this issue, and it does not supersede the specific Update 0.1.2 notes unless BULKHEAD publishes a later connection between them.
Read the separately documented Update 0.1.2 changes →The estimate expiring is not a recovery signal
The one-hour figure was an expectation, not a promised end time. With no timestamped start or recovery post visible at 09:38 UTC, this site cannot say whether the work ran, finished, was delayed or changed live service. Check Steam announcements, @WARDOGSUpdates, @WARDOGS or official Discord for a newer instruction.