Confluent Outage History

Confluent is up right now

Pingoru has recorded 60 incidents for Confluent: 56 in the last 12 months and 19 in the last 90 days.

Source: status.confluent.cloud

60incidents recorded
56last 12 months
19last 90 days
3 daystypical duration
Incidents per month
0510AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct7%
Pingoru began tracking Confluent in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026269 of 720 (10%)
May 20263352 of 744 (47%)
June 2026717 of 720 (2%)
July 2026318 of 744 (2%)
August 2026311 of 744 (1%)
September 20261073 of 720 (10%)
October 2026641 of 589 (7%)

Incidents, newest first

Major November 5, 2025 Availability issues for Kafka clusters in Azure West Europe 1d 3h Confluent Cloud

Started Nov 05, 2025, 06:19 PM UTC· resolved Nov 06, 2025, 09:39 PM UTC

  1. investigating Nov 05, 2025, 06:19 PM UTC

    We are currently experiencing an issue that appears to be related to an ongoing incident with Microsoft Azure. We are actively working with the Azure team to confirm the impact and will provide updates as soon as more information becomes available.

  2. investigating Nov 05, 2025, 06:47 PM UTC

    We are beginning to see some recovery of the affected Kafka clusters.

  3. investigating Nov 05, 2025, 07:22 PM UTC

    We are continuing to investigate this issue.

  4. identified Nov 05, 2025, 07:51 PM UTC

    The issue was localized to a single Availability Zone in Azure West Europe region. Only Single Zone Kafka Clusters are affected at this time. Multi-Zone clusters experienced intermittent availability and elevated latency for produce and fetch requests but auto-recovered within minutes. We are continuing to work with Microsoft Azure for resolution of affected single zone clusters. We will post next update by 1:00 PST.

  5. identified Nov 05, 2025, 09:13 PM UTC

    Azure posted outage details on its status page: https://azure.status.microsoft/en-us/status. No material changes since last update. We continue monitoring the situation from our side and will provide the next update within 60 minutes or when the status changes.

  6. identified Nov 05, 2025, 10:29 PM UTC

    Azure has provided an update on it's Status Page (https://azure.status.microsoft/en-us/status) stating that recovery efforts are in progress. We will provide an update within 60 minutes.

  7. identified Nov 06, 2025, 01:48 AM UTC

    We are monitoring Azure updates and recovery closely. We are noticing partial recovery in a subset of affected resources and will provide an update as more information becomes available.

  8. monitoring Nov 06, 2025, 02:03 PM UTC

    Issues observed with Azure Europe West are now resolved. Most impacted services have recovered and are operational. We are working on resolving issues impacting performance for few customers.

  9. resolved Nov 06, 2025, 09:39 PM UTC

    All affected clusters are now fully operational.

Read the full incident report →

Notice October 29, 2025 Brief unavailability of produce requests for Enterprise SKU clusters in AWS us-east-1 –

Started Oct 29, 2025, 05:00 PM UTC· resolved Oct 29, 2025, 05:00 PM UTC

  1. resolved Oct 29, 2025, 08:58 PM UTC

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

Read the full incident report →

Major October 29, 2025 Degraded Flink statements in Azure 7h 47m Confluent Cloud

Started Oct 29, 2025, 04:55 PM UTC· resolved Oct 30, 2025, 12:42 AM UTC

  1. investigating Oct 29, 2025, 04:55 PM UTC

    Confluent engineers are engaged on the incident. The impact is related to the ongoing Azure incident. You can find more information here: https://azure.status.microsoft/en-us/status

  2. investigating Oct 29, 2025, 06:12 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 29, 2025, 06:39 PM UTC

    Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.

  4. monitoring Oct 29, 2025, 06:59 PM UTC

    Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.

  5. monitoring Oct 29, 2025, 08:35 PM UTC

    Flink statements in Azure have recovered following Microsoft’s rollback of a recent network configuration change. Confluent systems are fully operational at this time, though Microsoft is continuing to monitor the rollback and validate stability. We will remain in monitoring until Microsoft confirms full recovery.

  6. resolved Oct 30, 2025, 12:42 AM UTC

    Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.

Read the full incident report →

Major October 27, 2025 Customers are encountering a 404 error when attempting to access resources within the Confluent Cloud UI. 25m Confluent Cloud

Started Oct 27, 2025, 05:48 PM UTC· resolved Oct 27, 2025, 06:13 PM UTC

  1. investigating Oct 27, 2025, 05:48 PM UTC

    We are currently investigating the root cause.

  2. investigating Oct 27, 2025, 05:56 PM UTC

    We are currently investigating the issue. In the meantime, customers can use the CLI to manage the resources.

  3. resolved Oct 27, 2025, 06:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 22, 2025 Delayed cluster provisioning in Azure eastus region 2d 6h Confluent Cloud

Started Oct 22, 2025, 10:38 PM UTC· resolved Oct 25, 2025, 05:14 AM UTC

  1. identified Oct 22, 2025, 10:38 PM UTC

    We are experiencing provisioning delays in Azure eastus region.

  2. identified Oct 23, 2025, 08:17 PM UTC

    We've identified a mitigation method and are rolling this out across affected networks.

  3. identified Oct 23, 2025, 11:56 PM UTC

    Provisioning delays have been partially mitigated, but there may still be delays for eastus region.

  4. identified Oct 24, 2025, 05:05 PM UTC

    Dedicated private networks and dedicated Kafka clusters provisioning with PrivateLink or VNet Peering are unavailable in the Azure eastus region.

  5. resolved Oct 25, 2025, 05:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 22, 2025 Flink statements failing in multiple regions 6h 24m Confluent Cloud

Started Oct 22, 2025, 04:21 PM UTC· resolved Oct 22, 2025, 10:45 PM UTC

  1. investigating Oct 22, 2025, 04:21 PM UTC

    Flink statements are failing to execute across multiple regions. The impact started at 15:12 UTC on Oct. 22, 2025. Customers may be experiencing increased rate of degraded statements and internal errors. We are currently investigating the issue.

  2. identified Oct 22, 2025, 05:42 PM UTC

    The issue causing Flink statement failures has been identified and a hotfix has been prepared. We are actively working to mitigate all impacted compute pools.

  3. identified Oct 22, 2025, 07:04 PM UTC

    We are continuing to mitigate Flink statement failures and apply fixes to necessary compute pools. We will post an update in 1 hour, or sooner if mitigation has been completed.

  4. identified Oct 22, 2025, 08:33 PM UTC

    A fix has been applied to a number Flink compute pools, but some customers may still see failing statement failures. We are continuing to apply the fixes to the remaining impacted pools. The next update will be posted in 1 hour, or sooner if mitigation has been completed.

  5. monitoring Oct 22, 2025, 10:25 PM UTC

    All impacted Flink compute pools have been fixed and degraded statements have now recovered. We are continuing to monitor to ensure no further issues occur.

  6. resolved Oct 22, 2025, 10:45 PM UTC

    All impacted Flink compute pools have been fixed and degraded statements have recovered.

Read the full incident report →

Major October 20, 2025 Experiencing Performance Degradation in AWS in US-East-1 region 1d 2h Confluent Cloud

Started Oct 20, 2025, 09:53 AM UTC· resolved Oct 21, 2025, 12:05 PM UTC

  1. monitoring Oct 20, 2025, 09:53 AM UTC

    We are currently investigating & monitoring the issue on AWS cloud provider in US-East-1 region, customers might face elevated latency / error rates in this region.

  2. monitoring Oct 20, 2025, 10:01 AM UTC

    We are currently investigating & monitoring the issue on AWS cloud provider in US-East-1 region, customers might face elevated latency / error rates in this region.

  3. monitoring Oct 20, 2025, 11:33 AM UTC

    We are continuing to work towards full recovery and are actively monitoring the status of our services to ensure stability.

  4. investigating Oct 20, 2025, 01:56 PM UTC

    We are currently investigating an issue on AWS cloud provider in US-East-1 region, where customers in certain Availability Zones may experience increased latency or elevated error rates.

  5. investigating Oct 20, 2025, 02:23 PM UTC

    We are currently investigating an issue on AWS cloud provider in US-East-1 region, where customers may experience increased latency or elevated error rates.

  6. investigating Oct 20, 2025, 05:01 PM UTC

    We are continuing to investigate and monitor the outage on AWS cloud provider in US-East-1 region. Customers may experience increased latency or elevated error rates in that region.

  7. investigating Oct 20, 2025, 06:34 PM UTC

    We are seeing recovery for Kafka clusters and other services hosted in the AWS US-East-1 region. We will continue to monitor and apply mitigations as needed to restore all functionality in the region.

  8. monitoring Oct 20, 2025, 08:00 PM UTC

    All Kafka clusters hosted in the AWS US-East-1 region have been recovered, however customers may still experience issues related to cluster provisioning. Other Confluent Cloud services in that region are still seeing some failures and are in the process of being fully restored.

  9. monitoring Oct 20, 2025, 10:47 PM UTC

    All Kafka clusters and provisioning issues in the AWS US-East-1 region have been mitigated. Some other Confluent Cloud services in that region are still experiencing failures for a small number of customers and are in the process of being fully restored.

  10. monitoring Oct 21, 2025, 12:20 AM UTC

    We are continuing to monitor recovery for other Confluent Cloud services in the US-East-1 region are still experiencing failures for a small number of customers.

  11. monitoring Oct 21, 2025, 02:09 AM UTC

    We’re monitoring an issue affecting multiple backend systems that may cause intermittent errors and provisioning delays with API keys and potentially other services. The problem is related to an upstream service dependency, and we’re working to restore normal operation.

  12. monitoring Oct 21, 2025, 11:13 AM UTC

    We are continuing to work towards full recovery and are actively monitoring the status of our services to ensure stability.

  13. resolved Oct 21, 2025, 12:05 PM UTC

    The incident has been fully resolved, and all services are operating as expected.

Read the full incident report →

Minor October 17, 2025 Basic/Std clsuters in AWS ap-southeast-1 are experiencing degraded performance 6h 36m Confluent Cloud

Started Oct 17, 2025, 10:44 PM UTC· resolved Oct 18, 2025, 05:21 AM UTC

  1. investigating Oct 17, 2025, 10:44 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 17, 2025, 11:57 PM UTC

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

  3. resolved Oct 18, 2025, 05:21 AM UTC

    This incident has been resolved.

Read the full incident report →