rewindex

CompaniesConfluentMonthly reportsMay 2025

Confluent in May 2025: incidents, uptime and changes

7incidents posted
2labelled major or critical
98.41%free of major/critical
74.12%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 11 h 46 min, incident time 8.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 · Minor 4 · No impact listed 1

Major and critical incidents 2

IncidentImpactStartedDurationStatusDay
Confluent Cloud Metrics may return incorrect or no data for a few customersMajor1.8 hresolved05-18
Customers will encounter issues when creating new Kafka clusters within existing Confluent Cloud Networks on Azure that use Privatelink as the access methodMajor10.0 hresolved05-19

Other incidents 5

IncidentImpactStartedDurationStatusDay
Confluent Cloud Metrics API DelayNo impact listed0 minresolved05-01
Confluent Cloud Flink - Customers may experience failures with DROP TABLE statementsMinor7 dresolved05-07
Degraded experience with Flink queriesMinor11 hresolved05-09
Cloud UI Homepage Status is degradedMinor3.1 hresolved05-12
Confluent Cloud Flink - Customers may experience increased rate of degraded statementsMinor24 hresolved05-14

Cite this

Confluent posted 7 status incidents in May 2025 (2 major or critical); 0 price changes and 0 notable page changes observed.

Title
Confluent in May 2025
Vendor
Confluent
Date
URL
https://rewindex.com/company/confluent/2025/05

All Confluent monthsRecent incidentsMarkdown