CompaniesConfluentMonthly reportsFebruary 2019
Confluent in February 2019: incidents, uptime and changes
2incidents posted
1labelled major or critical
99.84%free of major/critical
98.02%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 1 h 1 min, incident time 13 h 16 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 1 · Minor 1
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Pro Signups are Failing | Major | 1.0 h | resolved | 02-27 |
Other incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Management console is getting API errors trying to delete cluster from UI | Minor | 12 h | resolved | 02-22 |
Cite this
Confluent posted 2 status incidents in February 2019 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in February 2019
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2019/02