- Level
- confirmed
- Worst impact
- Major outage
- Components
- EUR-IS-3
- Down Index
- 55of 100
Summary
RunPod says EUR-IS-3 experienced network connectivity issues, which began with its 2026-11-05 17:40 UTC update. On 2026-11-06 at 07:12 UTC, RunPod reported the issue resolved and the EUR-IS-3 network operating normally.
Written by anthropic/claude-haiku-5.5 from RunPod's own updates.
What to do
Check whether you use RunPod EUR-IS-3. 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 13h 33m it lasted.
Anything that failed between 2026-11-05 17:40 UTC and 2026-11-06 07:12 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 2
- downtime
We are experiencing network connectivity issues in EUR-IS-3. We are working to resolve it.
provider
- resolved
Issue has been resolved and the network in EUR-IS-3 DC is operating normally.
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-6889cd2e21
Is RunPod still down?
No, this incident was resolved 2026-11-06 07:12 UTC. For RunPod's live state, see https://down.guide/runpod.
How long did it last?
13h 33m, from 2026-11-05 17:40 UTC to 2026-11-06 07:12 UTC, by the times RunPod posted.
What was affected?
RunPod named EUR-IS-3.
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.