Confluent Outage History

59 incidents recorded over the last 365 days, 58 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Confluent status100.00% uptime history

Every Recorded Confluent Incident

Confluent incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 9, 2026Possible outage in AWS us-east-1This incident has been resolved. All affected services have fully recovered.56 minResolved
Oct 9, 2026Experiencing high error rate in AZURE in West Europe regionThis incident has been resolved.20h 2mResolved
Oct 8, 2026Experiencing high error rate in AZURE in Germany West Central regionThis incident has been resolved.55 minResolved
Sep 27, 2026Missing Metrics on Confluent CloudConfluent Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27. Queries for recent metrics during this time duration may return incomplete or no data. This incident has been resolved as of 02:15 UTC.-917 minResolved
Sep 26, 2026Elevated error rates in Azure East USThis incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.13h 3mResolved
Sep 23, 2026Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.11h 29mResolved
Sep 22, 2026Elevated error rates in Azure Germany West Central regionThis incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.4h 49mResolved
Sep 21, 2026Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2This incident has been resolved. All affected services, including Flink in AWS us-west-2, have fully recovered, and no further customer impact is expected. No action is required from customers.9h 27mResolved
Sep 17, 2026Confluent Cloud Metrics API experienced elevated latency and error ratesConfluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.-49 minResolved
Sep 15, 2026Multiple Confluent Cloud services are in a degraded state - All regionsThis incident has been resolved.1h 22mResolved
Sep 8, 2026Connectivity degradation - AWS us-east-1The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.16h 59mResolved
Sep 8, 2026Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1The systems have recovered and Confluent Cloud is fully operational.29h 38mResolved
Sep 1, 2026Investigating Elevated Errors in GCP us-central1The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to…47 minResolved
Aug 25, 2026Elevated error rates and latencies in Azure Southeast Asia regionConfluent services in the Azure Southeast Asia region are now healthy and operating normally.3h 11mResolved
Aug 24, 2026Confluent Cloud logging degradation - Connect and FlinkBetween 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and…-1129 minResolved
Aug 20, 2026Elevated error rates and latency in GCP us-west1The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.3h 7mResolved
Jul 17, 2026Flink statements degraded in GCP us-central1 regionAll the statements should be running now.2h 58mResolved
Jul 15, 2026Kafka cluster performance degradation for clusters in AWS region eu-central-1The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.13h 41mResolved
Jul 13, 2026Confluent Cloud Metrics API is currently experiencing elevated latency and error rates.This incident has been resolved.1h 38mResolved
Jun 29, 2026Kafka consumer and producer degradation in Azure spaincentralThis incident has been resolved.2h 51mResolved
Jun 29, 2026Confluent Cloud Metrics API is currently experiencing elevated error ratesThis incident has been resolved.51 minResolved
Jun 25, 2026Increased error rates in Metrics APIThis incident has been resolved.1h 54mResolved
Jun 23, 2026Confluent Cloud Metrics API unavailableOn June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.0 minResolved
Jun 21, 2026Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2This incident has been resolved.2h 4mResolved
Jun 16, 2026Intermittent Produce/Consume Unavailability in Azure Dedicated clustersNo further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.1h 56mResolved
Jun 12, 2026Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2This incident has been resolved.4h 12mResolved
May 29, 2026Elevated error rates and latencies in Azure westus2 regionThe Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.15h 50mResolved
May 22, 2026Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2The incident has been resolved.1 minResolved
May 13, 2026New Intermediate TLS Certificates rollout starting May 13th, 2026The scheduled maintenance has been completed.720h 0mScheduled
May 8, 2026Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4The incident has been resolved and us-east-1 (use1-az4) is fully operational.663h 33mResolved
May 6, 2026Scheduled Confluent Cloud maintenance on May 6, 2026The maintenance is complete.4h 56mResolved
Apr 24, 2026Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statementsThis incident has been resolved.6h 56mResolved
Apr 21, 2026Experiencing delays in Tableflow external catalog syncs in AWSThis incident has been resolved.14 minResolved
Mar 20, 2026Elevated error rates in AWS me-south-1 and me-central-1 regionsResolved.2821h 23mResolved
Mar 5, 2026Metrics API was experiencing failures from 03:23 UTC to 03:58 UTCConfluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.2h 42mResolved
Mar 2, 2026Elevated error rates in AWS me-south-1 and me-central-1 regionsThis incident has been resolved.425h 35mResolved
Mar 1, 2026Elevated Error Rates in AWS me-central-1 regionThis incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.3h 57mResolved
Feb 26, 2026All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failingThis incident has been resolved.6h 1mResolved
Feb 26, 2026Network provisioning service in Azure East US region is degradedThis incident has been resolved.8h 24mResolved
Feb 25, 2026Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors ratesThis incident has been resolved.61h 14mResolved
Feb 24, 2026Elevated Kafka REST API Errors in AWS us-west-2This incident has been resolved.3h 52mResolved
Feb 23, 2026Elevated Kafka Latency in GCP asia-southeast1The issue was resolved successfully. All systems working as expected.11h 45mResolved
Feb 11, 2026All new cluster creations in Azure westus3, southcentralus, and eastus2 are failingThe incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.4h 30mResolved
Feb 3, 2026Confluent Cloud Service OutageThe issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC…3h 14mResolved
Jan 8, 2026Multiple customers are reporting networking instability in the Azure West Europe regionThis incident has been resolved.3h 55mResolved
Dec 16, 2025Metrics API /export endpoint emitting 400 errorsMetrics API /export endpoint was emitting 400 errors from 06:02 UTC to 10:20 UTC-302 minResolved
Dec 8, 2025Missing metrics in some Confluent Cloud Kafka clustersThis issue has been resolved.34h 59mResolved
Dec 2, 2025Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.4h 26mResolved
Nov 28, 2025BYOK-enabled Tableflow deployments may experience data inconsistencies when executing queries that include filter predicatesThis incident has been resolved.5h 8mResolved
Nov 21, 2025Confluent Cloud Freight customers experiencing latency spikes intermittently in us-east-1Some of the Freight customers in AWS us-east-1 could have experienced latency spikes intermittently0 minResolved
Nov 17, 2025Confluent Cloud Connector event logs - Unavailable - All clusters - All regionsThis issue has been resolved, and there should be no further log loss. All subsequent connector log events are now accessible.6h 39mResolved
Nov 5, 2025Availability issues for Kafka clusters in Azure West EuropeAll affected clusters are now fully operational.27h 19mResolved
Oct 29, 2025Brief unavailability of produce requests for Enterprise SKU clusters in AWS us-east-1Some customers in AWS us-east-1 may have experienced unavailability of produce requests for Enterprise SKU clusters from 3:40 to 4:05 PM UTC.-238 minResolved
Oct 29, 2025Degraded Flink statements in AzureMicrosoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.7h 47mResolved
Oct 27, 2025Customers are encountering a 404 error when attempting to access resources within the Confluent Cloud UI.This incident has been resolved.25 minResolved
Oct 22, 2025Delayed cluster provisioning in Azure eastus regionThis incident has been resolved.54h 35mResolved
Oct 22, 2025Flink statements failing in multiple regionsAll impacted Flink compute pools have been fixed and degraded statements have recovered.6h 24mResolved
Oct 20, 2025Experiencing Performance Degradation in AWS in US-East-1 regionThe incident has been fully resolved, and all services are operating as expected.26h 11mResolved
Oct 17, 2025Basic/Std clsuters in AWS ap-southeast-1 are experiencing degraded performanceThis incident has been resolved.6h 36mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Confluent incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Confluent Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Confluent acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Confluent outage in this window ran 117d 13h, against a mean recovery of 3d 22h. If you depend on Confluent in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.