Buildkite 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.
99.92%free of major or critical incidents, last 30 days
99.51%free of major or critical incidents, last 90 days
98.06%free of any incident, last 90 days
25incidents 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): 0 min with a major or critical incident open, 59 min with any incident open, 1 incident startedAug 11 (UTC day): 0 min with a major or critical incident open, 2 h 4 min with any incident openAug 12 (UTC day): 0 min with a major or critical incident open, 1 h 25 min with any incident open, 1 incident startedAug 13 (UTC day): 0 min with a major or critical incident open, 59 min with any incident open, 1 incident startedAug 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): 0 min with a major or critical incident open, 1 h 57 min with any incident open, 1 incident startedAug 18 (UTC day): no vendor-reported incident openAug 19 (UTC day): no vendor-reported 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): 1 h 5 min with a major or critical incident open, 2 h 40 min with any incident open, 2 incidents startedAug 26 (UTC day): 18 min with a major or critical incident open, 1 h 49 min with any incident open, 1 incident startedAug 27 (UTC day): 0 min with a major or critical incident open, 51 min with any incident open, 1 incident startedAug 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 20 min with any incident open, 1 incident startedSep 2 (UTC day): 1 h 5 min with a major or critical incident open, 1 h 5 min with any incident open, 1 incident startedSep 3 (UTC day): 0 min with a major or critical incident open, 1 h 6 min with any incident open, 1 incident startedSep 4 (UTC day): 0 min with a major or critical incident open, 57 min with any incident open, 1 incident startedSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): 4 h 53 min with a major or critical incident open, 4 h 53 min with any incident open, 1 incident startedSep 10 (UTC day): 1 h 54 min with a major or critical incident open, 1 h 54 min with any incident openSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): no vendor-reported incident openSep 15 (UTC day): no vendor-reported incident openSep 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): no vendor-reported incident openSep 21 (UTC day): 0 min with a major or critical incident open, 1 h 10 min with any incident open, 1 incident startedSep 22 (UTC day): 42 min with a major or critical incident open, 42 min with any incident open, 1 incident startedSep 23 (UTC day): no vendor-reported incident openSep 24 (UTC day): no vendor-reported incident openSep 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): no vendor-reported incident openSep 30 (UTC day): 0 min with a major or critical incident open, 1 h 29 min with any incident open, 1 incident startedOct 1 (UTC day): 0 min with a major or critical incident open, 47 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): no vendor-reported incident openOct 6 (UTC day): 0 min with a major or critical incident open, 5 h 40 min with any incident open, 1 incident startedOct 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): 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): no vendor-reported incident openOct 20 (UTC day): 0 min with a major or critical incident open, 1 h 8 min with any incident open, 1 incident startedOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): 0 min with a major or critical incident open, 46 min with any incident open, 1 incident startedOct 23 (UTC day): no vendor-reported incident openOct 24 (UTC day): no vendor-reported incident openOct 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): 0 min with a major or critical incident open, 32 min with any incident open, 1 incident startedOct 29 (UTC day): 0 min with a major or critical incident open, 2 h 1 min with any incident open, 1 incident startedOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): 33 min with a major or critical incident open, 3 h 30 min with any incident open, 3 incidents startedNov 4 (UTC day): 0 min with a major or critical incident open, 6 min with any 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 | 99.92% | 98.09% | 33 min | 13 h 43 min | 8 |
| Last 90 days | 99.51% | 98.06% | 10 h 30 min | 41 h 50 min | 25 |
This is what Buildkite 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: Buildkite status history · last 90 days · Buildkite status page (opens in new tab) · Markdown