rewindex

CompaniesConfluentMonthly reportsJune 2026

Confluent in June 2026: incidents, uptime and changes

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

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

Major and critical incidents 2

IncidentImpactStartedDurationStatusDay
Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2Major4.2 hresolved06-12
Increased error rates in Metrics APIMajor1.9 hresolved06-25

Other incidents 5

IncidentImpactStartedDurationStatusDay
Intermittent Produce/Consume Unavailability in Azure Dedicated clustersMinor1.9 hresolved06-16
Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2Minor2.1 hresolved06-21
Confluent Cloud Metrics API unavailableNo impact listed0 minresolved06-23
Confluent Cloud Metrics API is currently experiencing elevated error ratesMinor1.2 hresolved06-29
Kafka consumer and producer degradation in Azure spaincentralMinor2.9 hresolved06-29

Cite this

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

Title
Confluent in June 2026
Vendor
Confluent
Date
URL
https://rewindex.com/company/confluent/2026/06

All Confluent monthsRecent incidentsMarkdown