Incident Notice: Power Service Interruption – US-NC-1

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.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-04-04 17:58 UTC and 2026-04-04 17:58 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 1

1. resolvedApr 4, 2026, 5:58 PM UTC

   Update: At 1:45 PM PT, Power was restored to the site and machines had been started to be powered back on. The datacenter is back on full utility power with UPS backup. Datacenter engineers are continuing to look into why the generator supplied power at a voltage outside of expected range for the UPS which caused the UPS to not switch over. --------------- Original issue: Our datacenter US-NC-1 has reported a power failure at the US-NC-1 facility that occurred at approximately 8:00 AM PT on April 4th. This failure has taken down the entire A-side power. The servers currently failing are not N+N Redundant; they are N+1. Typically, in a power outage, UPS and Generators act as backup, however, this failover is not working. Onsite teams are working on providing a Root Cause Analysis (RCA) to find out why the backup power was unable to kick on to run these servers. Updates will be shared as our datacenter partners provide estimated repair times and as more information becomes available.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.