CPU pod, Servless and some public endpoint disruption

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.

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

  Anything that failed between 2025-11-03 12:47 UTC and 2025-11-03 12:47 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. resolvedNov 3, 2025, 12:47 PM UTC

   We’ve added more CPU resources, and so far both CPU serverless and public endpoints are scaling up normally again. -------- We are tracking an ongoing incident with CPU pod, serverles, github integration and public endpoints. we are spinning up emergency reservers of CPU server capacity in multiple datacenters and tracking current usage to pinpoint exact issues

   provider

Corrections

None so far.

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