Rust Server Status Checker

Why Check Rust Server Status?

Rust servers can experience wipes, restarts, maintenance, and unexpected crashes. When a server is down, players cannot connect and progress is temporarily halted. For competitive players and clan members, every minute of downtime means missed opportunities, lost loot, and the risk of losing hard-won base territory.

Checking server status helps players and administrators quickly see whether a server is reachable before attempting to join, saving time and frustration. It is also useful for content creators planning streams, raid coordinators verifying availability before scheduled raids, and server admins responding to player reports of connection issues.

Common Reasons a Rust Server Goes Offline

Rust servers are notoriously resource-hungry and prone to a unique set of failure modes. Knowing the most common causes helps you diagnose issues quickly:

• Scheduled wipes: Most Rust servers wipe weekly, biweekly, or monthly. During wipe day, the server may be offline for an extended period as the world regenerates and players cannot connect until the wipe is complete.
• Memory exhaustion: Rust uses massive amounts of RAM, especially with large player counts and many bases. When the server runs out of memory, it crashes or becomes unresponsive.
• Plugin or mod incompatibility: A recent update to Rust or to an Oxide/uMod plugin causes a crash on load. Common after monthly Rust updates from Facepunch.
• Update mismatch: Facepunch released a new Rust client version but the server has not been updated yet. Clients on the new version cannot join.
• DDoS attack: Popular PvP servers are frequent DDoS targets, especially during peak hours or competitive events.
• Save file corruption: A hard shutdown corrupted the server save, and the server fails to load on restart.
• Hosting provider outage: Game hosting services occasionally experience network or hardware issues affecting all customers on a node.
• Manual restart that did not finish: An admin restarted the server for an update but the start script failed silently — common after manual configuration changes.
• Cheat detection rebuild: The server is temporarily offline while EAC (Easy Anti-Cheat) restarts after detecting suspicious behavior.

Diagnosing Connection Problems

When you cannot connect to a Rust server, work through this checklist:

• Use this tool to check from outside. If the server responds externally, the problem is on your end — likely your client, your network, or your router.
• Verify the IP and port are correct. Rust uses port 28015 by default. Custom servers may use other ports — check the server's announcement or website.
• Check your Rust client version. If Facepunch just released an update, your client and the server may be on incompatible versions. Wait for the server to update or update your client.
• Restart your Rust client. Background corruption sometimes prevents new connections without giving a useful error.
• Check Steam status. Rust authentication depends on Steam being online. If Steam is having issues, you cannot join any Rust server.
• Disable VPN or proxy temporarily. Some Rust servers block VPN connections, and EAC sometimes flags VPN traffic as suspicious.
• Check the server's official Discord or status page. Most popular communities post updates about wipes, downtime, and restart schedules.
• Wait if it is wipe day. If the server is in the middle of a scheduled wipe, the only solution is to wait until the wipe completes.

Continuous Monitoring for Rust Server Owners

Rust server admins know that every hour of unexpected downtime means players migrating to competing servers and never coming back. Continuous monitoring is essential for any server with an active community.

With UptyBots, you can configure a port-based monitor for your Rust server that:

• Connects to your Rust server's port every 1 to 5 minutes.
• Verifies the server actually responds to a connection request.
• Sends instant alerts via email, Telegram, or webhook when the server goes down.
• Tracks long-term uptime that you can publish to your community as a real reliability metric.
• Provides an embeddable status widget for your server's website or Discord.

For competitive Rust servers and large communities, the difference between knowing about an outage in 30 seconds versus 30 minutes is the difference between a quick recovery and losing players to competing servers.

Frequently Asked Questions

What is the default Rust server port?

The default Rust server port is 28015. Some hosting providers use custom port ranges, in which case you need to specify the port explicitly when connecting (for example, example.com:28017).

Why does the server show offline during a wipe?

During a wipe, the server is typically taken offline for several minutes while the world regenerates and the save file is reset. This is normal and expected. Most communities announce wipe schedules in advance — check your server's Discord or website for the next planned wipe.

My Rust client cannot connect even though this tool says the server is online. Why?

The most common causes are: your client is on a different version than the server (after a Rust update), Steam authentication is having issues, your antivirus is blocking the connection, or the server has banned your account or IP. Try restarting your Rust client, restarting Steam, and verifying your client is fully updated.

Is this checker free?

Yes. The Rust Server Status Checker is completely free, with no signup or limits. For continuous monitoring with alerts and long-term uptime tracking, sign up for a free UptyBots account.

Can I use this for modded Rust servers?

Yes. The checker connects at the network level and works for vanilla, Oxide/uMod, and Carbon servers identically. Modifications do not affect whether the server responds to a connection check.