CompaniesConfluentMonthly reportsApril 2026
Confluent in April 2026: incidents, uptime and changes
3incidents posted
2labelled major or critical
76.63%free of major/critical
76.63%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 7.0 days, incident time 7.0 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 2 · No impact listed 1
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Elevated error rates in AWS me-south-1 and me-central-1 regions | Major | 105 d | resolved | 04-01 | |
| Experiencing delays in Tableflow external catalog syncs in AWS | Major | 15 min | resolved | 04-21 |
Other incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements | No impact listed | 6.9 h | resolved | 04-24 |
Cite this
Confluent posted 3 status incidents in April 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in April 2026
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2026/04