Roblox users across Russia reported a fresh wave of connection problems on August 25, according to complaint-tracking service Downdetector. Over 660 reports piled up within a single hour, reviving worries the platform might face another shutdown just months after its last one.
Roblox Outage Hits Russian Players Again on August 25
What the Downdetector Data Shows
Downdetector logged 662 complaints from Russian users in the hour before the report went out. The breakdown: 86% described a general outage, 7% pointed to the mobile app, 5% flagged the website, and less than 1% reported issues with a specific in-game service.
Complaints came in from the Leningrad and Chelyabinsk regions, St. Petersburg, and the Republic of Bashkortostan. No official statement from Roblox addressing the cause has surfaced yet.
Not the Same as the December Block
Worth separating from a fresh ban: this is not a repeat of the shutdown that hit Roblox in December 2025. That block was lifted on June 10, 2026, after the company said it had fully complied with Russian legal requirements and pledged to crack down on the kind of content that triggered the original restriction.
Given that history, any hiccup on Roblox’s servers tends to spark immediate speculation about another ban. Nothing in today’s reports points to a renewed official restriction — the pattern so far looks like a standard service disruption rather than a regulatory action.
What to Watch
Neither Roblox nor Russian authorities have issued a statement explaining today’s spike in complaints. Until an official cause turns up, treat this as an unresolved outage rather than confirmation of anything more serious, and check Downdetector before assuming your own connection is the problem.
Similar mass outages have hit other platforms recently — Runet experienced a wide-reaching disruption just a week earlier, and ChatGPT went down in July, suggesting this kind of instability isn’t unique to Roblox.
Roblox is experiencing a fresh technical outage in Russia on August 25, with no confirmed link to a new block. Hang in there — service should stabilize once the issue gets sorted.
