Companiesdbt Labsvs MongoDB Atlas
dbt Labs vs MongoDB Atlas
From vendor reports Category: data. 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.
| dbt Labs | MongoDB Atlas | |
|---|---|---|
| Free of major/critical incidents, 30 days | 98.80% | 99.75% |
| Free of major/critical incidents, 90 days | 97.95% | 98.26% |
| Free of any incident, 90 days | 89.00% | 97.29% |
| Outage time (major/critical), 90 days | 44 h 6 min | 37 h 26 min |
| Incidents started, 30 days | 10 | 2 |
| Incidents started, 90 days | 28 | 8 |
| Silently edited or deleted incidents (all time / 90 days) | 5 / 5 | 1 / 1 |
| Price changes detected | 0 | 0 |
| Deprecations and breaking changes | 5 | 5 |
| CVEs mapped to the vendor | 7 | 281 |
Counts are facts from the vendors’ own pages as archived by Rewindex; impact labels are the vendors’ own. Not a ranking. Recomputed .