Roblox Outage History

Roblox experienced a brief outage impacting the Creator / Website component and about 4% of players for roughly two minutes. The outage began at 10:56 AM UTC and was resolved by 10:58 AM UTC, with the Roblox team identifying and fixing the underlying cause to restore normal service. The Roblox status page documented three updates during the incident: at Jun 20, 2025 6:00 PM UTC the status changed from up to down; at Jun 20, 2025 6:14 PM UTC the status moved to warn; and at Jun 20, 2025 7:04 PM UTC the status returned to up. The incident appeared to be limited in scope, with recovery achieved quickly.

Roblox experienced a brief issue impacting private server creation, with the affected area centered on the Creator / Game Join component. The incident began at Jun 7, 2025 2:19 PM UTC and was resolved by Jun 7, 2025 2:29 PM UTC, lasting roughly 10 minutes. Users attempting to create private servers or join games via private sessions may have encountered failures during that window.

The Roblox status page issued two updates during the incident: an initial note that teams were investigating private server creation issues, followed by a post indicating the Creator / Game Join component had returned to normal. The issue appeared localized to private server creation and did not indicate broader service disruption.

Roblox experienced an incident affecting login and joining for a subset of players, with 21 components across the Player and Creator ecosystems impacted (including Player Avatar, Creator Website, Games, Studio, Dashboard, Talent, Documentation, Forum, Marketplace, Asset Delivery, Data Store, Game Join, Avatar, and related mobile and website apps). The outage began at 11:29 PM UTC and was resolved by 12:54 AM UTC, lasting roughly 1 hour and 25 minutes. The Roblox status page provided updates as the situation unfolded, indicating a degradation and then a return to normal as services recovered. The incident involved multiple components and appeared to affect a broad portion of the ecosystem before full restoration.

Roblox experienced a partial outage affecting Studio and Developer Product purchasing. Users reported issues when purchasing Dev products and Studio items, with services across Creator and User domains affected (including Data Store, Game Join, Dashboard, Marketplace, Talent, Documentation, Forum, Website, Mobile Apps, Xbox Apps, Avatar, and more). The outage began on May 24, 2025 2:34 PM UTC and lasted until May 24, 2025 7:24 PM UTC, with degraded purchasing capability for several hours. The Roblox status page posted 3 updates during the incident, noting that the issue was actively being worked on and that components were gradually returning to normal. As components recovered, most services came back online by the end of the window, though some users may have experienced intermittent issues during the period.

Roblox conducted a DevForum maintenance window that temporarily degraded access to Creator / Marketplace features. The incident began at May 19, 2025 9:09 PM UTC when the Creator / Marketplace component was marked degraded as part of DevForum Maintenance. The window lasted about 55 minutes. The Creator / Marketplace component returned to normal at May 19, 2025 10:04 PM UTC. Roblox posted two status updates during the incident documenting the maintenance and the recovery.

Roblox conducted a scheduled maintenance window to upgrade the DevForum software to the newest version, affecting the Creator / Forum component. During the window, DevForum features were in maintenance mode. The maintenance began at 3:09 AM UTC and completed by 6:00 AM UTC, lasting about 2 hours and 51 minutes.

The Roblox status page reported a brief connectivity issue that prevented users from joining and accessing the platform, impacting 21 components across Player, User, and Creator surfaces (including Player / Mobile App, User / Website, Player / Avatar, Creator / Studio, Games, Avatar, Data Store, and related services). The incident began at 10:39 PM UTC and lasted about 5 minutes, with Roblox issuing two status updates during the event before services returned to normal by 10:44 PM UTC. The disruption appeared short and localized to Roblox's platform access, with no explicit regional pattern noted on the status page.

Roblox experienced a brief authentication outage that prevented sign-ins across the platform. Users attempting to log in could have encountered errors or failed sign-in attempts across web, mobile, Xbox App, and Creator tools. The issues affected multiple interfaces including User Website, Player Website, User Mobile App, Player Mobile App, Avatar, Creator Website, Creator Games, and Creator Studio, leading to a temporary login disruption.

Timeline and communication: The incident began at 10:49 PM UTC when Roblox flagged authentication issues and listed multiple components as degraded. The problem was resolved about 20 minutes later at 11:09 PM UTC, with services returning to normal. Roblox published two status updates during the incident to describe the impact and resolution.

The Roblox platform experienced a brief outage beginning at 9:29 PM UTC and resolving by 9:44 PM UTC. The disruption affected 21 components across User, Player, and Creator services, including Mobile App, Xbox App, Website, Avatar, Data Store, Studio, Documentation, Forum, and more. Users could have faced issues with logging in, game joins, and content access during the outage. The incident was short, with services returning to normal within about 15 minutes.

Roblox published 2 status updates to describe the disruption and rapid restoration of services, with all listed components returning to normal by the end of the window.

Roblox reported a brief degraded period affecting Creator tools, with issues saving places and creating assets. The incident began at 8:44 PM UTC and lasted about 20 minutes, during which Creator / Studio and Creator / Asset Delivery showed degraded behavior before returning to normal. The Roblox status page issued two updates documenting the issue and mitigation steps, and both components returned to full functionality shortly after the incident. The impact was focused on Creator-related workflows, with no broader service disruption indicated.