dbt Labs 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.
98.80%free of major or critical incidents, last 30 days
97.95%free of major or critical incidents, last 90 days
89.00%free of any incident, last 90 days
28incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 8 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 9 (UTC day): 0 min with a major or critical incident open, 17 h 44 min with any incident openAug 10 (UTC day): 0 min with a major or critical incident open, 1 h 44 min with any incident open, 1 incident startedAug 11 (UTC day): 0 min with a major or critical incident open, 1 h 30 min with any incident openAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): 0 min with a major or critical incident open, 3 h 15 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): 6 h 19 min with a major or critical incident open, 6 h 19 min with any incident open, 1 incident startedAug 18 (UTC day): 0 min with a major or critical incident open, 3 h 1 min with any incident open, 1 incident startedAug 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): 0 min with a major or critical incident open, 1 h 35 min with any incident open, 1 incident startedAug 26 (UTC day): 0 min with a major or critical incident open, 5 h 51 min with any incident open, 1 incident startedAug 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): no vendor-reported incident openSep 2 (UTC day): 0 min with a major or critical incident open, 6 h 53 min with any incident open, 1 incident startedSep 3 (UTC day): no vendor-reported incident openSep 4 (UTC day): 1 h 31 min with a major or critical incident open, 1 h 31 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): 4 h 47 min with a major or critical incident open, 4 h 47 min with any incident open, 1 incident startedSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): 7 h 56 min with a major or critical incident open, 11 h 57 min with any incident open, 3 incidents startedSep 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): 28 min with a major or critical incident open, 28 min with any incident open, 1 incident startedSep 19 (UTC day): 14 h 30 min with a major or critical incident open, 14 h 30 min with any incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 0 min with a major or critical incident open, 2 h 48 min with any incident open, 1 incident startedSep 24 (UTC day): 0 min with a major or critical incident open, 10 h 33 min with any incident open, 2 incidents startedSep 25 (UTC day): 0 min with a major or critical incident open, 5 h 25 min with any 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, 6 h 10 min with any incident open, 1 incident startedOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): 0 min with a major or critical incident open, 44 min with any incident open, 1 incident startedOct 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, 40 min with any incident open, 1 incident startedOct 8 (UTC day): 0 min with a major or critical incident open, 8 h 30 min with any incident open, 1 incident startedOct 9 (UTC day): 0 min with a major or critical incident open, 22 h 56 min with any 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): 1 h 56 min with a major or critical incident open, 1 h 56 min with any incident open, 1 incident startedOct 14 (UTC day): 4 h 33 min with a major or critical incident open, 4 h 33 min with any incident openOct 15 (UTC day): 0 min with a major or critical incident open, 3 h with any incident open, 1 incident startedOct 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, 8 h 11 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, 6 h 39 min with any incident open, 1 incident startedOct 23 (UTC day): 0 min with a major or critical incident open, 5 h 27 min with any 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, 4 h 42 min with any incident open, 1 incident startedOct 29 (UTC day): 2 h 6 min with a major or critical incident open, 3 h 3 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): 0 min with a major or critical incident open, 13 h 10 min with any incident open, 2 incidents startedNov 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 | 98.80% | 88.50% | 8 h 35 min | 3.4 days | 10 |
| Last 90 days | 97.95% | 89.00% | 44 h 6 min | 9.9 days | 28 |
This is what dbt Labs 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: dbt Labs status history · last 90 days · dbt Labs status page (opens in new tab) · Markdown