CompaniesRed Hat (incl. Quay.io)Uptime
Red Hat (incl. Quay.io) 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.
94.45%free of major or critical incidents, last 30 days
89.64%free of major or critical incidents, last 90 days
76.62%free of any incident, last 90 days
35incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): 11 h with a major or critical incident open, 11 h with any incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): 19 h 36 min with a major or critical incident open, 19 h 36 min with any incident open, 1 incident startedAug 10 (UTC day): 4 h 24 min with a major or critical incident open, 4 h 24 min with any incident openAug 11 (UTC day): no vendor-reported incident openAug 12 (UTC day): 2 h 58 min with a major or critical incident open, 2 h 58 min with any incident open, 1 incident startedAug 13 (UTC day): no vendor-reported incident openAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): no vendor-reported incident openAug 18 (UTC day): 4 h 13 min with a major or critical incident open, 4 h 13 min with any incident open, 2 incidents startedAug 19 (UTC day): 3 h 14 min with a major or critical incident open, 3 h 14 min with any incident openAug 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): 16 min with a major or critical incident open, 16 min with any incident open, 1 incident startedSep 1 (UTC day): no vendor-reported incident openSep 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): no vendor-reported incident openSep 7 (UTC day): 13 h with a major or critical incident open, 13 h with any incident open, 3 incidents startedSep 8 (UTC day): 13 h 28 min with a major or critical incident open, 13 h 28 min with any incident openSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): no vendor-reported incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): 12 h with a major or critical incident open, 12 h with any incident open, 2 incidents startedSep 13 (UTC day): 19 h 21 min with a major or critical incident open, 19 h 21 min with any incident openSep 14 (UTC day): 10 h 26 min with a major or critical incident open, 10 h 26 min with any incident open, 2 incidents startedSep 15 (UTC day): 10 h 56 min with a major or critical incident open, 22 h 28 min with any incident open, 2 incidents startedSep 16 (UTC day): no vendor-reported incident openSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): 9 h 1 min with a major or critical incident open, 9 h 1 min with any incident open, 2 incidents startedSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): 21 min with a major or critical incident open, 21 min with any incident open, 1 incident startedSep 26 (UTC day): 11 h 35 min with a major or critical incident open, 11 h 35 min with any incident open, 1 incident startedSep 27 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 28 (UTC day): 13 h 58 min with a major or critical incident open, 13 h 58 min with any incident openSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): 0 min with a major or critical incident open, 8 h with any incident open, 2 incidents startedOct 1 (UTC day): 0 min with a major or critical incident open, 19 h 26 min with any incident open, 1 incident startedOct 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): 0 min with a major or critical incident open, 2 h 32 min with any incident open, 1 incident startedOct 6 (UTC day): no vendor-reported incident openOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): no vendor-reported incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): 7 h 3 min with a major or critical incident open, 7 h 3 min with any incident open, 1 incident startedOct 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, 7 h 40 min with any incident open, 1 incident startedOct 20 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 21 (UTC day): 23 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 22 (UTC day): 1 h 19 min with a major or critical incident open, 24 h with any incident openOct 23 (UTC day): 13 h 58 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedOct 24 (UTC day): 13 h 10 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 26 (UTC day): 1 h 49 min with a major or critical incident open, 16 h 20 min with any incident open, 1 incident startedOct 27 (UTC day): no vendor-reported incident openOct 28 (UTC day): no vendor-reported incident openOct 29 (UTC day): 19 min with a major or critical incident open, 13 h 45 min with any incident open, 2 incidents startedOct 30 (UTC day): 1 h 53 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 31 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openNov 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openNov 2 (UTC day): 0 min with a major or critical incident open, 18 h 51 min with any 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 | 94.45% | 60.80% | 39 h 54 min | 11.8 days | 14 |
| Last 90 days | 89.64% | 76.62% | 9.3 days | 21.0 days | 35 |
This is what Red Hat (incl. Quay.io) 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: Red Hat (incl. Quay.io) status history · last 90 days · Red Hat (incl. Quay.io) status page (opens in new tab) · Markdown