- Level
- confirmed
- Worst impact
- Maintenance
- Components
- EUR-NO-2
What to do
Check whether you use RunPod EUR-NO-2. 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-10-10 02:00 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 2
- update
Network Engineers have scheduled emergency maintenance on our upstream network infrastructure. Traffic will automatically reroute during this time, so we do not anticipate any interruptions to your services. Maintenance window: 10/09/2026 16:30 - 10/10/2026 02:00 UTC
provider
- update
Maintenance ended
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-93de3b9215
Is this RunPod maintenance still going on?
No, it ended 2026-10-10 02:00 UTC.
How long did it last?
9h 30m, from 2026-10-09 16:30 UTC to 2026-10-10 02:00 UTC, by the times RunPod posted.
What was affected?
RunPod named EUR-NO-2.
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.