Confluent outage history and postmortems
Data and observability · Mountain View, US · 16 incidents in 90 days · 99.40% implied uptime · last 45h ago
Incidents
55 on fileAbout Confluent
Confluent, Inc. is an American technology company headquartered in Mountain View, California.
The last year, day by day
Downtime, added up
Confluent: 12h 56m weighted downtime in range, category median 2h 1m.
16 incidents, 7 major or critical, 3d 12h of incident time (2d 2h major or critical, 34h 8m partial), longest 29h 39m, implied uptime 99.40%, between Jun 28, 2026 and Sep 25, 2026.
Across fru.dev:Company profileAcquisitionsCompliancePaydaysRegionsChangefeedSLAsTechConfUptime
Questions
Is Confluent down right now?
Check Confluent's own status page at https://status.confluent.cloud for the live state. This page shows Confluent's incident history from that page; the most recent incident started 2026-09-23: "Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2".
How often does Confluent have outages?
Confluent posted 16 incidents in the last 90 days and 55 in the last year, 7 of them major or critical in the last 90 days. The median incident lasted 3h 3m.
When was Confluent's last major outage?
2026-09-23: "Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2", lasting 11h 30m.
What usually causes Confluent incidents?
Where Confluent explained the cause, the most common was configuration change (1 incidents). Most status updates do not name a cause.
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.