On screen: Same account launched experience from different devices
People land on this error while searching whether the service is down. It is not. This code cannot be produced by an outage, so no amount of waiting will clear it.
This is an account-state code and cannot be produced by a Roblox outage. We are not going to show you a live tracker and imply it might be.
Roblox's explanation: error code 264 occurs when the same account attempts to access the same game from multiple devices simultaneously. The engine name for it is DisconnectDuplicatePlayer, which says the same thing more plainly.
So the platform is working correctly. It is doing exactly what it is designed to do — refusing a second simultaneous session.
Which raises the question most pages never ask: if you are not on a second device, who is?
Close Roblox everywhere — every device, every browser tab. If the error stops, it was a duplicate session, often a tab you forgot. If you are certain nothing else of yours is signed in and it keeps happening, somebody else has your account. That is the real finding here.
Operator documentation: en.help.roblox.com. One thing to know about Roblox's own articles for this family of codes. We compared them and the sections after “select your operating system” are byte-for-byte identical across codes 264, 266, 268, 277, 279 and 280 — the same reinstall, clear AppData and call your ISP sequence. Only a one-to-three line paragraph differs. So the official answer is close to the same for six unrelated problems, which is why the causes below matter more than the steps. For 264 that template is actively unhelpful: reinstalling Roblox and clearing AppData have no bearing on a duplicate login, and nor does your internet provider.
Roblox's explanation: error code 264 occurs when the same account attempts to access the same game from multiple devices simultaneously. The engine name for it is DisconnectDuplicatePlayer, which says the same thing more plainly.
People land on this error while searching whether the service is down. It is not. This code cannot be produced by an outage, so no amount of waiting will clear it.
Start with: Close Roblox on every device and tab. Including a browser tab left open on another machine. This resolves the ordinary case.