Is Confluent down?
Last checked just nowNo incidents right now.
Confluent is operational right now. Last checked just now; the most recent incident resolved 13d ago.
Real-time Confluent status, recent outages, and incident history: pulled directly from Confluent's official status page at status.confluent.cloud every 5 minutes. Pingoru tracks 1 Confluent service and has captured 19 incidents in the last 90 days (94.57% uptime). Get email, Slack, Discord, or webhook alerts the moment Confluent reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Confluent Cloud
Timeline · 5 updates
- investigating · Oct 20, 2026, 08:02 AM UTC
Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2
- investigating · Oct 20, 2026, 12:55 PM UTC
We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.
- monitoring · Oct 20, 2026, 02:46 PM UTC
The underlying GCP issue has been mitigated. Confluent Cloud Kafka clusters in the affected zone are fully operational and Connect and Flink workloads have recovered. We are monitoring to confirm stability and working to restore the few remaining impacted resources.
- monitoring · Oct 20, 2026, 02:51 PM UTC
We are continuing to monitor for any further issues.
- resolved · Oct 20, 2026, 06:27 PM UTC
This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
Latest: This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
-
- Confluent Cloud
Timeline · 9 updates
- investigating · Oct 16, 2026, 01:04 AM UTC
We are investigating an issue that is causing delays in Kafka cluster provisioning in all regions. Existing clusters are not affected and continue to operate normally. We will provide another update within 60 minutes.
- investigating · Oct 16, 2026, 02:26 AM UTC
We are still investigating the delays in Kafka cluster provisioning in all regions and are actively working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 3:30 UTC or as more information becomes available.
- identified · Oct 16, 2026, 03:34 AM UTC
We have identified the cause of the delays in Kafka cluster provisioning in all regions and are working on mitigation. Existing clusters continue to operate normally. Our next update will be posted by 4:30 UTC or as more information becomes available.
- identified · Oct 16, 2026, 04:34 AM UTC
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
- identified · Oct 16, 2026, 04:35 AM UTC
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Our next update will be posted by 5:30 UTC or as more information becomes available
- identified · Oct 16, 2026, 05:30 AM UTC
We are continuing to work on mitigation for the delays in Kafka cluster provisioning. Existing clusters continue to operate normally. Clusters provisioned during this window may take longer than usual to become available. Our next update will be posted by 6:30 UTC or as more information becomes available
- monitoring · Oct 16, 2026, 06:47 AM UTC
We have mitigated the issue that was causing delays in Kafka cluster provisioning and we are now monitoring the health of new cluster provisioning. Existing clusters were not affected. We will post our next update by 07:30 UTC, or sooner if there is new information
- monitoring · Oct 16, 2026, 07:02 AM UTC
We are continuing to monitor for any further issues.
- resolved · Oct 16, 2026, 08:23 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Confluent Cloud
Timeline · 2 updates
- monitoring · Oct 15, 2026, 04:01 PM UTC
Between 14:23 and 15:35 UTC on Oct 15, 2026, some users of the Confluent Cloud Console experienced errors and degraded page functionality. No other services were affected. The issue has been mitigated and no further problems have been observed. Confluent is investigating root cause and monitoring. No customer action is required.
- resolved · Oct 15, 2026, 06:46 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Confluent Cloud
Timeline · 3 updates
- investigating · Oct 09, 2026, 11:27 PM UTC
We are investigating an incident affecting services in the AWS us-east-1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates.
- monitoring · Oct 09, 2026, 11:43 PM UTC
The observed elevated error rates seen in AWS us-east-1 have subsided and all services have recovered. No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.
- resolved · Oct 10, 2026, 12:23 AM UTC
This incident has been resolved. All affected services have fully recovered.
Latest: This incident has been resolved. All affected services have fully recovered.
-
- Confluent Cloud
Timeline · 12 updates
- investigating · Oct 09, 2026, 01:34 PM UTC
Users in West Europe region of Azure could face elevated error rates and experience degraded performance. We are currently investigating the issue and attempting to mitigate or provide a work-around.
- identified · Oct 09, 2026, 04:46 PM UTC
Azure has identified the issue and recovery actions are underway
- identified · Oct 09, 2026, 07:10 PM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 20:00 UTC, or sooner, as updates are available.
- identified · Oct 09, 2026, 08:02 PM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 21:00 UTC, or sooner, as updates are available.
- identified · Oct 09, 2026, 09:07 PM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 22:00 UTC, or sooner, as updates are available.
- identified · Oct 09, 2026, 10:04 PM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 23:00 UTC, or sooner, as updates are available.
- identified · Oct 09, 2026, 11:03 PM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 00:00 UTC, or sooner, as updates are available.
- identified · Oct 10, 2026, 12:12 AM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 01:00 UTC, or sooner, as updates are available.
- identified · Oct 10, 2026, 02:12 AM UTC
Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 03:00 UTC, or sooner, as updates are available.
- identified · Oct 10, 2026, 04:15 AM UTC
Confluent continues to work closely with Azure, and we are seeing recovery across a number of affected clusters. Azure has not yet provided a specific ETA for full resolution. We will continue to provide updates as more information becomes available.
- monitoring · Oct 10, 2026, 08:47 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Oct 10, 2026, 09:36 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Confluent outage history
14 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Confluent outage history →Or sign up free to get alerts when Confluent breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Statuspage by Atlassian · 1 component checked every 5 minutesThe longest incident in the last year, Elevated error rates in AWS me-south-1 and me-central-1 regions on March 20, 2026, ran for 118 days. 2 maintenance windows announced in the same period.
Most affected components, last 12 months
- Confluent Cloud47
Latest incidents
- Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2
- Delay in Kafka cluster provisioning
We are investigating an issue that is causing delays in Kafka cluster provisioning in all regions. Existing clusters are not affected and continue to operate…
- Confluent Cloud Console (UI) degraded functionality
Between 14:23 and 15:35 UTC on Oct 15, 2026, some users of the Confluent Cloud Console experienced errors and degraded page functionality. No other services…
- Started Oct 20, 2026, 08:02 AM UTC · Resolved Oct 20, 2026, 06:27 PM UTC · 10h 24m
- Delay in Kafka cluster provisioning ResolvedStarted Oct 16, 2026, 01:04 AM UTC · Resolved Oct 16, 2026, 08:23 AM UTC · 7h 18m
- Started Oct 15, 2026, 04:01 PM UTC · Resolved Oct 15, 2026, 06:46 PM UTC · 2h 44m
- Possible outage in AWS us-east-1 ResolvedStarted Oct 09, 2026, 11:27 PM UTC · Resolved Oct 10, 2026, 12:23 AM UTC · 56m
- Started Oct 09, 2026, 01:34 PM UTC · Resolved Oct 10, 2026, 09:36 AM UTC · 20h 2m
- Started Oct 08, 2026, 11:00 AM UTC · Resolved Oct 08, 2026, 11:56 AM UTC · 55m
- Missing Metrics on Confluent Cloud ResolvedStarted Sep 27, 2026, 12:33 AM UTC · Resolved Sep 27, 2026, 02:15 AM UTC · 1h 42m
- Started Sep 26, 2026, 06:40 AM UTC · Resolved Sep 26, 2026, 07:43 PM UTC · 13h 3m