ROB RUN guides
Short, practical pages for the problems players actually hit: connection failures, the wipe, regions, and the infamous status-information screen. No filler, no invented server data.
Can't get into ROB RUN? A six-step connection check
Before blaming the servers, eliminate the six most common client-side causes: Steam cache, VPN routing, DNS, the game's own integrity, Steam itself, and your region.
Read the guideROB RUN regions: EU, East US, and the missing Asia server
ROB RUN ships with two official regions. Here is what that means for latency, for choosing a state, and for the persistent question about an Asian server.
Read the guideDid your ROB RUN state wipe? Reading the Federal Raid correctly
Woke up in prison with an empty base? Here is how to tell a Federal Raid from a restart, what Kefir actually wipes, and what to do next.
Read the guide'Waiting for status information' in ROB RUN — what it means
The screen that sits between the menu and the game is usually a client handshake problem, not an outage. Six steps that resolve it, in order.
Read the guideHow the verdict is computed
One-hour baseline, a 35% / 60% drop ladder, report bursts, and a three-sample recovery rule. Every threshold and every blind spot is written down.
The Steam Web API exposes a single number for the whole game: players online right now. Steam's News API exposes developer announcements. The third input is what visitors report on this site. Nothing else is public — not per-server health, not queue depth, not regional latency.
A Cloudflare cron reads the player count every five minutes and stores it with the exact observation time. Failures are stored as unavailable, never as zero. A reading older than thirty minutes is not used to claim anything about the present.
The baseline is the mean of successful samples taken 60 to 120 minutes before the latest reading. A drop of 35% or more is published as degraded; 60% or more is published as a suspected outage. A zero reading is published as an unconfirmed outage, because Steam occasionally returns zero while rebuilding its cache.
Anonymous reports are counted in fifteen-minute windows. More than 25 in a window, or three times the three-day average, pushes the verdict to at least degraded. The note text is never published verbatim, and the IP is only hashed for rate limiting.