Skip to main content

Work out which Rust worlds are affected before restarting

When an outage report says ‘Rust is down’, find the world and the failed action first. Compare the same action on another world. A management dashboard, a browser listing and a player join can fail separately.

Check each named world once

Write the time and use the same outside network for both worlds where possible. If you cannot reach a console, mark it unchecked. A blank cell should never be read as a failure.

Check each named world once
Read-only checkIf it fails
Direct join to the documented game addressCheck another world and, if available, ask a second network to test the affected address.
Rust browser listing with the usual filtersIf direct join works, investigate discovery or filters first.
Existing private console or hosting panel shows the current gameIf a tester can play, keep the game running while you check the management route.
Host reachable through the existing provider or local controlsIf both of its worlds fail from several networks, check host or network status before treating the games as separate crashes.

Name the affected world in the update

For example, ‘Harbor Weekly direct joins fail from two networks. Harbor Monthly still accepts joins. Weekly is missing from the list; Monthly appears normally.’ Give staff the time and one next observation. If both worlds share a host, say that too. Keep a working world open while the checks point to a narrower failure.

Confirm the user-facing result before closing the incident

When the failed path returns, repeat the original test from the outside network and verify the comparison world still works. Update the incident with the action that now passes. If the evidence still only proves a management panel failure, tell players about the game connection you actually tested.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details