- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Gitpod. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 57m it lasted.
Anything that failed between 2026-03-24 12:50 UTC and 2026-03-24 13:47 UTC may need a replay.Subscribe to Gitpod's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=gitpod works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Gitpod 3
- investigating
A small group of customers is experiencing issues starting new environments - existing environments are able to start. We are investigating the root cause.
provider
- monitoring
We've rolled back to the prior stable release as a mitigation, and confirmed that new environments are able to start. AWS Runners will pickup the change in the next 5m. After waiting, please try creating new environments again.
provider
- resolved
The rollback was successful. Users are able to start new environments after the Runner auto-updated.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-37b5d0dfdf
Is Gitpod still down?
No, this incident was resolved 2026-03-24 13:47 UTC. For Gitpod's live state, see https://down.guide/gitpod.
How long did it last?
57m, from 2026-03-24 12:50 UTC to 2026-03-24 13:47 UTC, by the times Gitpod posted.
What caused it?
Gitpod hasn't published a root cause. If it does, it shows here.
Where does this come from?
Gitpod's official status page, https://onastatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.