Rust Server Status
Paste an address. We query the server itself, not a cached list.
Paste an address. We query the server itself, not a cached list.
Type the address the way your game shows it — a hostname or an IP, with or without the port. If you leave the port off we use 28015, the game's default. The check is a real query to the server from our network, so what you see is what the server answered a moment ago, not a status somebody set by hand.
If the server is one we already track, the result links to its page, where the last thirty days of uptime and player counts are waiting. That history is the difference between "it is down right now" and "it goes down every evening at nine" — and the second one is the answer that actually tells you whether to keep it on your list.
A timeout does not always mean the server is off. Some hosts block status queries while still accepting players, and a server under a DDoS may answer players and ignore queries. When we cannot reach it, the page says so plainly rather than guessing.
Because the query port and the join port are not always the same, and some hosts block status queries entirely. Try the query port if you know it. If a server is reachable for players and not for us, it is the server's configuration, not an outage.
It is what the server reported in the query a moment ago. Most servers report truthfully; a few inflate the number in their listing, which is why the tracked-server page shows a verified count separately.
Not from here — we refuse private and local addresses on purpose, because a public checker that connects to private networks is a security hole. Use a LAN tool for that.
Often enough for any real use. There is a per-hour limit that a person will not reach and a script will, and it exists so the checker stays free and fast for everyone.
Game names are used to identify what these tools calculate for. SV.GAMES is not affiliated with, endorsed by or sponsored by any publisher.