CompaniesConfluentMonthly reportsDecember 2019
Confluent in December 2019: incidents, uptime and changes
Vendor-reported outage time 3 h 55 min, incident time 7 h 44 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: Critical 1 · Minor 2 · No impact listed 2
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Subset of customers experiencing outage in our public facing AWS us-west-2 cluster | Critical | 3.9 h | resolved | 12-19 |
Other incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Degraded performance from kafka-6 broker on pkc-epgnk cluster (GCP us-central1 cluster) | No impact listed | 1.7 h | resolved | 12-03 | |
| Degraded performance from kafka-3/7 broker on pkc-l915e cluster | Minor | 0 min | resolved | 12-10 | |
| Degradation of service in AWS US East 1 | No impact listed | 9.9 h | resolved | 12-11 | |
| Kafka service degradation Confluent Cloud in us-west-2 AWS | Minor | 3.8 h | resolved | 12-31 |
Cite this
Confluent posted 5 status incidents in December 2019 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in December 2019
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2019/12