Error 290 is a server-side disconnect code. Unlike mid-session network errors, 290 means the server actively ended your session — either because a developer kicked you, a game script triggered a kick, or the server shut down during your session.
What does Roblox Error 290 mean?
Error 290 covers several server-initiated disconnect scenarios. The most common are: a developer or admin kicked you, a game script triggered an automatic kick, or the game server shut down and your client received a termination signal instead of a graceful disconnect code.
Kick vs. server shutdown
If you rejoin and the same server appears in the list, you were kicked (game or developer action). If the server is gone, it shut down — this is normal in Roblox and not related to your account or actions.
When it happens without reason
Error 290 with no explanation can appear when a game script has a bug that causes unintentional kicks, or when Roblox performs backend maintenance that closes servers without a graceful shutdown message. In those cases, simply rejoining resolves it.
How to fix step by step
- 1Try rejoining the same server — if available, you were kicked rather than disconnected by a shutdown.
- 2Read any kick message carefully before the dialog closes.
- 3Check Roblox status for service disruptions.
- 4If one specific game causes repeated 290 errors without clear reason, check that game's community for reports.
- 5Ensure you are not violating game rules that could trigger automated kicks.
- 6Restart Roblox if the error appears on every game.
How 290 differs from related codes
- Error 269: A game script or anti-cheat system kicked you from the server. This is a developer-triggered kick, not a Roblox platform error. (game-side)
- Error 283: You were removed from the Roblox experience by a game script or moderator. The kick included a custom message from the developer. (game-side)