CompaniesConfluentMonthly reportsJanuary 2025
Confluent in January 2025: incidents, uptime and changes
Vendor-reported outage time 30 h 7 min, incident time 40 h 3 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 2 · No impact listed 2
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Metrics API is Experiencing Delays | Major | 30 h | resolved | 01-10 |
Other incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Experiencing network issues within Azure East US2 deployments | Minor | 9.6 h | resolved | 01-09 | |
| Metrics API is Experiencing Delays | Minor | 21 min | resolved | 01-10 | |
| Some clusters seeing problems provisioning nodes in Azure East US2 deployments | No impact listed | 3.0 h | resolved | 01-10 | |
| Customers experiencing HTTP 401 errors on Schema Registry API requests | No impact listed | 1.4 h | resolved | 01-16 |
Cite this
Confluent posted 5 status incidents in January 2025 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Confluent in January 2025
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/2025/01