- 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-09-29 17: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
Planned Network Maintenance EUR-NO-2 Core Router Upgrade: When: September 29th 2026, from 14:00–17:00 UTC. Please be advised that scheduled network maintenance will take place at the EUR-NO-2 Datacenter. We will be migrating the core routing infrastructure to new routers. The migration will be completed in phases, with redundancy maintained throughout. Expected Impact: Customers may experience brief upstream connectivity interruptions during individual cut-over phases. No impact is expected outside of these short windows.
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-7d0f41e121
Is this RunPod maintenance still going on?
No, it ended 2026-09-29 17:00 UTC.
How long did it last?
3h, from 2026-09-29 14:00 UTC to 2026-09-29 17: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.