- Level
- confirmed
- Worst impact
- Maintenance
- Regions
- us
What to do
Check whether you use RunPod in us. 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 2026-04-25 17:49 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
Key Maintenance Details Date: April 28, 2026 Time: 1:00 PM – 6:00 PM PST Location: Datacenter US-CA-2 Scope: Network infrastructure upgrades specifically targeting storage system connectivity. Impact Assessment Service Interruption: Expect downtime or intermittent connectivity for systems residing within this datacenter during the four-hour window. Specific Notifications: Not all machines may be affected. Check your system-level dashboard for individual maintenance flags to confirm if your specific instances are in scope. Objective: These changes are designed to "enhance network connectivity for performance storage systems," which typically results in lower latency and higher throughput for data-heavy operations once completed.
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-5aeaf6891a
Is this RunPod maintenance still going on?
No, it ended 2026-04-25 17:49 UTC.
How long did it last?
0m, from 2026-04-25 17:49 UTC to 2026-04-25 17:49 UTC, by the times RunPod posted.
What was affected?
RunPod named in us.
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.