- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on RunPod. 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 4h 41m it lasted.
Anything that failed between 2026-05-08 17:08 UTC and 2026-05-08 21:49 UTC may need a replay.Subscribe to RunPod's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=runpod works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from RunPod 3
- update
We are experiencing increased times for Pods to start along with console logs not being displayed. We are investigating the issue and will provide an update once we have more information.
provider
- update
We've identified the issue and are working to incorporate the fix.
provider
- resolved
The issue has been resolved. Functionality for pod starts and display for logs on the console have returned to normal.
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-40a453f7c8
Is RunPod still down?
No, this incident was resolved 2026-05-08 21:49 UTC. For RunPod's live state, see https://down.guide/runpod.
How long did it last?
4h 41m, from 2026-05-08 17:08 UTC to 2026-05-08 21:49 UTC, by the times RunPod posted.
What caused it?
RunPod hasn't published a root cause. If it does, it shows here.
Where does this come from?
RunPod's official status page, https://uptime.runpod.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.