- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 38m it lasted.
Anything that failed between 2026-02-16 18:21 UTC and 2026-02-16 19:00 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 2
- identified
The issue has been identified and a fix is currently being deployed. We are working to restore command functionality immediately.
provider
- resolved
A fix has been deployed and commands are fully restored. If you still encounter issues, please reset your conversation or restart the environment to apply the changes
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-4822d44622
Is Gitpod still down?
No, this incident was resolved 2026-02-16 19:00 UTC. For Gitpod's live state, see https://down.guide/gitpod.
How long did it last?
38m, from 2026-02-16 18:21 UTC to 2026-02-16 19:00 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.