Is Rust Console Down, or Is It Just Your Server? Outage vs Bot Triage

Start with the one test that saves you an hour

There is a single check that collapses the whole "is Rust Console down right now" panic into one yes-or-no answer: can anyone actually join your server this minute? Have a player, or your own second account, open the community browser (Y on Xbox, Triangle on PlayStation) and try to connect.

If they join and play normally, Rust Console is not down and your server is up. Your problem is your tools, almost always the bot's connection, and you can skip straight to the bot layer below. If they cannot join your server but can join others, it is your server or host, not the platform. If nobody can join any server at all, you are looking at a platform-wide outage and nothing on your end will fix it.

That one test tells you which branch you are on. Everything else in this post is just confirming the branch and knowing what to do once you are there.

Layer 1: Is Rust Console actually down?

Rust Console Edition is a Facepunch title, so a true outage is a platform event, not something hiding in your server config. Check these in order.

First, the official Rust Console Edition social accounts and Discord. Patch notes, known-issue posts, and "servers are coming back up" messages land there before anywhere else. Second, whether other owners are reporting the same thing at the same minute. A wave of "rust console servers not working today" posts appearing across communities within a few minutes of each other is the clearest outage signal you will get. Third, your platform's own status: PlayStation Network and Xbox Live. If PSN or Xbox is having a bad day, players cannot reach any game, and from your seat that looks exactly like Rust being down.

If every sign points to a genuine outage, the honest move is to tell your players it is platform-side and wait. Restarting your server or bumping gather rate will not bring a Facepunch backend back online.

Layer 2: Your server is up, but your bot went quiet

This is the most common case by far, and the most misdiagnosed. Players are on your server building and fighting fine, but your killfeed stopped, kit commands do nothing, and events will not fire. The game is healthy. The bot's connection is not.

Remember what the bot actually connects to: your server's IP, the RCON port (commonly 28016, a TCP and WebSocket port) and the RCON password. That is a separate door from the game port players walk through (28015, UDP). Players getting in through the front door tells you nothing about whether the bot's door is open. If you have never mapped that out, the difference between the RCON port and the game port is worth five minutes.

A quiet bot on a live server almost always means one of four things: the RCON connection dropped and has not reconnected, rcon.web got flipped off when it needs to be 1, the RCON password or port changed under you, or the host rebooted. If the bot goes quiet like this on a regular basis, that is a pattern with its own fixes, and it is worth understanding why a Rust Console bot keeps dropping rather than restarting it over and over.

Layer 3: Is it your host, not the game?

G-Portal and Nitrado are the two official hosts, and both have maintenance windows and the occasional bad day. Two host-side situations look like an outage but are not.

The first is scheduled or emergency host maintenance. Your server goes briefly unreachable, players cannot join, but Rust itself is fine on other servers. Check your host panel's status page. The second is a patch-day reboot, which catches everyone, so it gets its own section next.

The tell is simple. If players can join other servers but yours is dead, and your host panel shows the server stopped or restarting, that is your answer. It is a host event, not Rust Console going down.

The patch-day pattern (why your bot dies every Thursday)

Here is the sequence that fools most owners. Facepunch ships an update. G-Portal auto-updates and reboots your server to apply it. For a few minutes the server is offline, then it comes back, but your bot is still pointed at a connection that dropped during the reboot. Players trickle back in and everything looks normal to them, while your killfeed and commands stay dead until the bot reconnects on its own.

Wipes make this worse, because forced updates and wipe reboots often land together, usually weekly and commonly Thursday around 18:00 UTC. The signature is unmistakable: your bot went quiet at the exact minute of a known patch or scheduled restart, and the server itself is up.

A bot that handles reconnection cleanly rides straight through this without you noticing. One that goes silent every time is a fixable problem, not a fact of console life, and it is a close cousin of a bot that stops working after a restart. This is the one place worth being picky: Vantic is built to reconnect itself after a patch reboot so wipe day does not turn into a bot-babysitting shift.

Layer 4: "Server not responding" and what it usually means

When you or a tool reports that the server is not responding, that phrase almost always points at the RCON connection, not the game. Run this short list top to bottom.

Is the server actually running? Check the host panel first, because a stopped or crashed server beats every other theory. Right port? The bot needs the RCON port, often 28016, not the game port 28015, and mixing them up is the single most common first-connection mistake. Is rcon.web set to 1? Some hosts need web RCON explicitly enabled. Did the password or IP change? A host migration, a new instance, or a reset can quietly change any of them. And did a setting fail to persist? Convars pushed live over RCON do not survive a restart unless they are written to config with server.writecfg, so if something worked yesterday and reset overnight, that is why.

If you are setting a bot up for the first time and it simply will not link at all, that is a different track from an outage, and the WebRCON connection troubleshooter walks it end to end.

One more lookalike: "my server vanished from the browser"

Worth naming because it panics owners the same way. If your server disappeared from the community browser but the bot is still connected and players who favorited it can join, the game is not down and your server is not dead.

The console browser has a ping-based cap of roughly 5,000 servers and a Show-Empty filter, and a freshly booted server can take up to about 15 minutes to reappear after a restart or wipe. The name must be kept under about 60 characters or the listing misbehaves. That is a visibility quirk, not an outage, and it resolves on its own once the browser catches up.

Frequently asked questions

Keep reading

Why your Rust Console bot keeps disconnecting · Bot stops working after a server restart · WebRCON won't connect: the first-time setup fix · Server not showing in the community browser · RCON port vs game port, explained