rewindex

CompaniesConfluentMonthly reportsFebruary 2026

Confluent in February 2026: incidents, uptime and changes

7incidents posted
5labelled major or critical
89.73%free of major/critical
87.40%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 2.9 days, incident time 3.5 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 5 · Minor 2

Major and critical incidents 5

IncidentImpactStartedDurationStatusDay
Confluent Cloud Service OutageMajor3.3 hresolved02-03
All new cluster creations in Azure westus3, southcentralus, and eastus2 are failingMajor4.5 hresolved02-11
Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors ratesMajor3 dresolved02-25
Network provisioning service in Azure East US region is degradedMajor8.4 hresolved02-26
All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failingMajor6.0 hresolved02-26

Other incidents 2

IncidentImpactStartedDurationStatusDay
Elevated Kafka Latency in GCP asia-southeast1Minor12 hresolved02-23
Elevated Kafka REST API Errors in AWS us-west-2Minor3.9 hresolved02-24

Cite this

Confluent posted 7 status incidents in February 2026 (5 major or critical); 0 price changes and 0 notable page changes observed.

Title
Confluent in February 2026
Vendor
Confluent
Date
URL
https://rewindex.com/company/confluent/2026/02

All Confluent monthsRecent incidentsMarkdown