Is Confluent down?
Last checked just nowActive incident: Elevated error rates in AWS me-south-1 and me-central-1 reg…
Confluent is reporting a partial outage right now (last checked just now). Some components are affected; others remain operational.
Real-time Confluent status, recent outages, and incident history — pulled directly from Confluent's official status page at https://status.confluent.cloud every 5 minutes. Pingoru tracks 1 Confluent service and has captured 8 incidents in the last 90 days (87.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Confluent reports a new incident — free for 5 monitors, no credit card.
Active incident 1
- Confluent Cloud
Timeline · 3 updates
- monitoring · Mar 20, 2026, 01:58 PM UTC
AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
- monitoring · Apr 01, 2026, 07:52 PM UTC
Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
- monitoring · Apr 02, 2026, 03:40 PM UTC
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
Latest: Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 a…
-
Recent outages & incidents
Past 90 days- Confluent Cloud
Timeline · 4 updates
- investigating · Jun 12, 2026, 07:42 AM UTC
We are investigating intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking and Apache Flink processing for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
- investigating · Jun 12, 2026, 09:11 AM UTC
We continue to investigate intermittent inter-region network connectivity issues affecting AWS us-west-2. Customers may experience delays or errors with Cluster Linking, Flink processing and logs for clusters in or communicating with this region. We are actively investigating the cause and working on mitigation.
- monitoring · Jun 12, 2026, 09:53 AM UTC
We have deployed a mitigation for the intermittent inter-region connectivity issues affecting AWS us-west-2, which began at approximately 04:00 UTC. Customers with clusters in or communicating with this region may have experienced delays or errors with Cluster Linking, Flink processing, and accessing logs in the Confluent Cloud UI. We are monitoring to confirm full restoration.
- resolved · Jun 12, 2026, 11:55 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Confluent Cloud
Timeline · 5 updates
- investigating · May 29, 2026, 05:57 AM UTC
We are currently experiencing increased error rates and latencies in the Azure westus2 region. This began at approximately 5:10 AM UTC 29th May. Our team is actively investigating it.
- investigating · May 29, 2026, 06:47 AM UTC
Confluent cloud services are experiencing a zonal outage in Azure West US2 linked to Azure network connectivity degradation. Team is continuing active investigation.
- monitoring · May 29, 2026, 10:25 AM UTC
We are monitoring the health of impacted Confluent services in the Azure West US2 region. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
- monitoring · May 29, 2026, 04:49 PM UTC
Confluent services in the Azure West US2 region are now healthy. We are continuing to monitor for residual effects as Azure continues to address their service outage. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
- resolved · May 29, 2026, 09:47 PM UTC
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
Latest: The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
-
- Confluent Cloud
Timeline · 2 updates
- investigating · May 22, 2026, 12:21 AM UTC
Starting 20:26 UTC May 21, 2026, Confluent Cloud experienced connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2. We have fully mitigated the issue as of 23:56 UTC May 21, 2026 and service is operating normally.
- resolved · May 22, 2026, 12:22 AM UTC
The incident has been resolved.
Latest: The incident has been resolved.
-
- Confluent Cloud
Timeline · 5 updates
- investigating · May 08, 2026, 01:14 AM UTC
We are investigating data plane impact (produce/consume) resulting from elevated error rates and latencies from AWS us-east-1 resources in AZ4. EC2 instances hosted on this availability zone are impaired by loss of power during an ongoing thermal event.
- monitoring · May 08, 2026, 01:55 AM UTC
We are monitoring the health of impacted brokers in the affected availability zone. More details about the thermal event on the AWS status page: https://health.aws.amazon.com/health/status
- monitoring · May 09, 2026, 01:19 PM UTC
AWS has resolved the underlying infrastructure issue in us-east-1 (use1-az4). The majority of Confluent Cloud services have recovered and are operating normally. We are continuing to monitor for any lingering effects and performing cleanup of affected resources.
- monitoring · May 12, 2026, 06:51 PM UTC
AWS has reported the underlying infrastructure issue in us-east-1 (use1-az4) as resolved. However, some Confluent Cloud customers in the affected availability zone continue to experience connectivity issues. Confluent is actively investigating and working to restore full connectivity for impacted customers.
- resolved · Jun 04, 2026, 04:47 PM UTC
The incident has been resolved and us-east-1 (use1-az4) is fully operational.
Latest: The incident has been resolved and us-east-1 (use1-az4) is fully operational.
-
- Confluent Cloud
Timeline · 5 updates
- investigating · Apr 24, 2026, 05:18 PM UTC
We are currently investigating this issue.
- identified · Apr 24, 2026, 08:14 PM UTC
The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
- identified · Apr 24, 2026, 10:27 PM UTC
Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
- monitoring · Apr 24, 2026, 11:06 PM UTC
A fix has been implemented and we are monitoring for next hour.
- resolved · Apr 25, 2026, 12:14 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Confluent outage history
2 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
- Started Jun 12, 2026, 07:42 AM UTC · Resolved Jun 12, 2026, 11:55 AM UTC · 4h 12m
- Started May 29, 2026, 06:47 AM UTC · Resolved May 29, 2026, 09:47 PM UTC · 15h
- Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2 ResolvedStarted May 22, 2026, 12:21 AM UTC · Resolved May 22, 2026, 12:22 AM UTC · 1m
- Started May 08, 2026, 01:14 AM UTC · Resolved Jun 04, 2026, 04:47 PM UTC · 27d 15h
- Started Apr 24, 2026, 05:18 PM UTC · Resolved Apr 25, 2026, 12:14 AM UTC · 6h 56m
- Started Apr 21, 2026, 09:34 AM UTC · Resolved Apr 21, 2026, 09:49 AM UTC · 14m
- Started Apr 01, 2026, 07:52 PM UTC · ● 73d 4h