Roblox Error Code 517: The Server You Were In Shut Down
517 means the server closed while you were in it. Usually an update, sometimes a crash, occasionally a developer restarting it deliberately.
The short answer
Roblox error code 517 means the server you were playing on shut down, most often because the developer published an update that restarts all servers. It is not a fault with your connection or device and cannot be prevented from your side. Rejoining places you on a new server, and progress saved server-side against your account is retained.
Verified and last updated August 12, 2026.
- Time needed
- 7 min
- Difficulty
- Beginner
- Read time
- 2 min
517 looks like something went wrong on your end and it almost never is. The server you were on stopped existing, which is a normal thing for a Roblox server to do.
This is server-side
517 means the server ended. 277 means your connection to it dropped. Different causes, and the network troubleshooting that helps one does nothing for the other.
Why servers shut down
The first row accounts for most of it. Publishing an update in Roblox Studio restarts every running server for that experience, and games in active development do this frequently.
What to do
- Rejoin. You will be placed on a new server. This is the entire fix in most cases.
- If it happens again immediately, the developer is mid-update. Wait twenty minutes.
- Check the game's community server if it persists, since developers usually announce update windows there.
- Check status.roblox.com if it is happening across multiple games, which indicates platform maintenance rather than a single developer.
About your progress
Most Roblox experiences store progress server-side against your account and save periodically, so a shutdown normally costs you nothing.
What can be lost is progress within the current session that had not reached a save point: an unfinished round, an uncollected reward, items picked up seconds before the shutdown.
Whether that happens depends entirely on how the developer implemented saving, which varies enormously across the platform.
What does not help
Reinstalling the client, flushing DNS, changing your DNS server, adjusting firewall rules, or restarting your router. None of these touch a server-side shutdown, and all of them appear in search results for this error.
The reason they appear is that people apply generic Roblox connection fixes to every error number. The error code overview separates which fixes apply to which errors.
What works
What doesn't
Key takeaways
Frequently asked questions
Did I lose my progress?
Usually not, because Roblox experiences store progress server-side against your account and most save on a timer as well as on exit. What you can lose is progress within the current session that had not yet hit a save point, such as an unfinished round. That is a developer design decision rather than a consequence of the shutdown.
Why does this keep happening in one game?
Because that experience is being updated frequently, and every publish restarts every server. Games in active development can shut down servers several times an hour during a patch cycle. There is nothing to fix on your side; the developer is shipping changes and each one closes the running servers.
Is 517 different from 277?
Yes, and the distinction matters. 277 means your connection to the server dropped, which is a network problem and often local. 517 means the server itself ended, which is server-side and unrelated to your connection. Applying network fixes to a 517 is wasted effort.
Can I avoid it?
Not really, though joining a server that has been running for a while rather than one that just started makes no practical difference since a publish restarts all of them simultaneously. If a game is mid-update cycle, waiting twenty minutes for the developer to finish shipping is the only effective response.
About the author
Roblox & Live-Service Editor
Priya started scripting in Roblox Studio at fourteen and has since published three experiences, the largest of which passed 1.2 million visits. That background is why our Roblox coverage explains why a code fails rather than just telling you to try again later.
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.