Confluent change history

Confluent reported a major Confluent Cloud outage in AWS us-east-1; Kafka clusters could experience elevated latency, request timeouts, or increased error rates. It started at 2026-10-09 23:27 UTC and was resolved at 2026-10-10 00:23 UTC, lasting 56 min. All affected services recovered; no customer action was required, and the root cause remained under investigation with the provider.

Confluent Cloud experienced elevated error rates and degraded performance in Azure West Europe, with major impact. The incident started at 2026-10-09 23:03 UTC and was resolved at 2026-10-10 09:36 UTC, lasting 10 h 33 min; Azure identified the issue, and a fix was implemented.

Confluent Cloud users in Azure’s Germany West Central region could face elevated error rates in a major-impact incident starting 2026-10-08 11:00 UTC and lasting 55 min. A fix was implemented by 2026-10-08 11:38 UTC, and the incident was resolved at 2026-10-08 11:56 UTC.

Confluent reported a major degradation: Cloud Metrics were delayed from 00:33 to 02:15 UTC on Sep 27, potentially leaving recent-metrics queries incomplete or empty. Marked resolved, its timestamps conflict: start 2026-09-27 17:17 UTC, resolution 2026-09-27 02:00 UTC, and update-stated resolution 02:15 UTC; computed duration is unknown.

Confluent reported a major incident degrading Cloud Console in all regions and multiple services in AWS us-west-2, including degraded Flink jobs and failed new job submissions. It started at 2026-09-23 11:47 UTC and was resolved at 2026-09-23 23:17 UTC, lasting 11 h 29 min. All affected services recovered; no customer action was required.

A major Confluent Cloud incident caused elevated errors and intermittent connectivity for some clusters in Azure Germany West Central, associated with an Azure disruption. Issues began approximately 13:00 UTC on 22 Sep 2026; recorded start: 2026-09-22 15:09 UTC. Mitigation: 18:00 UTC; resolved: 2026-09-22 19:58 UTC; tracked duration: 4 h 49 min.

Confluent recorded a major incident starting 2026-09-21 16:15 UTC: Kafka, Connect, and Flink requests failed or slowed in AWS us-west-2, while Cloud Console degradation affected cluster visibility across regions. Resolved at 2026-09-22 01:31 UTC after 9 h 16 min; all affected services recovered, and no customer action was required.

Multiple Confluent Cloud services degraded across all regions, with major impact; the vendor reported onset at 21:25 UTC on September 15th 2026. The recorded incident ran from 2026-09-15 23:59 UTC to resolution at 2026-09-16 01:21 UTC (1 h 22 min); mitigation was deployed and services were recovering by 00:20 UTC on September 16th, 2026.

Confluent Cloud reported a major connectivity disruption affecting Kafka clusters in AWS us-east-1, starting 2026-09-08 20:01 UTC and resolved 2026-09-09 13:01 UTC (reported duration: 16 h 59 min). A fix was implemented at 09-08 20:30 UTC; connectivity was reported fully operational at resolution.

Confluent reported a major Confluent Cloud degradation in Azure Southeast Asia, with elevated errors, latency and intermittent connectivity affecting produce/consume availability. Recorded from 2026-08-25 04:17 UTC to 2026-08-25 07:29 UTC (3 h 11 min), it reportedly began around 03:13 UTC and was associated with a Microsoft Azure disruption; services returned to normal.

Confluent Cloud reported a major incident affecting Kafka clusters in GCP us-west1, with elevated latency, request timeouts, and increased error rates. It started at 2026-08-20 17:10 UTC and was resolved at 2026-08-20 20:18 UTC, lasting 3 h 7 min. Confluent said the GCP issues were mitigated and monitoring showed no remaining impact.

Confluent reported a major Confluent Cloud Metrics API incident starting 2026-06-25 15:59 UTC, resolved at 2026-06-25 17:53 UTC after 1 h 54 min. The vendor reported increased error rates from 2026-06-25 15:15 UTC to 2026-06-25 15:55 UTC and said the incident was mitigated and systems recovered.

Confluent Cloud reported major intermittent inter-region connectivity degradation affecting AWS us-west-2, causing delays or errors with Cluster Linking, Flink processing, and UI log access. Recorded start: 2026-06-12 07:42 UTC; the vendor later stated approximately 04:00 UTC. A mitigation was deployed; resolution was recorded at 2026-06-12 11:55 UTC, with a computed duration of 4 h 12 min.

Confluent Cloud had a major outage with elevated errors and latencies in Azure westus2, linked to Azure network connectivity degradation. The incident ran from 2026-05-29 06:47 UTC to 2026-05-29 21:47 UTC (15 h 0 min), though Confluent reported symptoms beginning around 05:10 UTC. Azure’s degradation was mitigated and Confluent Cloud returned to normal.

Confluent Cloud reported major connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2, starting 20:26 UTC May 21, 2026. Confluent stated full mitigation by 23:56 UTC May 21, 2026, with service operating normally. The resolved incident record’s computed duration was 1 min.

Confluent Cloud reported a major incident affecting produce/consume operations in AWS us-east-1 AZ4, with elevated errors, latency and lingering connectivity issues. It started 2026-05-08 01:14 UTC and resolved 2026-06-04 16:47 UTC, lasting 27 days 15 h. Confluent attributed the initial impact to EC2 power loss during a thermal event and confirmed full operation at resolution.

Confluent Cloud experienced delays in Tableflow external catalog syncs in AWS, rated major impact, starting 2026-04-21 09:34 UTC. Confluent reported applying a fix and monitoring; the incident was resolved at 2026-04-21 09:49 UTC, with a computed duration of 14 min.

Confluent Cloud’s major incident in AWS me-south-1 and me-central-1 started 2026-04-01 19:52 UTC and resolved 2026-07-16 03:21 UTC, lasting 105 days 7 h. New workload provisioning was disabled in both regions; me-south-1 became completely unavailable, preventing cluster access. Confluent communicated migration steps and advised relocating me-central-1 workloads to another region.

Confluent reported a major Confluent Cloud Metrics API outage, with unavailability from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC. The incident record ran from 2026-03-05 04:40 UTC to resolution at 2026-03-05 07:22 UTC (2 h 42 min). Confluent reported mitigation and confirmed normal operation at resolution.

Confluent Cloud’s major incident affected AWS me-south-1 and me-central-1, including a complete outage in me-central-1 caused by AWS regional infrastructure failure. Errors began approximately 05:00 AM UTC on March 2; the recorded start was 2026-03-02 07:19 UTC. me-south-1 was mitigated, and the incident resolved 2026-03-20 00:55 UTC after 17 days 17 h.

Confluent Cloud experienced elevated errors in AWS me-central-1 due to disruption in AWS availability zone mec1-az2, with major impact. Errors began approximately 12:51 PM UTC; the incident was recorded from 2026-03-01 18:08 UTC to 2026-03-01 22:05 UTC (3 h 57 min). Confluent applied mitigation and reported all regional services healthy.

Confluent reported a major Confluent Cloud outage affecting all new dedicated Kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2. It lasted 6 h 1 min, from 2026-02-26 19:56 UTC to 2026-02-27 01:57 UTC; the issue was identified, a fix was being implemented, and the incident was subsequently resolved.

Confluent Cloud experienced a major network provisioning degradation in Azure East US: provisioning new networks could fail. It started at 2026-02-26 13:59 UTC and was resolved at 2026-02-26 22:24 UTC, lasting 8 h 24 min. Confluent reported implementing a fix at 02-26 22:23 UTC but did not state a cause.

Confluent reported a major incident involving elevated error rates for some Confluent Cloud customers in GCP us-south1, with single zone clusters in us-south1 Zone-a impacted. It started 2026-02-25 05:01 UTC and was resolved 2026-02-27 18:16 UTC, lasting 2 days 13 h. GCP identified the issue; a fix was implemented and monitored.

Confluent reported a major outage preventing all new Confluent Cloud cluster creations in Azure westus3, southcentralus, and eastus2, with customer impact starting February 11, 2026 at 09:50 UTC. The recorded incident lasted 4 h 30 min and was resolved at 2026-02-12 02:45 UTC; Confluent identified the issue with Azure support and confirmed cluster creation was fixed.

Confluent reported a major Confluent Cloud outage starting 2026-02-03 21:33 UTC, resolved 2026-02-04 00:48 UTC (3 h 14 min). A networking configuration change in us-west-2 caused intermittent client connectivity and disruptions affecting Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication; Confluent reverted the change and reported normal operations.

Confluent Cloud experienced major networking instability affecting multiple customers in Azure West Europe from 2026-01-08 12:30 UTC to 2026-01-08 16:25 UTC, lasting 3 h 55 min. Confluent reported implementing a fix at 13:09 UTC and subsequently confirmed resolution.

Confluent reported a major outage affecting Flink job submission and scaling in GCP asia-northeast1, europe-west8, europe-north1, and southamerica-east1, leaving jobs Pending or Stopping. Symptoms began 2025-12-02 19:53 UTC; the recorded incident started 2025-12-02 21:37 UTC and lasted 4 h 26 min. Fixes restored all affected regions; resolution was recorded at 2025-12-03 02:04 UTC.