Historial de interrupciones de Confluent

1. September 1, 2026 at 4:27 PM UTCinvestigating

   Estamos investigando tasas de error elevadas y rendimiento degradado para algunos servicios que se ejecutan en la región de Google Cloud (GCP) us-central1. Esto está relacionado con un problema de red de Google Cloud que afecta a una parte de la región. Los clientes de esta región pueden experimentar problemas de provisión o desprovisionamiento de grupos, problemas de conectividad intermitente, latencia elevada o errores. Estamos evaluando activamente el alcance completo del impacto y proporcionaremos una actualización a medida que se disponga de más información.

2. September 1, 2026 at 5:14 PM UTCresolved

   La cuestión del GCP que afecta a la región nosotros-central1 ha sido mitigada y todos los servicios de Confluent Cloud en la región han regresado a su funcionamiento normal. La capacidad de suministro, las tasas de error y latencia se han recuperado a niveles previstos. Los clientes ya no deben experimentar impacto. Si continúa viendo cualquier problema, por favor contacte con Confluent Support.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 25, 2026 at 4:17 AM UTCinvestigating

   Estamos investigando problemas de conectividad y tasas de error elevadas que afectan a algunos clusters Confluentes de la Nube alojados en la región de Azure Sudeste de Asia, comenzando aproximadamente a las 03:13 UTC el 25 de agosto de 2026. Los clientes afectados pueden experimentar la disponibilidad de productos/consumo degradados o la conectividad intermitente para grupos en esta región. Esto se asocia con una perturbación continua del servicio de Microsoft Azure en la región del sudeste asiático. Estamos activamente comprometidos con Microsoft Azure.

2. August 25, 2026 at 5:28 AM UTCmonitoring

   Estamos viendo la recuperación de los servicios confluentes en la región afectada de Azure Sudeste de Asia y siguen vigilando la situación.

3. August 25, 2026 at 7:29 AM UTCresolved

   Los servicios confluentes en la región de Azure Asia sudoriental son ahora saludables y funcionan normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 24, 2026 at 3:49 PM UTCresolved

   Entre las 21:15 – 22:30 UTC y las 00:05 – 01:15 UTC el 23-24 de Agosto de 2026, el servicio de registro de nubes confluentes fue degradado. Los clientes pueden notar los registros de conexión y enlace perdidos en la interfaz de usuario de Confluent Cloud, el CLI Confluente y los destinos de integración de logging configurados durante estas ventanas. Otros tipos de registros y las cargas de trabajo Connect / Flink no se vieron afectadas. La cuestión ha sido mitigada.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 5:10 PM UTCinvestigating

   Estamos investigando un incidente que afecta a los servicios en la región del GCP nosotros-oeste1. Los clientes con cúmulos de Kafka en esta región pueden experimentar latencia elevada, solicitar los plazos o aumentar las tasas de error. Nuestros equipos de ingeniería están trabajando activamente para restaurar el rendimiento normal.

2. August 20, 2026 at 7:18 PM UTCinvestigating

   Estamos viendo la recuperación de los servicios confluentes y seguimos monitoreando la situación. La siguiente actualización será publicada dentro de 1 hora.

3. August 20, 2026 at 8:18 PM UTCresolved

   Se han mitigado las cuestiones del GCP en la región de nosotros-oeste1. Los servicios confluentes ya no están viendo ningún impacto basado en nuestro monitoreo.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 10:01 PM UTCinvestigating

   Las declaraciones de Flink se degradan en la región central y central del PCG1. El impacto comenzó a las 18:37 UTC el 17 de julio. Actualmente, los ingenieros están investigando el tema.

2. July 17, 2026 at 10:54 PM UTCidentified

   Los ingenieros han identificado y aplicado una solución.

3. July 17, 2026 at 10:55 PM UTCmonitoring

   Actualmente, estamos monitoreando los resultados después de la liquidación.

4. July 18, 2026 at 12:59 AM UTCresolved

   Todas las declaraciones deben estar funcionando ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 11:33 PM UTCinvestigating

   Confluente es consciente del incidente en curso que afecta a eu-central-1. Hemos identificado grupos de desempeño degradados que impactan en esta región, y nuestros ingenieros están trabajando activamente con AWS para mitigar la cuestión.

2. July 16, 2026 at 1:14 PM UTCresolved

   Se ha resuelto la cuestión que afecta a la región Eu-central-1 de la AWS. Todos los grupos son plenamente operacionales y saludables.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 2:25 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. July 13, 2026 at 2:36 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados

3. July 13, 2026 at 4:04 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 29, 2026 at 5:44 PM UTCidentified

   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. June 29, 2026 at 8:36 PM UTCresolved

   This incident has been resolved.

1. June 29, 2026 at 11:58 AM UTCinvestigating

   We are currently investigating this issue.

2. June 29, 2026 at 12:04 PM UTCidentified

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

3. June 29, 2026 at 12:05 PM UTCmonitoring

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

4. June 29, 2026 at 12:50 PM UTCresolved

   This incident has been resolved.

1. June 25, 2026 at 3:59 PM UTCinvestigating

   We are currently investigating this issue.

2. June 25, 2026 at 4:12 PM UTCmonitoring

   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. June 25, 2026 at 5:53 PM UTCresolved

   This incident has been resolved.

1. June 23, 2026 at 7:30 AM UTCresolved

   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.

1. June 21, 2026 at 7:14 AM UTCidentified

   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. June 21, 2026 at 8:31 AM UTCmonitoring

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

3. June 21, 2026 at 9:19 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. June 21, 2026 at 9:19 AM UTCresolved

   This incident has been resolved.

1. June 16, 2026 at 4:02 PM UTCinvestigating

   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. June 16, 2026 at 4:43 PM UTCmonitoring

   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. June 16, 2026 at 5:58 PM UTCmonitoring

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

4. June 16, 2026 at 5:58 PM UTCresolved

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

1. June 12, 2026 at 7:42 AM UTCinvestigating

   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.

2. June 12, 2026 at 9:11 AM UTCinvestigating

   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.

3. June 12, 2026 at 9:53 AM UTCmonitoring

   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.

4. June 12, 2026 at 11:55 AM UTCresolved

   This incident has been resolved.

1. May 29, 2026 at 5:57 AM UTCinvestigating

   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. May 29, 2026 at 6:47 AM UTCinvestigating

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

3. May 29, 2026 at 10:25 AM UTCmonitoring

   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. May 29, 2026 at 4:49 PM UTCmonitoring

   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

5. May 29, 2026 at 9:47 PM UTCresolved

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

1. May 22, 2026 at 12:21 AM UTCinvestigating

   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. May 22, 2026 at 12:22 AM UTCresolved

   The incident has been resolved.

1. May 8, 2026 at 1:14 AM UTCinvestigating

   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. May 8, 2026 at 1:55 AM UTCmonitoring

   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. May 9, 2026 at 1:19 PM UTCmonitoring

   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. May 12, 2026 at 6:51 PM UTCmonitoring

   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.

5. June 4, 2026 at 4:47 PM UTCresolved

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

1. April 24, 2026 at 5:18 PM UTCinvestigating

   We are currently investigating this issue.

2. April 24, 2026 at 8:14 PM UTCidentified

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

3. April 24, 2026 at 10:27 PM UTCidentified

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

4. April 24, 2026 at 11:06 PM UTCmonitoring

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

5. April 25, 2026 at 12:14 AM UTCresolved

   This incident has been resolved.

1. April 21, 2026 at 9:34 AM UTCmonitoring

   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. April 21, 2026 at 9:49 AM UTCresolved

   This incident has been resolved.

1. March 20, 2026 at 1:58 PM UTCmonitoring

   Se espera que la recuperación regional de la AWS se prorrogue tanto en las regiones mecentral-1 como en las regiones mesur-1. Se alienta a los clientes que requieran una restauración inmediata en estas dos regiones a que revisen las opciones regionales de failover.

2. April 1, 2026 at 7:52 PM UTCmonitoring

   La provisión de nuevas cargas de trabajo en las regiones de AWS me-central-1 y me-south-1 está discapacitada. Se han comunicado pasos de migración a otras regiones del AWS a clientes afectados.

3. April 2, 2026 at 3:40 PM UTCmonitoring

   Per AWS, la región me-south-1 es ahora completamente indisponible. Los clientes no podrán acceder a grupos en la región de Me-south-1. Los clientes que tienen cargas de trabajo en me-central-1 son muy recomendables para trasladarlos a una región alternativa.

4. July 16, 2026 at 3:21 AM UTCresolved

   Resolvido.

Traducido automáticamente desde la actualización oficial del incidente.