- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
- Down Index
- 27of 100
What to do
Check whether you use RunPod in eu. 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 22h 36m it lasted.
Anything that failed between 2026-02-23 22:21 UTC and 2026-02-24 20:57 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 4
- update
We are experiencing network connectivity issues in EU-FR-1. We are working to resolve it.
provider
- update
We are continuing to work on resolving the network issue in EU-FR-1 DC.
provider
- update
We have network recovery in EU-FR-1 DC but will be continuing to monitor for the next 24 hours.
provider
- resolved
We've completed monitoring. Issue has been resolved and network 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-c9e38f9a4f
Is RunPod still down?
No, this incident was resolved 2026-02-24 20:57 UTC. For RunPod's live state, see https://down.guide/runpod.
How long did it last?
22h 36m, from 2026-02-23 22:21 UTC to 2026-02-24 20:57 UTC, by the times RunPod posted.
What was affected?
RunPod named in eu.
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.