- Detected by Pingoru
- Jun 16, 2026, 04:02 PM UTC
- Resolved
- Jun 16, 2026, 05:58 PM UTC
- Duration
- 1h 56m
Affected: Confluent Cloud
Timeline · 4 updates
-
investigating Jun 16, 2026, 04:02 PM UTC
We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:50 UTC. We are currently investigating and will update as we know more.
-
monitoring Jun 16, 2026, 04:43 PM 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.
-
monitoring Jun 16, 2026, 05:58 PM UTC
No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.
-
resolved Jun 16, 2026, 05:58 PM UTC
No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 07:42 AM UTC
- Resolved
- Jun 12, 2026, 11:55 AM UTC
- Duration
- 4h 12m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 06:47 AM UTC
- Resolved
- May 29, 2026, 09:47 PM UTC
- Duration
- 15h
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 12:21 AM UTC
- Resolved
- May 22, 2026, 12:22 AM UTC
- Duration
- 1m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:14 AM UTC
- Resolved
- Jun 04, 2026, 04:47 PM UTC
- Duration
- 27d 15h
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 05:18 PM UTC
- Resolved
- Apr 25, 2026, 12:14 AM UTC
- Duration
- 6h 56m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 09:34 AM UTC
- Resolved
- Apr 21, 2026, 09:49 AM UTC
- Duration
- 14m
Affected: Confluent Cloud
Timeline · 2 updates
-
monitoring Apr 21, 2026, 09:34 AM 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.
-
resolved Apr 21, 2026, 09:49 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 04:40 AM UTC
- Resolved
- Mar 05, 2026, 07:22 AM UTC
- Duration
- 2h 42m
Affected: Confluent Cloud
Timeline · 2 updates
-
monitoring Mar 05, 2026, 04:40 AM 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.
-
resolved Mar 05, 2026, 07:22 AM UTC
Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 07:19 AM UTC
- Resolved
- Mar 20, 2026, 12:55 AM UTC
- Duration
- 17d 17h
Affected: Confluent Cloud
Timeline · 6 updates
-
investigating Mar 02, 2026, 07:19 AM 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 mes1-az2). Team is currently working on mitigating these and will provide updates as the situation evolves.
-
investigating Mar 02, 2026, 08:32 AM 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.
-
monitoring Mar 02, 2026, 10:35 AM 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.
-
monitoring Mar 02, 2026, 03:37 PM 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 infrastructure failure in that region.
-
monitoring Mar 03, 2026, 05:34 AM 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.
-
resolved Mar 20, 2026, 12:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 06:08 PM UTC
- Resolved
- Mar 01, 2026, 10:05 PM UTC
- Duration
- 3h 57m
Affected: Confluent Cloud
Timeline · 4 updates
-
investigating Mar 01, 2026, 06:08 PM 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 steps and will provide updates as the situation evolves.
-
identified Mar 01, 2026, 06:48 PM 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.
-
monitoring Mar 01, 2026, 09:41 PM 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.
-
resolved Mar 01, 2026, 10:05 PM UTC
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 07:56 PM UTC
- Resolved
- Feb 27, 2026, 01:57 AM UTC
- Duration
- 6h 1m
Affected: Confluent Cloud
Timeline · 3 updates
-
investigating Feb 26, 2026, 07:56 PM UTC
Azure is investigating the issue and we will post an update soon.
-
identified Feb 26, 2026, 11:07 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Feb 27, 2026, 01:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 01:59 PM UTC
- Resolved
- Feb 26, 2026, 10:24 PM UTC
- Duration
- 8h 24m
Affected: Confluent Cloud
Timeline · 3 updates
-
investigating Feb 26, 2026, 01:59 PM UTC
Provisioning new networks in this region can potentially fail. We are investigating the issue and will post an update soon.
-
monitoring Feb 26, 2026, 10:23 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 26, 2026, 10:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 05:01 AM UTC
- Resolved
- Feb 27, 2026, 06:16 PM UTC
- Duration
- 2d 13h
Affected: Confluent Cloud
Timeline · 6 updates
-
investigating Feb 25, 2026, 05:01 AM UTC
We are currently investigating the issue
-
identified Feb 25, 2026, 12:02 PM UTC
GCP has identified the issue and is actively working on applying mitigation.
-
identified Feb 26, 2026, 01:11 AM UTC
At this time, single zone clusters in us-south1 Zone-a are impacted.
-
monitoring Feb 26, 2026, 05:41 PM UTC
A fix has been implemented and we are monitoring the results
-
monitoring Feb 27, 2026, 03:25 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 27, 2026, 06:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 09:15 PM UTC
- Resolved
- Feb 25, 2026, 01:07 AM UTC
- Duration
- 3h 52m
Affected: Confluent Cloud
Timeline · 5 updates
-
investigating Feb 24, 2026, 09:15 PM 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.
-
investigating Feb 24, 2026, 09:16 PM UTC
We are currently working on a mitigation.
-
investigating Feb 24, 2026, 09:16 PM UTC
We are continuing to investigate this issue.
-
identified Feb 25, 2026, 12:33 AM UTC
Issue has been identified and we are currently deploying the fix.
-
resolved Feb 25, 2026, 01:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 10:12 PM UTC
- Resolved
- Feb 24, 2026, 09:58 AM UTC
- Duration
- 11h 45m
Affected: Confluent Cloud
Timeline · 6 updates
-
investigating Feb 23, 2026, 10:12 PM UTC
We are currently investigating this issue.
-
investigating Feb 23, 2026, 10:17 PM 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 identify the root cause of the issue. We will provide next update in 2 hours or earlier.
-
investigating Feb 23, 2026, 10:18 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 24, 2026, 12:23 AM UTC
We are continuing to investigate this issue with GCP. GCP is actively working on applying mitigation.
-
monitoring Feb 24, 2026, 07:27 AM UTC
GCP has identified the root cause and has fixed the same. Currently monitoring.
-
resolved Feb 24, 2026, 09:58 AM UTC
The issue was resolved successfully. All systems working as expected.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 10:14 PM UTC
- Resolved
- Feb 12, 2026, 02:45 AM UTC
- Duration
- 4h 30m
Affected: Confluent Cloud
Timeline · 5 updates
-
investigating Feb 11, 2026, 10:14 PM 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 achieved.
-
investigating Feb 11, 2026, 10:50 PM UTC
We are continuing to investigate. Our next update will be in 90 minutes or sooner if mitigation has been achieved.
-
identified Feb 12, 2026, 12:07 AM 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.
-
identified Feb 12, 2026, 01:58 AM UTC
We are continuing to work on mitigation for new cluster creations. We will provide another update in the next 60 minutes or sooner.
-
resolved Feb 12, 2026, 02:45 AM UTC
The incident has been resolved. New cluster creation in the Azure westus3, southcentralus, and eastus2 regions have been fixed.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 09:33 PM UTC
- Resolved
- Feb 04, 2026, 12:48 AM UTC
- Duration
- 3h 14m
Affected: Confluent Cloud
Timeline · 4 updates
-
investigating Feb 03, 2026, 11:10 PM UTC
We are currently investigating this issue.
-
identified Feb 03, 2026, 11:25 PM 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.
-
monitoring Feb 04, 2026, 12:08 AM 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 provisioning, were briefly impacted. The issue has been mitigated, services are stable, and we continue to monitor.
-
resolved Feb 04, 2026, 12:48 AM 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 Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 12:30 PM UTC
- Resolved
- Jan 08, 2026, 04:25 PM UTC
- Duration
- 3h 55m
Affected: Confluent Cloud
Timeline · 3 updates
-
investigating Jan 08, 2026, 12:30 PM UTC
We are currently investigating this issue.
-
monitoring Jan 08, 2026, 01:09 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 08, 2026, 04:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 11:02 AM UTC
- Resolved
- Dec 16, 2025, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 16, 2025, 11:02 AM UTC
Metrics API /export endpoint was emitting 400 errors from 06:02 UTC to 10:20 UTC
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 05:48 PM UTC
- Resolved
- Dec 10, 2025, 04:48 AM UTC
- Duration
- 1d 10h
Affected: Confluent Cloud
Timeline · 5 updates
-
investigating Dec 08, 2025, 05:48 PM UTC
We are investigating an issue with missing metrics affecting a small number of Confluent Cloud Kafka clusters.
-
investigating Dec 08, 2025, 08:44 PM UTC
We are mitigating the impacted clusters and continuing to investigate the root cause.
-
identified Dec 09, 2025, 01:13 AM UTC
The mitigation is nearing completion and we have seen recovery on most clusters. The root cause has been identified.
-
monitoring Dec 09, 2025, 02:51 PM UTC
Normal metrics operations have been restored for all originally affected clusters. We are actively monitoring for any new occurrences of the issue.
-
resolved Dec 10, 2025, 04:48 AM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 09:37 PM UTC
- Resolved
- Dec 03, 2025, 02:04 AM UTC
- Duration
- 4h 26m
Affected: Confluent Cloud
Timeline · 5 updates
-
investigating Dec 02, 2025, 09:37 PM 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 and attempting to mitigate or provide a work-around.
-
identified Dec 02, 2025, 10:03 PM UTC
The root cause for the issue has been identified and the team is working on applying a mitigation.
-
identified Dec 02, 2025, 11:14 PM 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.
-
monitoring Dec 03, 2025, 01:32 AM 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.
-
resolved Dec 03, 2025, 02:04 AM UTC
No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.
Read the full incident report →
- Detected by Pingoru
- Nov 28, 2025, 01:25 PM UTC
- Resolved
- Nov 28, 2025, 06:33 PM UTC
- Duration
- 5h 8m
Affected: Confluent Cloud
Timeline · 3 updates
-
identified Nov 28, 2025, 01:25 PM UTC
We've identified the issue; a hotfix is on its way to production.
-
identified Nov 28, 2025, 06:02 PM UTC
We have fixed the issue, and are now monitoring the few affected tables to ensure they all return to full operation. As of Nov 28th 6:00PM UTC customers should see normal operations with Confluent systems.
-
resolved Nov 28, 2025, 06:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 01:00 AM UTC
- Resolved
- Nov 21, 2025, 01:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 21, 2025, 03:09 AM UTC
Some of the Freight customers in AWS us-east-1 could have experienced latency spikes intermittently
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 02:28 PM UTC
- Resolved
- Nov 17, 2025, 09:07 PM UTC
- Duration
- 6h 39m
Affected: Confluent Cloud
Timeline · 5 updates
-
investigating Nov 17, 2025, 02:28 PM UTC
We are experiencing issues with the availability of recent Connector event logs across all regions and cluster types. The problem started at 09:00 UTC on November 17, 2025. We are currently investigating, and will update as we know more.
-
investigating Nov 17, 2025, 02:38 PM UTC
We are continuing to investigate this issue.
-
identified Nov 17, 2025, 03:29 PM UTC
We have identified the cause of the issue and have begun mitigation steps. Our investigation confirmed that some connector log events were lost as a result of this issue. The mitigation currently in progress will prevent further log loss, but we will be unable to recover the events that were previously lost. The full mitigation is expected to take up to 8 hours to complete for all clusters. We will provide a further update within the next 2 hours.
-
monitoring Nov 17, 2025, 07:53 PM UTC
A fix has been implemented, ensuring no further log loss. All subsequent connector log events are now available, and we will continue monitoring the results.
-
resolved Nov 17, 2025, 09:07 PM UTC
This issue has been resolved, and there should be no further log loss. All subsequent connector log events are now accessible.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 06:19 PM UTC
- Resolved
- Nov 06, 2025, 09:39 PM UTC
- Duration
- 1d 3h
Affected: Confluent Cloud
Timeline · 9 updates
Read the full incident report →
