64 Confluent incidents · 2025年7月 — official updates, affected components, duration and resolution details.
我们正在调查一个服务中断 影响连接 卡夫卡集群 在AWS我们东一.
我们正在继续调查这一问题.
一个可能的根源已经查明, 团结云团队正在执行一个解决方案
已执行一个固定办法,该小组正在监测恢复情况.
The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
自动翻译自官方事件更新。
我们正在调查一个服务中断 影响AWS我们东一区的多种服务。 受影响的客户可能遇到认证失败、访问Schema Registration的错误或与KSQL和Flink工作量有关的问题。 我们正在积极调查根源并努力减缓.
我们目前正在调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
我们继续努力纠正AWS我们东一号的服务中断。 确认撞击: - 认证——请求的子集可能失败 - Schema登记——对一组请求的授权错误 - ksqlDB -- -- 可能会影响一组查询/请求 - Flink — 语句管理操作( 创建/ 更新/ 删除) 退化, 一些运行中的 Flink 任务可能失败或重新启动 - Kafka操作(创建、删除等) 未受影响:卡夫卡集群数据平面操作不受此事件影响. 这个问题与AWS我们东一地区隔绝;其他区域不受影响
我们继续努力纠正AWS我们东一号的服务中断。 目前尚未确认ETA.
Confluent正在继续努力补救AWS us-east-1的服务中断.
Confluent正在继续研究AWS us-east-1的服务中断. 没有立即解决的ETA.
我们对影响Schema注册、认证、ksqlDB、Flink和AWS东一的Kafka业务的问题采取了缓解措施。 服务正在恢复,我们正在密切监测.
The systems have recovered and Confluent Cloud is fully operational.
自动翻译自官方事件更新。
我们正在调查Google Cloud(GCP)我们-中央1区域运行的一些服务的高误率和低效。 这与目前影响到该区域一部分地区的谷歌云联网问题有关。 本区域的客户可能会遇到供应或取消供应集群的问题、断断续续的连通性问题、超常或出错。 我们正在积极评估影响的全面范围,并将在获得更多信息后提供最新情况.
影响我们中一地区的GCP问题已经得到缓解,该地区所有紧凑的云服务都恢复正常运行. 供给能力、误差率和延迟率已恢复到预期水平。 客户不应再受到影响。 如果您继续看到任何问题,请联系Confluent Support.
自动翻译自官方事件更新。
我们正在调查连接问题和高误差率,这些误差率影响到在Azure东南亚地区主办的一些云群,从2026年8月25日协调世界时大约03:13开始。 受影响的客户可能经历产品退化/假定本区域集群的可用性或间歇性连接。 这与东南亚区域微软Azure服务持续中断有关。 我们正积极与微软Azure接触.
我们看到受影响的Azure东南亚地区恢复了不便的服务,并继续监测局势.
Azure东南亚地区的服务目前很健康并正常运行.
自动翻译自官方事件更新。
21:15–22:30 UTC至00:05–01:15 UTC于2026年8月23–24日,Confluent Cloud Looking服务退化. 客户可能注意到Confluent Cloud UI,Confluent CLI中缺少Connect和Flink日志,并在这些窗口中配置了日志集成目的地. 其他日志类型和连接/链接工作量本身没有受到影响。 这一问题已经得到缓解.
自动翻译自官方事件更新。
我们正在调查一起影响GCP我们西部1地区服务的事件。 本区域卡夫卡集群的客户可能会面临超常、超时或误差率上升等情况。 我们的工程团队正积极致力于恢复正常的性能.
我们看到各种服务正在恢复,并继续监测局势。 下一次更新将在1小时内公布.
我们西部1 区域的全球协商进程问题已经得到缓解。 根据我们的监测,各处不再看到任何影响.
自动翻译自官方事件更新。
在GCP我们-中央1区域,Flink语句退化. 撞击开始于协调世界时7月17日18:37. 目前,工程师正在调查这个问题.
工程师确定并实施了固定装置.
目前,我们正在对结果进行监测.
所有发言现在都应该进行.
自动翻译自官方事件更新。
Confluent知道目前影响eu-central-1的AWS事件. 我们已查明该区域退化的性能影响集群,我们的工程师正同原子能机构积极合作来缓解这一问题.
影响AWS eu-Central-1区域的问题现已得到解决。 所有集群都充分运作,健康.
自动翻译自官方事件更新。
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been 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.
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.
The team is now observing recovery. The team will continue to monitor the clusters to ensure full stability.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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.
No further issues have been observed. The incident is now resolved as of 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.
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.
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.
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.
This incident has been resolved.
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.
Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.
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
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
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
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.
The incident has been resolved.
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.
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
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.
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.
The incident has been resolved and us-east-1 (use1-az4) is fully operational.
We are currently investigating this issue.
The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
A fix has been implemented and we are monitoring for next hour.
This incident has been resolved.