CompaniesConfluentMonthly reportsMarch 2024
Confluent in March 2024: incidents, uptime and changes
6incidents posted
0labelled major or critical
100%free of major/critical
94.33%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 42 h 11 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: Minor 5 · No impact listed 1
Incidents 6
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Connection failures for kafka clusters in AWS us-east-1 | Minor | 4.2 h | resolved | 03-06 | |
| Experiencing high latency in few Azure clusters | Minor | 5.8 h | resolved | 03-12 | |
| Schema Linking functionality with destination Schema Registry clusters in Confluent Cloud (all regions) may experience failures. | Minor | 5.8 h | resolved | 03-13 | |
| Schema Registry/KSQL/Flink new API Key Sync delay | No impact listed | 1.4 h | resolved | 03-13 | |
| Azure clusters in South Africa North and South Africa West regions may experience network latency or failed connections | Minor | 22 h | resolved | 03-14 | |
| Confluent cloud metrics are experiencing delays | Minor | 4.2 h | resolved | 03-28 |
Cite this
Confluent posted 6 status incidents in March 2024 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in March 2024
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2024/03