- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 41of 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 1h 40m it lasted.
Anything that failed between 2026-04-22 18:46 UTC and 2026-04-22 20:25 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
We are aware of an issue impacting Ona conversations, where the agent is not responding. Old environments will continue to work, but new agent conversations will not. We are investigating.
provider
- monitoring
We have applied a fix and are currently monitoring the situation. Please note that any previously unresponsive conversations will need to be reset.
provider
- resolved
Conversations start normally again.
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-9b33da72a5
Is Gitpod still down?
No, this incident was resolved 2026-04-22 20:25 UTC. For Gitpod's live state, see https://down.guide/gitpod.
How long did it last?
1h 40m, from 2026-04-22 18:46 UTC to 2026-04-22 20:25 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.