Roblox Outage History

Roblox players experienced a brief login disruption that caused unexpected sign-outs during gameplay. Reports surfaced around 21:30 UTC and surged by 21:45 UTC, with players in North America and the Netherlands reporting being logged out and prompted to sign back in. The outage lasted about 10 minutes, beginning at 9:43 PM UTC and ending at 9:53 PM UTC.

StatusGator detected the issue at Jan 26, 2026 9:43 PM UTC, ahead of any Roblox status page acknowledgment. There were no publicly observed Roblox status updates during the event. The incident appears to have been a brief login/authentication disruption affecting players across multiple regions.

The Roblox outage disrupted gameplay for players worldwide, with reports of being unable to join games, getting returned to lobbies, or experiencing loading failures. The disruption began at 7:24 PM UTC and lasted about 1 hour and 22 minutes, ending around 8:46 PM UTC. StatusGator detected the issue at Jan 24, 2026 7:24 PM UTC, ahead of any Roblox official updates. There were no public status updates from Roblox during the incident, and user reports surged around 8:15 PM UTC as the impact spread across regions.

A brief Roblox server incident caused Roblox games to freeze and fail to load for players. Reports from the United States indicate the issue affected gameplay stability, with impact concentrated on the East Coast. The outage lasted about 2 minutes, beginning at 2:37 AM UTC and ending by 2:39 AM UTC.

Roblox Studio experienced transfer issues affecting uploads and downloads of some place files, likely causing errors when saving or loading assets. The problem affected two Roblox components: Creator / Studio and Creator / Asset Delivery, and Roblox began investigating. The outage began at 10:24 PM UTC and was resolved by 11:24 PM UTC.

During the incident, Roblox published two status updates outlining the investigation and eventual resolution. The incident was brief, lasting roughly an hour and focused on file transfer operations rather than broader Roblox services.

Roblox DevForum underwent a scheduled maintenance window that affected the Creator / Forum component. Users may have experienced limited access to DevForum features during the window. The maintenance began at Jan 14, 2026 4:09 AM UTC and was completed by Jan 14, 2026 5:34 AM UTC, lasting about 1 hour 25 minutes. The maintenance window was announced as DevForum maintenance from 8:00 PST to 10:00 PST on January 14. During the incident, Roblox issued two status updates on the DevForum status page to indicate the maintenance and subsequent restoration. User reports were limited, indicating this was a targeted maintenance window rather than a widespread outage.

The Roblox website and mobile app were unavailable, preventing players from accessing games, joining sessions, or using social features. Users across regions reported crashes, failures to load content, and avatars not displaying in some cases. The disruption began at Jan 8, 2026 2:44 AM UTC and lasted until Jan 8, 2026 3:43 AM UTC, for a duration of about 1 hour and 59 minutes, indicating a global impact.

Roblox experienced a global outage beginning at 6:34 AM UTC that prevented players from loading games, joining sessions, or preserving in-game progress. Reports described server connection issues and data loss across many titles, with players worldwide affected.

The outage persisted for about an hour and was resolved by 7:34 AM UTC. StatusGator detected the issue at Jan 6, 2026 6:34 AM UTC. There were no official Roblox status updates published during the incident. The surge in user reports across regions indicated a broad impact, though some games may have recovered gradually toward the end.

Roblox faced a brief degraded experience affecting players trying to join experiences across its platforms. A handful of user reports described trouble joining experiences on the Player Website, Mobile App, Xbox App, and the Creator tools. The incident began around 4:30 PM UTC. Roblox issued a status update at 5:34 PM UTC noting issues joining experiences and listing affected components (Player Website, Player Mobile App, Player Xbox App, Player Games, Creator Games, Creator Website). A second update at 5:44 PM UTC indicated the service was returning to normal. The disruption affected six Roblox components and lasted about 1 hour and 14 minutes.

The outage began on Dec 19, 2025 4:54 AM UTC and was resolved by Dec 19, 2025 10:04 AM UTC. Roblox faced a platform-wide disruption preventing access to Roblox.com and related services. The outage affected six components including Player Website, Creator Website, User Website, and related game services, causing login failures and pages failing to load with errors such as Service Instances Unavailable (Error 9007). The incident produced widespread reports from users around the world and blocked core functionality such as joining games and loading content.

Status updates tracked the incident as it evolved, with Roblox moving from a full outage to degraded performance around Dec 19, 2025 8:54 AM UTC and back to normal by Dec 19, 2025 10:04 AM UTC. Roblox issued 3 status updates during the incident. StatusGator detected the issue at Dec 19, 2025 4:32 AM UTC, {{time:22}} minutes before Roblox acknowledged the problem.

Roblox users were unable to access the platform and participate in games as a broad outage affected 22 components across Creator, User, and Player services, including Creator Forum, Marketplace, Avatar, Game Join, Talent, Documentation, Dashboard, Asset Delivery, Data Store, and mobile/Xbox apps. The disruption prevented logins, game joins, and loading content, with reports from users across North America, Europe, and Oceania indicating a global impact. The outage lasted about 10 minutes, from 11:54 PM UTC to 12:04 AM UTC.

Roblox's status page documented the incident with two updates. StatusGator issued an Early Warning Signal at Dec 11, 2025 11:17 PM UTC, ending at 11:56 PM UTC, reflecting a period of user reports preceding official acknowledgment by about 37 minutes. The outage affected multiple components across Creator, User, and Player services, and was resolved quickly as Roblox restored services.