What the exact error tells us
The Steam discussion started on November 5 records players getting stuck on “Waiting for status information” and then returning to the map. Replies associate the problem with restarts and lengthy waits. That is evidence of a shared symptom, not a technical diagnosis of your own connection. This guide has not reproduced the error and cannot confirm what happens inside the server during that screen.
Separately, a pinned developer post acknowledged repeated DDoS attacks causing connection errors, lag and other in-game problems during launch week. It gives a documented server-side incident context. It does not establish that every later status-information hang is caused by DDoS, or that an old attack is still active when you read this page. The distinction matters before changing local files or network settings.
First check the dated official discussion
Open the pinned developer discussion and official Discord linked below. Look for a newer announcement that names your symptom, region or maintenance window. The timestamp is more useful than a generic “servers are down” headline. This site has no live server probe, so the historical incident box on the homepage is not a current availability test.
If you post a report, record the exact wording, time, region, destination world and whether the game returns to the map. That is editorial reporting advice rather than a developer-approved fix. It helps distinguish the loading gate from a crash, low frame rate or a problem entering only your base. Avoid posting login tokens, passwords or other account secrets in a public reply or screenshot.
What we will not label a fix
There is no confirmed registry edit, DNS change, VPN service, reinstall sequence or cache-deletion recipe in the research for this exact message. A generic Steam checklist is not equivalent to a tested solution. In particular, repeated reinstallation is not supported by the evidence as a way around a server-side incident. We do not offer a downloadable patch or a paid “unlock” tool.
The source file includes generic client checks, explicitly not from Kefir. If you independently investigate local problems, keep that limitation clear. Meeting Steam’s requirements is a separate check: the minimum includes 12 GB RAM and a GTX 1050 Ti, RX 580 or Arc A380. Hardware requirements do not prove a cause for this specific message, and a high-end PC does not prove the servers are healthy.
How to use this launch-week evidence
The research snapshot for this guide was compiled on November 9, 2026, after Early Access began on November 4. Official announcements establish what Kefir has said; a forum reply establishes what one player reported. A symptom appearing in both places does not prove that every affected machine has the same cause. We keep the two kinds of evidence separate so you can decide what the next check should be.
No real-time server probe or in-game reproduction runs on this website. An old incident is not proof of an outage right now, and a reply saying that one person got back in is not proof that all regions recovered. Use the linked official discussion and community channels for newer announcements. If you report your own case, include the time, region, server identifier and exact message rather than treating this dated summary as a live status indicator.
What if money disappears after a disconnect?
Players in the same discussion described being kicked to the map and losing money, including uncollected police salary. No confirmed restoration process or compensation commitment was found. Use the dedicated lost-money page to prepare a report, not to follow an invented recovery button. Keep the connection error and the balance change as separate observations when describing the incident.
Waiting and checking for a newer official update is the conservative response to a documented server incident, but there is no verified wait duration. A player’s two-hour delay is not a service-level promise. If you get back in, that establishes only your own successful entry at that moment. We will update the guide when a supported fix exists rather than turn an anecdotal retry into a guaranteed troubleshooting method.