Sep 16, 01:21 UTC Resolved - This incident has been resolved. Sep 16, 00:22 UTC Monitoring - The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC). Sep 16, 00:00 UTC Identified - The issue has been identified and a fix is being implemen…
Sep 9, 14:56 UTC Resolved - The systems have recovered and Confluent Cloud is fully operational. Sep 9, 06:41 UTC Monitoring - We have applied a mitigation for the issue affecting Schema Registry, Authentication, ksqlDB, Flink, and Kafka operations in AWS us-east-1. Services are recovering and we are monitoring closely. Sep 9, 01:45 UTC Update - Confluent is continuing to work on the service disru…
Sep 9, 13:01 UTC Resolved - The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational. Sep 8, 20:30 UTC Monitoring - A fix has been implemented and the team is monitoring recovery. Sep 8, 20:20 UTC Identified - A possible root cause has been identified and the Confluent Cloud team is implementing a fix Sep 8, 20:13 UTC Update - We are continuing to investigate this issu…
Sep 1, 17:14 UTC Resolved - The 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 expected levels.Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support. Sep 1, 16:27 UTC Investiga…
Aug 25, 07:29 UTC Resolved - Confluent services in the Azure Southeast Asia region are now healthy and operating normally. Aug 25, 05:28 UTC Monitoring - We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation. Aug 25, 04:17 UTC Investigating - We are investigating connectivity issues and elevated error rates affecting so…
Aug 23, 21:00 UTC Resolved - Between 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 configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue h…
Aug 20, 20:18 UTC Resolved - The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring. Aug 20, 19:18 UTC Update - We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour. Aug 20, 17:10 UTC Investigating - We are investigating an incident affecting…
Jul 18, 00:59 UTC Resolved - All the statements should be running now. Jul 17, 22:55 UTC Monitoring - Currently, we are monitoring the results after rolling out the fix. Jul 17, 22:54 UTC Identified - Engineers have identified and implemented a fix. Jul 17, 22:01 UTC Investigating - Flink statements are degraded in GCP us-central1 region. The impact started at 18:37 UTC on July 17. Currently, engi…
Jul 16, 13:14 UTC Resolved - The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy. Jul 15, 23:33 UTC Investigating - Confluent is aware of the ongoing AWS incident affecting eu-central-1. We have identified degraded performance impacting clusters in this region, and our engineers are actively working with AWS to mitigate the issue.
Jul 16, 03:21 UTC Resolved - Resolved. Apr 2, 15:40 UTC Update - 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. Apr 1, 19:52 UTC Update - Provisioning new workloads in AWS me-central-1 and me-south-1 regi…
Jul 13, 16:04 UTC Resolved - This incident has been resolved. Jul 13, 14:36 UTC Monitoring - A fix has been implemented and we are monitoring the results Jul 13, 14:25 UTC Identified - The issue has been identified and a fix is being implemented.
Jun 29, 20:36 UTC Resolved - This incident has been resolved. Jun 29, 17:44 UTC Identified - Kafka producers and consumers to some clusters in Azure spaincentral may not be able to produce and consume records from their topic partitions. An issue has been identified by Azure and is under investigation.
Jun 29, 12:50 UTC Resolved - This incident has been resolved. Jun 29, 12:10 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 29, 12:04 UTC Identified - The issue has been identified and a fix is being implemented. Jun 29, 11:40 UTC Investigating - We are currently investigating this issue.
Jun 25, 17:53 UTC Resolved - This incident has been resolved. Jun 25, 16:12 UTC Monitoring - Confluent Cloud Metrics API experienced increased error rates from 2026-06-25 15:15 UTC to 2026-06-25 15:55 UTC. The incident has been mitigated and the systems have recovered. We are continuing to monitor. Jun 25, 15:59 UTC Investigating - We are currently investigating this issue.
Jun 23, 07:00 UTC Resolved - On June 23rd, between 7:00 to 7:16 UTC the Confluent Cloud Metrics API was unavailable. Confluent has identified the issue and restored functionality.
Jun 21, 09:19 UTC Resolved - This incident has been resolved. Jun 21, 09:19 UTC Update - We are continuing to monitor for any further issues. Jun 21, 08:31 UTC Monitoring - The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability. Jun 21, 07:14 UTC Identified - The team has identified the root cause of the issues affecting standard and basic Kafka…
Jun 16, 17:58 UTC Resolved - No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC. Jun 16, 17:58 UTC Update - No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC. Jun 16, 16:43 UTC Monitoring - We have found the root cause and have mitigated the problem as of 2026-06-16 16:09 UTC. We will monitor for any residual is…
Jun 12, 11:55 UTC Resolved - This incident has been resolved. Jun 12, 09:53 UTC Monitoring - 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…
Jun 12, 00:00 UTC Completed - The scheduled maintenance has been completed. May 28, 19:23 UTC Update - Let's Encrypt has addressed the problem they had previously identified with their cross-signed CA certificates (see https://community.letsencrypt.org/t/upcoming-let-s-encrypt-profile-changes-on-may-13/247049/4). Confluent is now resuming this maintenance operation to replace the intermediate cert…
Jun 4, 16:47 UTC Resolved - The incident has been resolved and us-east-1 (use1-az4) is fully operational. May 12, 18:51 UTC Update - 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…
May 29, 21:47 UTC Resolved - The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally. May 29, 16:49 UTC Update - 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: http…
May 22, 00:22 UTC Resolved - The incident has been resolved. May 22, 00:21 UTC Investigating - 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.
May 7, 03:08 UTC Resolved - The maintenance is complete. May 6, 22:12 UTC Monitoring - Confluent Cloud is undergoing a planned maintenance event between 4pm and 8pm PST on May 6, 2026. Customers might experience intermittent unavailability of certain pages in the customer portal, such as new customer sign-up, cluster creation, promo code claims, invoicing and public cost interfaces.
Apr 25, 00:14 UTC Resolved - This incident has been resolved. Apr 24, 23:06 UTC Monitoring - A fix has been implemented and we are monitoring for next hour. Apr 24, 22:27 UTC Update - Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes. Apr 24, 20:14 UTC Identified - The issue has been identified and fix is being rolled out. ETA for rollout complete acros…
Apr 21, 09:49 UTC Resolved - This incident has been resolved. Apr 21, 09:34 UTC Monitoring - We are experiencing delays Tableflow external catalog sync in AWS.Our team has added a fix to resolve the situation and are monitoring the same.
Mar 20, 00:55 UTC Resolved - This incident has been resolved. Mar 3, 05:34 UTC Update - 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. Mar 2, 15:37 UTC Update - Confluent Cloud services in AWS me-south-1 remain stable and operating normal…
Mar 5, 07:22 UTC Resolved - Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal. Mar 5, 04:40 UTC Monitoring - Confluent Cloud Metrics API was unavailable from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC, the incident has been mitigated and the systems are functioning well. We are continuing to monitor and will provide an upda…
Mar 1, 22:05 UTC Resolved - This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region. Mar 1, 21:41 UTC Monitoring - The problem has been mitigated as of 21:15 PM UTC today. All Confluent Cloud services are now healthy in me-central-1 region and we will monitor for any residual issues before resolving this incident in 1 hour. Mar 1, 18:48 UTC Identified -…
Feb 27, 18:16 UTC Resolved - This incident has been resolved. Feb 27, 03:25 UTC Update - We are continuing to monitor for any further issues. Feb 26, 17:41 UTC Monitoring - A fix has been implemented and we are monitoring the results Feb 26, 01:11 UTC Update - At this time, single zone clusters in us-south1 Zone-a are impacted. Feb 25, 12:02 UTC Identified - GCP has identified the issue and is act…
Feb 27, 01:57 UTC Resolved - This incident has been resolved. Feb 26, 23:07 UTC Identified - The issue has been identified and a fix is being implemented. Feb 26, 19:56 UTC Investigating - Azure is investigating the issue and we will post an update soon.