CompaniesBitbucketvs HashiCorp
Bitbucket vs HashiCorp
From vendor reports Category: devtools. 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.
| Bitbucket | HashiCorp | |
|---|---|---|
| Free of major/critical incidents, 30 days | 99.62% | 96.07% |
| Free of major/critical incidents, 90 days | 99.64% | 98.22% |
| Free of any incident, 90 days | 99.54% | 94.55% |
| Outage time (major/critical), 90 days | 7 h 37 min | 38 h 18 min |
| Incidents started, 30 days | 2 | 2 |
| Incidents started, 90 days | 5 | 10 |
| Silently edited or deleted incidents (all time / 90 days) | 0 / 0 | 2 / 2 |
| Price changes detected | 0 | 0 |
| Deprecations and breaking changes | 0 | 0 |
| CVEs mapped to the vendor | 159 | 91 |
Counts are facts from the vendors’ own pages as archived by Rewindex; impact labels are the vendors’ own. Not a ranking. Recomputed .