Confluent Cloud

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 08:02 UTC

   Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2

2. investigating 2026-10-20 12:55 UTC

   We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.

3. monitoring 2026-10-20 14:46 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.

4. monitoring 2026-10-20 14:51 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-10-20 18:27 UTC

   This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-16 01:04 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.

2. investigating 2026-10-16 02:26 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.

3. identified 2026-10-16 03:34 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.

4. identified 2026-10-16 04:34 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

5. identified 2026-10-16 04:35 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

6. identified 2026-10-16 05:30 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...

7. monitoring 2026-10-16 06:47 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

8. monitoring 2026-10-16 07:02 UTC

   We are continuing to monitor for any further issues.

9. resolved 2026-10-16 08:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-15 16:01 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...

2. resolved 2026-10-15 18:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 23:27 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.

2. monitoring 2026-10-09 23:43 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.

3. resolved 2026-10-10 00:23 UTC

   This incident has been resolved. All affected services have fully recovered.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-09 13:34 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.

2. identified 2026-10-09 16:46 UTC

   Azure has identified the issue and recovery actions are underway

3. identified 2026-10-09 19:10 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.

4. identified 2026-10-09 20:02 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.

5. identified 2026-10-09 21:07 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.

6. identified 2026-10-09 22:04 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.

7. identified 2026-10-09 23:03 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.

8. identified 2026-10-10 00:12 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.

9. identified 2026-10-10 02:12 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.

10. identified 2026-10-10 04:15 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.

11. monitoring 2026-10-10 08:47 UTC

    A fix has been implemented and we are monitoring the results.

12. resolved 2026-10-10 09:36 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-10-08 11:00 UTC

   Users in Germany West Central region of Azure could face elevated error rates. We are currently investigating the issue and attempting to mitigate or provide a work-around.

2. monitoring 2026-10-08 11:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-10-08 11:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-27 02:00 UTC

   Confluent 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.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-26 06:40 UTC

   We are currently investigating an issue related to elevated error rates in Azure East US

2. identified 2026-09-26 08:00 UTC

   Microsoft Azure has confirmed an outage impacting their Azure East US region, which is the root cause of the elevated error rates affecting Confluent services. Confluent will provide another update as soon as we receive further details.

3. identified 2026-09-26 13:23 UTC

   Systems are continuing to recover and are being monitored

4. identified 2026-09-26 19:43 UTC

   We are continuing to work on a fix for this issue.

5. resolved 2026-09-26 19:43 UTC

   This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-09-23 11:47 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2026-09-23 14:18 UTC

   Flink in AWS us-west-2 is continues to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. All other services including Connect, ConfluentCloud UI are mitigated and operational

3. monitoring 2026-09-23 15:57 UTC

   All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.

4. resolved 2026-09-23 23:17 UTC

   This incident has been resolved. All affected services have fully recovered, and no further customer impact is expected. No action is required from customers.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-22 15:09 UTC

   We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in Microsoft Azure's Germany West Central region, beginning at approximately 13:00 UTC on 22 Sep 2026. Affected customers may experience degraded availability or...

2. monitoring 2026-09-22 19:35 UTC

   The Azure regional disruption has ended, and Confluent Cloud mitigation was achieved as of 18:00 UTC. Clusters in the Azure's Germany West Central region are now fully operational. We will monitor for residual impact before marking this incident resolved.

3. resolved 2026-09-22 19:58 UTC

   This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-21 16:04 UTC

   Starting today at 15:26 UTC, Confluent Cloud is experiencing an incident involving multiple service disruptions in the AWS us-west-2 region. We are investigating the issue and will provide further updates shortly.

2. investigating 2026-09-21 16:15 UTC

   Multiple Confluent Cloud services in the AWS us-west-2 region are experiencing elevated error rates and service disruption. Impacted customers may see failed or slow requests to Kafka clusters, Connect, and Flink in this region. The Confluent Cloud UI is also degraded and...

3. investigating 2026-09-21 16:32 UTC

   We have made progress in identifying the cause of the disruption in AWS us-west-2 and are working to confirm the safest path to mitigation. Some customers in this region may continue to experience errors or degraded performance. We will post the next update by 17:00 UTC, or...

4. investigating 2026-09-21 17:04 UTC

   We are confirming a contributing factor and applying a mitigation intended to restore Confluent Cloud services. We will post an update by 17:45 UTC, or sooner if service is restored.

5. investigating 2026-09-21 18:01 UTC

   We have refined the scope of customer impact and continue to work on a mitigation. Impacted Services: - Confluent Cloud Console (web UI), all regions: broad degradation. Customers may be unable to view or manage their resources in the Console. - Schema Registry, AWS us-west-2: a...

6. investigating 2026-09-21 18:31 UTC

   We are testing and validating several potential mitigations in parallel to restore the Confluent Cloud Console and affected services. We do not yet have a confirmed fix in place and are continuing to investigate. We will post the next update by 19:00 UTC, or sooner if service is...

7. investigating 2026-09-21 19:08 UTC

   We are continuing to investigate an incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. Several potential mitigations remain under active testing and validation. We do not yet have a confirmed fix in place. We will post the next update by...

8. investigating 2026-09-21 19:33 UTC

   We are continuing to validate several proposed mitigations to address the ongoing incident affecting the Confluent Cloud UI and other services in the AWS us-west-2 region. We do not yet have a confirmed fix in place. We will post the next update by 20:00 UTC, or sooner if...

9. investigating 2026-09-21 20:03 UTC

   We are continuing to work to resolve the incident and do not yet have a confirmed mitigation. Impact remains as previously described. We will post the next update by 20:30 UTC, or sooner if the situation changes.

10. identified 2026-09-21 20:56 UTC

    We have applied a mitigation and most affected services are beginning to recover. Flink in AWS us-west-2 will continue to be affected while we restore full service: running jobs may remain degraded and new job submissions may continue to fail during this period. We will post the...

11. identified 2026-09-21 21:30 UTC

    Most affected services are recovering and we are continuing to monitor for stability. Flink in AWS us-west-2 is still recovering and running jobs may remain degraded with new submissions still failing. We will post the next update by 22:00 UTC or sooner if the situation changes.

12. identified 2026-09-21 22:12 UTC

    Flink in AWS us-west-2 is still recovering as we continue to restore full service: running jobs may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will post the next update by 22:30...

13. identified 2026-09-21 23:06 UTC

    Flink in AWS us-west-2 is still recovering as we continue to restore full service: while some jobs may start to recover, others may remain degraded and new job submissions may still fail. Previously affected services have recovered and are being monitored for stability. We will...

14. identified 2026-09-21 23:35 UTC

    All affected services have recovered with the exception of a small number of Flink customers in AWS us-west-2 that may still experience degraded jobs while we complete recovery. We are actively working to fully restore them and will post the next update by 00:00 UTC, or sooner...

15. identified 2026-09-22 00:06 UTC

    Confluent is continuing to monitor recovered services and complete recovery for a small number of Flink customers in AWS us-west-2 that may still be experiencing degraded jobs. We are actively working to fully restore them and will post the next update by 00:30 UTC, or sooner if...

16. monitoring 2026-09-22 00:40 UTC

    All affected services, including Flink in AWS us-west-2, have recovered and we are no longer observing customer impact. We are monitoring to confirm full stability before resolving this incident.

17. resolved 2026-09-22 01:31 UTC

    This 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.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-17 17:00 UTC

   Confluent Cloud Metrics API experienced elevated latency and error rates between 9:55 AM PDT to 10:10 AM PDT.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 23:59 UTC

   Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue...

2. identified 2026-09-16 00:00 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-16 00:22 UTC

   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).

4. resolved 2026-09-16 01:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-08 20:01 UTC

   We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.

2. investigating 2026-09-08 20:13 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-08 20:20 UTC

   A possible root cause has been identified and the Confluent Cloud team is implementing a fix

4. monitoring 2026-09-08 20:30 UTC

   A fix has been implemented and the team is monitoring recovery.

5. resolved 2026-09-09 13:01 UTC

   The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-08 09:17 UTC

   We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and...

2. identified 2026-09-08 10:37 UTC

   The issue has been identified and a fix is being implemented.

3. investigating 2026-09-08 11:38 UTC

   We are currently investigating this issue.

4. identified 2026-09-08 14:06 UTC

   The issue has been identified and a fix is being implemented.

5. identified 2026-09-08 15:55 UTC

   We continue to work on remediating the service disruption in AWS us-east-1. Confirmed impact: - Authentication — a subset of requests may fail - Schema Registry — authorization errors on a subset of requests - ksqlDB — a subset of queries/requests may be affected - Flink —...

6. identified 2026-09-08 17:41 UTC

   We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.

7. identified 2026-09-09 00:01 UTC

   Confluent is continuing to work on remediating the service disruption in AWS us-east-1.

8. identified 2026-09-09 01:45 UTC

   Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.

9. monitoring 2026-09-09 06:41 UTC

   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.

10. resolved 2026-09-09 14:56 UTC

    The systems have recovered and Confluent Cloud is fully operational.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 16:27 UTC

   We are investigating elevated error rates and degraded performance for some services running in the Google Cloud (GCP) us-central1 region. This is related to an ongoing Google Cloud networking issue affecting a portion of the region. Customers in this region may experience...

2. resolved 2026-09-01 17:14 UTC

   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....

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-25 04:17 UTC

   We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in the Azure Southeast Asia region, beginning at approximately 03:13 UTC on 25 Aug 2026. Affected customers may experience degraded produce/consume availability or...

2. monitoring 2026-08-25 05:28 UTC

   We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.

3. resolved 2026-08-25 07:29 UTC

   Confluent services in the Azure Southeast Asia region are now healthy and operating normally.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-23 21:00 UTC

   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...

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 17:10 UTC

   We are investigating an incident affecting services in the GCP us-west1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates. Our engineering teams are actively working to restore normal performance.

2. investigating 2026-08-20 19:18 UTC

   We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.

3. resolved 2026-08-20 20:18 UTC

   The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-17 22:01 UTC

   Flink statements are degraded in GCP us-central1 region. The impact started at 18:37 UTC on July 17. Currently, engineers are investigating the issue.

2. identified 2026-07-17 22:54 UTC

   Engineers have identified and implemented a fix.

3. monitoring 2026-07-17 22:55 UTC

   Currently, we are monitoring the results after rolling out the fix.

4. resolved 2026-07-18 00:59 UTC

   All the statements should be running now.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-15 23:33 UTC

   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.

2. resolved 2026-07-16 13:14 UTC

   The issue impacting the AWS eu-central-1 region has now been resolved. All clusters are fully operational and healthy.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-13 14:25 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-07-13 14:36 UTC

   A fix has been implemented and we are monitoring the results

3. resolved 2026-07-13 16:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-06-29 17:44 UTC

   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.

2. resolved 2026-06-29 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 11:40 UTC

   We are currently investigating this issue.

2. identified 2026-06-29 12:04 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-06-29 12:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-29 12:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 15:59 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-25 16:12 UTC

   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.

3. resolved 2026-06-25 17:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-23 07:00 UTC

   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.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-06-21 07:14 UTC

   The team has identified the root cause of the issues affecting standard and basic Kafka clusters in the AWS us-east-2 region. We are actively working on a mitigation strategy and will provide further updates as they become available.

2. monitoring 2026-06-21 08:31 UTC

   The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.

3. monitoring 2026-06-21 09:19 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-06-21 09:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-06-16 16:02 UTC

   We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:20 UTC. We are currently investigating and will update as we know more.

2. monitoring 2026-06-16 16:43 UTC

   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 issues before resolving this incident in 1 hour.

3. monitoring 2026-06-16 17:58 UTC

   No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

4. resolved 2026-06-16 17:58 UTC

   No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-12 07:42 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...

2. investigating 2026-06-12 09:11 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...

3. monitoring 2026-06-12 09:53 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...

4. resolved 2026-06-12 11:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Power/cooling issues in West US 2.

1. investigating 2026-05-29 05:57 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.

2. investigating 2026-05-29 06:47 UTC

   Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.

3. monitoring 2026-05-29 10:25 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

4. monitoring 2026-05-29 16:49 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:...

5. resolved 2026-05-29 21:47 UTC

   The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-22 00:21 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.

2. resolved 2026-05-22 00:22 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 01:14 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.

2. monitoring 2026-05-08 01:55 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

3. monitoring 2026-05-09 13:19 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 verifying full service restoration.

4. monitoring 2026-05-12 18:51 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...

5. resolved 2026-06-04 16:47 UTC

   The incident has been resolved and us-east-1 (use1-az4) is fully operational.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-05-06 22:12 UTC

   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...

2. resolved 2026-05-07 03:08 UTC

   The maintenance is complete.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Control plane issues in East US.

1. investigating 2026-04-24 17:18 UTC

   We are currently investigating this issue.

2. identified 2026-04-24 20:14 UTC

   The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.

3. identified 2026-04-24 22:27 UTC

   Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.

4. monitoring 2026-04-24 23:06 UTC

   A fix has been implemented and we are monitoring for next hour.

5. resolved 2026-04-25 00:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-04-21 09:34 UTC

   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.

2. resolved 2026-04-21 09:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-03-20 13:58 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.

2. monitoring 2026-04-01 19:52 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.

3. monitoring 2026-04-02 15:40 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.

4. resolved 2026-07-16 03:21 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-03-05 04:40 UTC

   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 update on or before 2026-03-05 06:40 UTC.

2. resolved 2026-03-05 07:22 UTC

   Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

1. investigating 2026-03-02 07:19 UTC

   We are experiencing increased error rates in some of our Confluent Cloud services in AWS me-south-1 and me-central-1 regions. This began at approximately 05:00 AM UTC today and is linked to disruptions in AWS’s availability zones in these regions (mec1-az1, mec1-az3 and...

2. investigating 2026-03-02 08:32 UTC

   Confluent Cloud services in AWS me-central-1 region are experiencing a major outage. They are linked to AWS's me-central-1 regional outage Confluent Cloud services in AWS me-south-1 are being mitigated.

3. monitoring 2026-03-02 10:35 UTC

   Confluent cloud services in AWS me-south-1 are mitigated. They are currently being monitored. Confluent Cloud Services in AWS me-central-1 are still disrupted owing to regional outage at AWS.

4. monitoring 2026-03-02 15:37 UTC

   Confluent Cloud services in AWS me-south-1 remain stable and operating normally following mitigation. We continue to monitor for any residual issues. Confluent Cloud services in AWS me-central-1 continue to experience a complete outage due to the ongoing AWS regional...

5. monitoring 2026-03-03 05:34 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.

6. resolved 2026-03-20 00:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. investigating 2026-03-01 18:08 UTC

   We are experiencing increased error rates in some of our Confluent Cloud services in the AWS me-central-1 region. This began at approximately 12:51 PM UTC today and is linked to a disruption in one of AWS’s availability zones (mec1-az2). Our team is actively applying mitigation...

2. identified 2026-03-01 18:48 UTC

   We have identified the cause of the problem to be disruption in one of AWS’s availability zones (mec1-az2). We are taking steps to confirm the safest path to mitigation for any impacted Confluent Cloud services in this region.

3. monitoring 2026-03-01 21:41 UTC

   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.

4. resolved 2026-03-01 22:05 UTC

   This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-02-26 19:56 UTC

   Azure is investigating the issue and we will post an update soon.

2. identified 2026-02-26 23:07 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-02-27 01:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-02-26 13:59 UTC

   Provisioning new networks in this region can potentially fail. We are investigating the issue and will post an update soon.

2. monitoring 2026-02-26 22:23 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-26 22:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-02-25 05:01 UTC

   We are currently investigating the issue

2. identified 2026-02-25 12:02 UTC

   GCP has identified the issue and is actively working on applying mitigation.

3. identified 2026-02-26 01:11 UTC

   At this time, single zone clusters in us-south1 Zone-a are impacted.

4. monitoring 2026-02-26 17:41 UTC

   A fix has been implemented and we are monitoring the results

5. monitoring 2026-02-27 03:25 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-02-27 18:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-02-24 21:15 UTC

   We are experiencing an elevated level of Kafka REST API Errors with error code 429 in AWS us-west-2 and are currently looking into the issue. This issue impacts Kafka eSKU clusters in this regions.

2. investigating 2026-02-24 21:16 UTC

   We are currently working on a mitigation.

3. investigating 2026-02-24 21:16 UTC

   We are continuing to investigate this issue.

4. identified 2026-02-25 00:33 UTC

   Issue has been identified and we are currently deploying the fix.

5. resolved 2026-02-25 01:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-02-23 22:12 UTC

   We are currently investigating this issue.

2. investigating 2026-02-23 22:17 UTC

   Starting 2/21/2026, 21:00 UTC We are observing Elevated Kafka Latency in GCP asia-southeast1 region for less than 0.1% of produce and fetch requests for some customers. Median latencies for both produce and fetch requests are not impacted. We are actively working with GCP to...

3. investigating 2026-02-23 22:18 UTC

   We are continuing to investigate this issue.

4. investigating 2026-02-24 00:23 UTC

   We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.

5. monitoring 2026-02-24 07:27 UTC

   GCP has identified the root cause and has fixed the same. Currently monitoring.

6. resolved 2026-02-24 09:58 UTC

   The issue was resolved successfully. All systems working as expected.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-02-11 22:14 UTC

   Confluent has been experiencing failures creating all new clusters in Azure westus3, southcentralus, and eastus2. The impact started at 09:50 UTC on Wednesday, February 11, 2026. We are investigating and will provide another update in 30 minutes or sooner if mitigation has been...

2. investigating 2026-02-11 22:50 UTC

   We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.

3. identified 2026-02-12 00:07 UTC

   The issue has been identified with Azure support and working on mitigating failed cluster creations. We will provide another update in the next 90 minutes or sooner if mitigation has been achieved.

4. identified 2026-02-12 01:58 UTC

   We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.

5. resolved 2026-02-12 02:45 UTC

   The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-03 21:33 UTC

   We are currently investigating this issue.

2. identified 2026-02-03 23:25 UTC

   We’ve identified the cause of the connection issues and are reverting a recent configuration change. Service stability is improving as the rollback progresses. We’ll continue monitoring and provide an update once all services are confirmed restored.

3. monitoring 2026-02-04 00:08 UTC

   Confluent has identified the cause of the issue and reverted the related configuration change. During the incident, some Kafka clusters experienced intermittent connectivity issues, and some control plane services, including metrics, logging, authentication, and new cluster...

4. resolved 2026-02-04 00:48 UTC

   The 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, resulting in intermittent service disruption across several...

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-01-08 12:30 UTC

   We are currently investigating this issue.

2. monitoring 2026-01-08 13:09 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-08 16:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-12-16 06:00 UTC

   Metrics API /export endpoint was emitting 400 errors from 06:02 UTC to 10:20 UTC

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-08 17:48 UTC

   We are investigating an issue with missing metrics affecting a small number of Confluent Cloud Kafka clusters.

2. investigating 2025-12-08 20:44 UTC

   We are mitigating the impacted clusters and continuing to investigate the root cause.

3. identified 2025-12-09 01:13 UTC

   The mitigation is nearing completion and we have seen recovery on most clusters. The root cause has been identified.

4. monitoring 2025-12-09 14:51 UTC

   Normal metrics operations have been restored for all originally affected clusters. We are actively monitoring for any new occurrences of the issue.

5. resolved 2025-12-10 04:48 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.

Affected: Confluent Cloud

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-12-02 21:37 UTC

   This manifests itself in new Flink jobs remaining stuck in "Statement Status: Pending", existing Flink jobs being requested to stop remaining stuck in "Statement Status: Stopping". This issue started manifesting at 2025-12-02 19:53 UTC. We are currently investigating the issue...

2. identified 2025-12-02 22:03 UTC

   The root cause for the issue has been identified and the team is working on applying a mitigation.

3. identified 2025-12-02 23:14 UTC

   The team has successfully applied a fix to asia-northeast1 and we're seeing recovery there. Meanwhile the team is applying mitigations in the other affected regions.

4. monitoring 2025-12-03 01:32 UTC

   A fix has been applied to all regions and we've seen recovery in all affected regions. We'll continue to monitor for the next 30 minutes.

5. resolved 2025-12-03 02:04 UTC

   No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.

Excerpts are shortened. Read the full incident on Confluent Cloud's status page.