- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 11m it lasted.
Anything that failed between 2026-04-17 08:40 UTC and 2026-04-17 10:51 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
- identified
We're seeing issues starting new Ona conversations. Not all conversations might be impacted. We identified the issue and are on track to fix it.
provider
- monitoring
We deployed a fix and are monitoring. New conversations should work as expected.
provider
- resolved
The issue has been fully resolved and we haven't observed disrupted conversations in the last hour.
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-9b5c7b116a
Is Gitpod still down?
No, this incident was resolved 2026-04-17 10:51 UTC. For Gitpod's live state, see https://down.guide/gitpod.
How long did it last?
2h 11m, from 2026-04-17 08:40 UTC to 2026-04-17 10:51 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.