Is ROB RUN Down? How to Check Servers and Maintenance
How to tell a ROB RUN outage from a local problem: there is no status page, so check Kefir's posts, the maintenance screen and the error code before reinstalling.
How do you check if ROB RUN is down?
There is no status page. The official channels are Kefir’s X account (@ROBRUNGame), its Discord and the pinned posts in the game’s Steam discussions. If none of them mentions an outage, assume the problem is on your side and work through the connection checks below.
The Steam player count is not a status indicator. It shows how many clients are open, not whether the servers accept new connections — a game can show six figures of players while your region is refusing logins.
What has actually gone wrong so far?
Three distinct kinds of downtime, and they need different responses:
| Incident | What it looked like | What to do |
|---|---|---|
| DDoS attacks, confirmed by Kefir on 7 November 2026 | Connection errors, lag, disconnects, long queues | Wait it out; do not reinstall |
| Scheduled maintenance | Full-screen “game is temporarily unavailable” message with a Quit button | Wait 15 minutes to an hour |
| Server crash with a rollback | Progress or items missing after a reconnect | Check the wipe first, then contact support with your UID |
| EU-only login failure, 14 November 2026 | EU players could not log in or stay connected; US unaffected; restart announced at 23:20 CET | Check the region before anything else |
The 14 November incident is the one worth remembering, because it isolates the variable. Kefir’s post named EU servers specifically for login problems and instability, said the US was unaffected, and then announced a restart that evening. If EU is broken and East US is fine, the fault is regional and nothing on your PC caused it — and nothing on your PC will fix it.
Kefir’s 7 November statement was unusually direct: servers had been under repeated attacks since the previous night, causing connection errors, lag and other in-game issues, and the team said it was doing everything it could to stabilise them. It closed with a promise to keep players updated.
A follow-up status post added two details worth knowing. Server conditions had improved considerably but were not fully resolved, and the crashes had produced progress rollbacks and duplicated items. No patch date for the connection problems has been published.
Maintenance is not a wipe. Your server keeps its seven-day clock and your plot keeps its contents. The wipe is a separate event: the Federal Raid, seven days after your server opened.
How do you tell their outage from your problem?
Three quick tests, in order:
- Does the Steam store page load? If Steam itself is unreachable, the problem is upstream of ROB RUN.
- Does the game reach the server and fail, or fail before that? An error code such as E-0101 or E-0110 means the client cannot download startup data. A freeze at “compiling shaders” usually means the client is waiting on something it cannot get.
- Are other players reporting it right now? The Steam discussions and the Discord are the fastest crowd-sourced signal. One player with a problem is a local issue; twenty in ten minutes is an outage.
Then ask which region. A failure that only hits EU or only hits East US is Kefir’s problem, and asking in Discord which region is failing separates it from a bad local route in one sentence. The 14 November incident was exactly this shape.
If all three point outward, stop troubleshooting your PC. The errors and fixes guide has the code-by-code table if the symptom is specific rather than general.
What should you not do during an outage?
- Do not reinstall the game. It costs an hour of download and fixes nothing that a server-side problem caused.
- Do not download third-party “fix” tools. Easy Anti-Cheat is kernel-level and Kefir’s rules treat cheating tools as a permanent ban, even when the tool was sold as a launcher fix.
- Do not delete your shader cache as a first step. It is a legitimate later step for a genuinely local stutter problem, not an outage fix.
- Do not switch servers to escape the lag. Surrendering to the feds clears your progress on the current server, which is a much bigger loss than an evening of queueing.
What if the server rolled your progress back?
A rollback is not the same as a wipe, and the order you check things in decides whether you lose an evening or a cycle:
- Check whether a wipe has happened. Every server wipes seven days after it opens, and a wipe is not reversible. The wipe timer turns your server’s opening date into a countdown.
- Check that you are on the same server and the same Steam account. Progress does not follow you between States.
- Check whether the missing thing was ever banked. Cash carried in a bag can be lost in a disconnect; cash in the Looty Bay Bank is protected until the wipe. That is the practical argument for laundering early rather than at the end of a run.
- Contact support with evidence. Kefir’s lost-progress FAQ asks for your UID first — press Esc, it sits on the right under your character name with a Copy UID button — plus your player name and the approximate time. The address on the help centre is
[email protected].
Items duplicated by a crash are the other half of the same bug. Kefir has acknowledged them; do not treat a duplicated crate as a windfall worth planning around, because a rollback can remove it again.
What can you do while the servers are down?
Plan the next session instead of refreshing the launcher:
- Check where your server is in its wipe cycle, so you know whether the downtime cost you a day or an hour.
- Read the patch notes for anything that changed since your last session.
- Decide what to sell and what to launder first; both are decisions better made off the clock.
- If you are new, read the beginner guide rather than learning the map under fire.
When is downtime a bug report?
Report it when the outage is over and the problem stays:
- You can log in but one character or one base is missing.
- Your bank balance does not match what you remember, and no wipe has happened.
- A specific error code repeats after a full restart, file verification and a different network.
Support needs your UID, your player name and the approximate time. Send the error code, your CPU and your graphics card as well; a screenshot or short clip of the steps before the failure is worth more than a paragraph of description.
Server regions, daily opening times and how to switch are in servers and playing with friends.
Related Articles
guides
ROB RUN Errors and Fixes: Loading, E-Codes, EAC, FPS
Fix the ROB RUN problems players actually hit: stuck loading, 'waiting for status information', E-0101 to E-0904 error codes, Easy Anti-Cheat failures and low FPS.
guides
ROB RUN Servers and Playing With Friends
ROB RUN servers explained: EU and East US regions, a fresh server daily at 17:00 UTC and 20:00 ET, how to switch region, and how to meet friends on one server.
guides
ROB RUN System Requirements and Platforms (2026)
ROB RUN runs on Windows through Steam only. Minimum and recommended specs, no Mac or Steam Deck support, and what Early Access means.
Was this helpful?
Thanks for the feedback!