- 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-03-24 18:26 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 are expanding our VXLAN fabric in the US-CA-2 datacenter by adding an additional Spine switch. This enhancement increases redundancy and ensures $N+1$ fault tolerance for all services hosted in this region. Schedule: Location: US-CA-2 Datacenter Date: Thursday, March 26, 2026 Maintenance Window: 11:00 AM – 2:00 PM PDT Service Impact: Expected Impact: None Details: This is a non-disruptive infrastructure addition. Network traffic will continue to route through existing nodes while the new node is integrated. Monitoring: Our engineering team will be actively monitoring the fabric throughout the window. No action is required on your part.
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-64f14faea7
Is this RunPod maintenance still going on?
No, it ended 2026-03-24 18:26 UTC.
How long did it last?
0m, from 2026-03-24 18:26 UTC to 2026-03-24 18:26 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.