- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
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 3h 20m it lasted.
Anything that failed between 2026-04-28 04:52 UTC and 2026-04-28 08: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 3
- update
We are experiencing network connectivity issues in CA-MTL-1 and CA-MTL-3. We are working to resolve it.
provider
- update
Network connectivity to CA-MTL-3 DC has been restored. We are continuing to work on resolving network issues in CA-MTL-1 DC.
provider
- resolved
Network connectivity to CA-MTL-1 DC has been restored.
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-e021ea89a6
Is RunPod still down?
No, this incident was resolved 2026-04-28 08:12 UTC. For RunPod's live state, see https://down.guide/runpod.
How long did it last?
3h 20m, from 2026-04-28 04:52 UTC to 2026-04-28 08:12 UTC, by the times RunPod posted.
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.