GitHub Codespaces "503 Service Unavailable" Error
Quick answer
A 503 usually means the codespace stopped after 30 minutes of inactivity. Click Start, or reload the window.
Most likely fix: Reconnect
How to fix it
Try these in order — the most common fix is first.
1. Reconnect
- Click the Start button if it appears in VS Code or the browser
- In VS Code run "Developer: Reload Window" from the Command Palette
Did this fix it?
Symptoms
Error "503 service unavailable" when interacting with a codespace.
Why it happens
- Codespaces stop after 30 minutes without activity and you interacted with a stopped one
This guide also covers
- codespaces 503 service unavailable
- codespace 503 error
Still not working?
If GitHub Codespaces keeps failing, you're not alone. See every GitHub Codespaces problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other GitHub Codespaces errors
- Codespace Running in Recovery Mode: "This codespace is currently running in recovery mode due to a container error"
- GitHub Codespaces Creation Failed
- Can't Create a Codespace: No Option to Create on the Repository
- Codespaces "Oh no, it looks like you are offline" and Other Connection Errors
- GitHub Codespaces Port Forwarding Not Working
- Codespace Out of Storage: How to Free Disk Space
- Codespaces Included Usage Used Up: Core Hours and Storage Quota
- Codespaces Prebuild Not Working: "Prebuild Ready" Label Missing