- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 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 2h 40m it lasted.
Anything that failed between 2026-02-19 16:29 UTC and 2026-02-19 19:09 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 monitoring errors with an upstream authentication provider that is causing console login to be very slow or fail for some users.
provider
- update
We are still tracking errors from an upstream authentication provider which are causing console login to be very slow or fail for some users.
provider
- resolved
The issues have been resolved by the upstream vendor and we are not seeing errors at this time, but will continue monitoring.
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-1f1b3dbf46
Is RunPod still down?
No, this incident was resolved 2026-02-19 19:09 UTC. For RunPod's live state, see https://down.guide/runpod.
How long did it last?
2h 40m, from 2026-02-19 16:29 UTC to 2026-02-19 19:09 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.