rewindex

CompaniesConfluentMonthly reportsFebruary 2025

Confluent in February 2025: incidents, uptime and changes

8incidents posted
6labelled major or critical
97.66%free of major/critical
96.14%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 15 h 43 min, incident time 25 h 56 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: Critical 1 · Major 5 · Minor 2

Major and critical incidents 6

IncidentImpactStartedDurationStatusDay
Confluent Cloud incident affecting Kafka clusters in Azure norwayeastCritical19 minresolved02-20
Experiencing connectors provisioning delaysMajor38 minresolved02-06
Kafka Rest API unreachable for certain dedicated networksMajor3.0 hresolved02-12
connectivity issues in AWS eu-north-1. Customers may experience availability issues in the region.Major2.8 hresolved02-13
Apache Flink incident in AWS us-west-2Major49 minresolved02-20
Experiencing partial outage in AZURE in US EAST 2 regionMajor8.2 hresolved02-25

Other incidents 2

IncidentImpactStartedDurationStatusDay
Cluster Provisioning - degraded performanceMinor7.4 hresolved02-18
Egress IPs are not discoverable.Minor2.8 hresolved02-26

Maintenance 1

Show scheduled maintenance

Cite this

Confluent posted 8 status incidents in February 2025 (6 major or critical); 0 price changes and 0 notable page changes observed.

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

All Confluent monthsRecent incidentsMarkdown