Roblox Adds 30-Day Server History to Server Management

Server Management previously removed a server from view as soon as it stopped. The new rolling history preserves terminated-server evidence and normally adds a stopped server within about a minute, without requiring game-code changes.

Updated: 2026-08-04

Roblox Adds 30-Day Server History to Server Management

Each server is labeled Active, Shut down, Restarted, Roblox Restarted, Crashed, Out of Memory or Moderated. Terminated rows add the stop time and total uptime, while occupancy, framerate and memory show the last known values from up to 30 seconds before termination.

Creators can filter any combination of statuses and sort by uptime, start time or status to isolate short-lived servers and clusters of failures. Creator Hub hides terminated servers by default; the existing ListGameServers Open Cloud endpoint now returns status, terminationTime and uptime and accepts a server_status filter.

Why it matters

The history closes a major observability gap: teams can investigate crashes, memory exhaustion and unexpected restarts after the live server disappears, while retaining access to its details and logs for 30 days.

Key details

Rolling 30-day server history.
Seven active and termination statuses.
Creator Hub and existing Open Cloud API.

Roblox Adds 30-Day Server History to Server Management

Why it matters

Key details

Sources