CompaniesCockroachDBMonthly reportsFebruary 2026
CockroachDB in February 2026: incidents, uptime and changes
2incidents posted
2labelled major or critical
97.75%free of major/critical
97.75%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 15 h 6 min, incident time 15 h 6 min. 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. Last 90 days.
By vendor label: Major 2
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Advanced cluster creation on AWS taking longer than expected | Major | 2.8 h | resolved | 02-02 | |
| Connectivity issues to Standard and Basic clusters on AWS | Major | 12 h | resolved | 02-09 |
Cite this
CockroachDB posted 2 status incidents in February 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- CockroachDB in February 2026
- Vendor
- CockroachDB
- Date
- URL
- https://rewindex.com/company/cockroachdb/2026/02