CompaniesConfluentMonthly reportsMarch 2026
Confluent in March 2026: incidents, uptime and changes
3incidents posted
3labelled major or critical
77.02%free of major/critical
77.02%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 7.1 days, incident time 7.1 days. 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 3
Major and critical incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Elevated Error Rates in AWS me-central-1 region | Major | 4.0 h | resolved | 03-01 | |
| Elevated error rates in AWS me-south-1 and me-central-1 regions | Major | 18 d | resolved | 03-02 | |
| Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC | Major | 2.7 h | resolved | 03-05 |
Deprecations and commercial changes
- IBM completes its acquisition of Confluent (opens in new tab) (Confluent (Confluent Cloud & Platform)) · announced 2026-03-17, effective 2026-03-17
Cite this
Confluent posted 3 status incidents in March 2026 (3 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in March 2026
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2026/03