- Level
- confirmed
- Worst impact
- Maintenance
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.Check that everything you run on RunPod came back after the window closed 2025-11-27 22:28 UTC.
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 1
- resolved
We will be performing a planned failover for CA-MTL-4 ISP connections in order to perform firewall firmware upgrades. Internet connections may be reset during this period. Internal workloads and networking will not be impacted.
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-02ed89a174
Is this RunPod maintenance still going on?
No, it ended 2025-11-27 22:28 UTC.
How long did it last?
0m, from 2025-11-27 22:28 UTC to 2025-11-27 22:28 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.