63 Confluent incidents · juli 2025 — official updates, affected components, duration and resolution details.
Vi er ved at undersøge en tjenesteforstyrrelse, der påvirker flere tjenester i AWS us-East-1-regionen. Berørte kunder kan opleve autentificeringsfejl, fejl ved adgang til Schema Registry, eller problemer med KSQL og Flink workloads. Vi undersøger aktivt årsagen og arbejder hen imod afbødning.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger forhøjede fejlrater og forringet ydeevne for nogle tjenester, der kører i Google Cloud (GCP) us- central 1-regionen. Dette er relateret til et igangværende Google Cloud-netværksproblem, der påvirker en del af regionen. Kunder i denne region kan opleve problemer levering eller deprovisering klynger, intermitterende forbindelse problemer, forhøjet latency, eller fejl. Vi er aktivt ved at vurdere det fulde omfang af virkningen og vil give en opdatering, efterhånden som flere oplysninger bliver tilgængelige.
GCP-problemet, der påvirker den centrale region, er blevet afbødet, og alle Confluent Cloud-tjenester i regionen er vendt tilbage til normal drift. Provisionering kapacitet, fejlrater og latency er kommet til forventede niveauer. Kunderne bør ikke længere opleve effekt. Hvis du fortsætter med at se nogen problemer, bedes du kontakte Confluent Support.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er ved at undersøge konnektivitet problemer og forhøjede fejlrater påvirker nogle Confluent Cloud klynger hostet i Azure Sydøstasien region, der begynder omkring 03: 13 UTC på 25 Aug 2026. Berørte kunder kan opleve forringet produktion / forbrug tilgængelighed eller intermitterende forbindelse for klynger i denne region. Dette er forbundet med en igangværende Microsoft Azure service afbrydelse i Sydøstasien region. Vi er aktivt engageret i Microsoft Azure.
Vi ser en genopretning af sammenfletningen i den berørte region Azure Sydøstasien og følger fortsat situationen.
Konfluente tjenester i Azure Sydøstasien regionen er nu sunde og fungerer normalt.
Automatisk oversat fra den officielle hændelsesopdatering.
Mellem 21: 15 - 22: 30 UTC og 00: 05 - 01: 15 UTC på aug 23-24, 2026, Confluent Cloud logning service blev nedbrudt. Kunder kan bemærke manglende Connect og Flink logs i Confluent Cloud UI, Confluent CLI, og konfigureret logning integration destinationer under disse vinduer. Andre log typer og Connect / Flink arbejdsbelastninger selv var upåvirket. Spørgsmålet er blevet afhjulpet.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi undersøger en hændelse, der påvirker tjenester i GCP us-west1-regionen. Kunder med Kafka klynger i denne region kan opleve forhøjet latency, anmode timeouts, eller øgede fejlrater. Vores ingeniørhold arbejder aktivt på at genoprette normal ydeevne.
Vi er vidne til en genopretning af sammenfaldende tjenester og følger fortsat situationen. Den næste opdatering vil blive sendt inden for 1 time.
GCP-spørgsmålene i us-west1-regionen er blevet afbødet. Konfluente tjenester ser ikke længere nogen virkning baseret på vores overvågning.
Automatisk oversat fra den officielle hændelsesopdatering.
Flinkopgørelser nedbrydes i GCP-us-Central1-regionen. Virkningen startede kl. 18.37 UTC den 17. juli. Ingeniørerne undersøger sagen.
Ingeniører har identificeret og implementeret et fix.
I øjeblikket overvåger vi resultaterne efter rulning af fix.
Alle udsagnene burde køre nu.
Automatisk oversat fra den officielle hændelsesopdatering.
Konfluent er klar over den igangværende AWS hændelse påvirker eu- central-1. Vi har identificeret forringet ydeevne påvirker klynger i denne region, og vores ingeniører arbejder aktivt med AWS for at afbøde problemet.
Det spørgsmål, der berører regionen AWS eucentral, er nu løst. Alle klynger er fuldt operationelle og sunde.
Automatisk oversat fra den officielle hændelsesopdatering.
Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.
Et fix er blevet gennemført, og vi overvåger resultaterne
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
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.
This incident has been resolved.