RunPod uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
95.15%free of major or critical incidents, last 30 days
97.89%free of major or critical incidents, last 90 days
93.26%free of any incident, last 90 days
28incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): no vendor-reported incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): no vendor-reported incident openAug 11 (UTC day): no vendor-reported incident openAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): 0 min with a major or critical incident open, 13 h 13 min with any incident open, 1 incident startedAug 14 (UTC day): 2 h 30 min with a major or critical incident open, 12 h 20 min with any incident open, 1 incident startedAug 15 (UTC day): 3 h 40 min with a major or critical incident open, 3 h 40 min with any incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): 0 min with a major or critical incident open, 3 h with any incident open, 1 incident startedAug 18 (UTC day): no vendor-reported incident openAug 19 (UTC day): 48 min with a major or critical incident open, 2 h with any incident open, 2 incidents startedAug 20 (UTC day): no vendor-reported incident openAug 21 (UTC day): no vendor-reported incident openAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): no vendor-reported incident openAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): 0 min with a major or critical incident open, 1 h 46 min with any incident open, 1 incident startedSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): 0 min with a major or critical incident open, 1 h 25 min with any incident open, 1 incident startedSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): 28 min with a major or critical incident open, 28 min with any incident open, 1 incident startedSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): 0 min with a major or critical incident open, 7 h 52 min with any incident open, 1 incident startedSep 13 (UTC day): 0 min with a major or critical incident open, 5 h 33 min with any incident openSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): no vendor-reported incident openSep 16 (UTC day): 0 min with a major or critical incident open, 1 h 8 min with any incident open, 1 incident startedSep 17 (UTC day): 1 h 59 min with a major or critical incident open, 2 h 59 min with any incident open, 2 incidents startedSep 18 (UTC day): 0 min with a major or critical incident open, 2 h with any incident open, 1 incident startedSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): 14 min with a major or critical incident open, 14 min with any incident open, 1 incident startedSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): 0 min with a major or critical incident open, 5 h 23 min with any incident open, 1 incident startedSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): 33 min with a major or critical incident open, 33 min with any incident open, 1 incident startedSep 25 (UTC day): no vendor-reported incident openSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): 0 min with a major or critical incident open, 3 h 30 min with any incident open, 1 incident startedSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): no vendor-reported incident openOct 7 (UTC day): 0 min with a major or critical incident open, 31 min with any incident open, 1 incident startedOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): 1 h 31 min with a major or critical incident open, 1 h 31 min with any incident open, 1 incident startedOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): 0 min with a major or critical incident open, 1 h 30 min with any incident open, 1 incident startedOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): no vendor-reported incident openOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): 0 min with a major or critical incident open, 6 h 55 min with any incident open, 1 incident startedOct 20 (UTC day): 1 h 23 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 21 (UTC day): 0 min with a major or critical incident open, 7 h 35 min with any incident open, 1 incident startedOct 22 (UTC day): 0 min with a major or critical incident open, 2 h 58 min with any incident open, 1 incident startedOct 23 (UTC day): 0 min with a major or critical incident open, 25 min with any incident openOct 24 (UTC day): 5 h 14 min with a major or critical incident open, 5 h 14 min with any incident open, 1 incident startedOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): 2 h 31 min with a major or critical incident open, 2 h 31 min with any incident open, 1 incident startedOct 29 (UTC day): 14 min with a major or critical incident open, 14 min with any incident open, 1 incident startedOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): 3 h 30 min with a major or critical incident open, 3 h 30 min with any incident open, 1 incident startedNov 1 (UTC day): 20 h 30 min with a major or critical incident open, 20 h 30 min with any incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): no vendor-reported incident openNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 95.15% | 89.25% | 34 h 53 min | 3.2 days | 11 |
| Last 90 days | 97.89% | 93.26% | 45 h 5 min | 6.0 days | 28 |
This is what RunPod itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: RunPod status history · last 90 days · RunPod status page (opens in new tab) · Markdown