- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 100
What to do
Check whether your product depends on RunPod. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 9m it lasted.
Anything that failed between 2025-10-02 14:34 UTC and 2025-10-02 17:43 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 2
- update
We are experiencing intermittent connectivity issues to our upstream that is impacting calls to Runpod APIs and Console. We working on resolving this issue.
provider
- resolved
Issue has been resolved. We've been monitoring the situation and it is operating normally.
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-ae7ba22b6b
Is RunPod still down?
No, this incident was resolved 2025-10-02 17:43 UTC. For RunPod's live state, see https://down.guide/providers/runpod.
How long did it last?
3h 9m, from 2025-10-02 14:34 UTC to 2025-10-02 17:43 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.