# Confluent change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [Confluent](https://rewindex.com/company/confluent.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 28 | 28 | 2026-10-09 23:27 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-10-09 23:27 UTC | Major incident | [Major incident: Possible outage in AWS us-east-1](https://rewindex.com/change/i8663db79ee6b46.md) | outage | 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. | | 2026-10-09 23:03 UTC | Major incident | [Major incident: Experiencing high error rate in AZURE in West Europe region](https://rewindex.com/change/i487d8101457c8f.md) | outage | 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. | | 2026-10-08 11:00 UTC | Major incident | [Major incident: Experiencing high error rate in AZURE in Germany West Central region](https://rewindex.com/change/i7f38d13a0eac9e.md) | outage | 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. | | 2026-09-27 17:17 UTC | Major incident | [Major incident: Missing Metrics on Confluent Cloud](https://rewindex.com/change/i96f415fea72361.md) | degradation | 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. | | 2026-09-23 11:47 UTC | Major incident | [Major incident: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2](https://rewindex.com/change/i60fb3ac363f6dc.md) | outage | 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. | | 2026-09-22 15:09 UTC | Major incident | [Major incident: Elevated error rates in Azure Germany West Central region](https://rewindex.com/change/i9f769e9c3d960d.md) | outage | 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. | | 2026-09-21 16:15 UTC | Major incident | [Major incident: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2](https://rewindex.com/change/i545b9b252157ae.md) | outage | 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. | | 2026-09-15 23:59 UTC | Major incident | [Major incident: Multiple Confluent Cloud services are in a degraded state - All regions](https://rewindex.com/change/ia5b515d339b7c8.md) | degradation | 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. | | 2026-09-08 20:01 UTC | Major incident | [Major incident: Connectivity degradation - AWS us-east-1](https://rewindex.com/change/iac1283df13beed.md) | degradation | 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. | | 2026-08-25 04:17 UTC | Major incident | [Major incident: Elevated error rates and latencies in Azure Southeast Asia region](https://rewindex.com/change/i7ef856d821b1a0.md) | degradation | 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. | | 2026-08-20 17:10 UTC | Major incident | [Major incident: Elevated error rates and latency in GCP us-west1](https://rewindex.com/change/ia3dd26b5c5cd9a.md) | degradation | 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. | | 2026-06-25 15:59 UTC | Major incident | [Major incident: Increased error rates in Metrics API](https://rewindex.com/change/ibbd1961113d11e.md) | outage | 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. | | 2026-06-12 07:42 UTC | Major incident | [Major incident: Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2](https://rewindex.com/change/i3443fb9090d628.md) | degradation | 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. | | 2026-05-29 06:47 UTC | Major incident | [Major incident: Elevated error rates and latencies in Azure westus2 region](https://rewindex.com/change/i706d4484b03a28.md) | outage | 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. | | 2026-05-22 00:21 UTC | Major incident | [Major incident: Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2](https://rewindex.com/change/i186efdad8aa186.md) | outage | 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. | | 2026-05-08 01:14 UTC | Major incident | [Major incident: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4](https://rewindex.com/change/i4534fd33a396f4.md) | degradation | 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. | | 2026-04-21 09:34 UTC | Major incident | [Major incident: Experiencing delays in Tableflow external catalog syncs in AWS](https://rewindex.com/change/i8ab677441db957.md) | degradation | 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. | | 2026-04-01 19:52 UTC | Major incident | [Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions](https://rewindex.com/change/i79889a7b1550f7.md) | outage | 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. | | 2026-03-05 04:40 UTC | Major incident | [Major incident: Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC](https://rewindex.com/change/ia4785cabc0ef8e.md) | outage | 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. | | 2026-03-02 07:19 UTC | Major incident | [Major incident: Elevated error rates in AWS me-south-1 and me-central-1 regions](https://rewindex.com/change/i216a555df77571.md) | outage | 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. | | 2026-03-01 18:08 UTC | Major incident | [Major incident: Elevated Error Rates in AWS me-central-1 region](https://rewindex.com/change/i62ec2271ac6380.md) | outage | 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. | | 2026-02-26 19:56 UTC | Major incident | [Major incident: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing](https://rewindex.com/change/i0b8cb2c119f5cf.md) | outage | 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. | | 2026-02-26 13:59 UTC | Major incident | [Major incident: Network provisioning service in Azure East US region is degraded](https://rewindex.com/change/i19ea1d41b33700.md) | degradation | 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. | | 2026-02-25 05:01 UTC | Major incident | [Major incident: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates](https://rewindex.com/change/i942ea44e6d3ab6.md) | outage | 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. | | 2026-02-11 22:14 UTC | Major incident | [Major incident: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failing](https://rewindex.com/change/i078b274d488429.md) | outage | 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. | | 2026-02-03 21:33 UTC | Major incident | [Major incident: Confluent Cloud Service Outage](https://rewindex.com/change/i9f1d140e410577.md) | outage | 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. | | 2026-01-08 12:30 UTC | Major incident | [Major incident: Multiple customers are reporting networking instability in the Azure West Europe region](https://rewindex.com/change/ib7a1140e509ace.md) | degradation | 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. | | 2025-12-02 21:37 UTC | Major incident | [Major incident: Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1](https://rewindex.com/change/i26d6183316ccab.md) | outage | 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. | --- Canonical: https://rewindex.com/company/confluent/changes · Markdown: https://rewindex.com/company/confluent/changes.md · JSON: https://rewindex.com/api/v1/companies/confluent/changes · Generated 2026-10-18T02:25:12.982Z