Companies / data
Confluent
750incidents since 2018-04-24
299major or critical
18in the last 90 days
0silently edited or deleted
Recent notable changes
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Possible outage in AWS us-east-1 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. | Major incident | |
| Major incident: Experiencing high error rate in AZURE in West Europe region 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. | Major incident | |
| Major incident: Experiencing high error rate in AZURE in Germany West Central region 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. | Major incident | |
| Major incident: Missing Metrics on Confluent Cloud 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. | Major incident | |
| Major incident: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 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. | Major incident | |
| Major incident: Elevated error rates in Azure Germany West Central region 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. | Major incident | |
| Major incident: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 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. | Major incident | |
| Major incident: Multiple Confluent Cloud services are in a degraded state - All regions 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. | Major incident | |
| Major incident: Connectivity degradation - AWS us-east-1 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. | Major incident | |
| Major incident: Elevated error rates and latencies in Azure Southeast Asia region 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. | Major incident |
Full Confluent change timeline, with diffs →
Status incident history
Confluent status incidents per year
Data table
| Year | Incidents | Major/critical |
|---|---|---|
| 2018 | 27 | 8 |
| 2019 | 44 | 13 |
| 2020 | 86 | 19 |
| 2021 | 118 | 52 |
| 2022 | 133 | 60 |
| 2023 | 136 | 57 |
| 2024 | 91 | 33 |
| 2025 | 70 | 30 |
| 2026 | 45 | 27 |
Incidents per month, last 36 months
criticalmajorminornonemaintenanceunknown
Data table
| Month | Impact | Incidents |
|---|---|---|
| 2023-10 | major | 2 |
| 2023-10 | minor | 1 |
| 2023-10 | none | 2 |
| 2023-11 | critical | 1 |
| 2023-11 | major | 4 |
| 2023-11 | minor | 7 |
| 2023-11 | none | 5 |
| 2023-12 | major | 2 |
| 2023-12 | minor | 3 |
| 2024-01 | critical | 1 |
| 2024-01 | major | 5 |
| 2024-01 | minor | 4 |
| 2024-01 | none | 1 |
| 2024-02 | major | 5 |
| 2024-02 | minor | 3 |
| 2024-02 | none | 2 |
| 2024-03 | minor | 5 |
| 2024-03 | none | 1 |
| 2024-04 | major | 7 |
| 2024-04 | minor | 3 |
| 2024-04 | none | 2 |
| 2024-05 | minor | 2 |
| 2024-06 | critical | 1 |
| 2024-06 | major | 1 |
| 2024-06 | minor | 7 |
| 2024-06 | none | 1 |
| 2024-07 | major | 3 |
| 2024-07 | minor | 5 |
| 2024-07 | none | 5 |
| 2024-08 | major | 1 |
| 2024-08 | minor | 5 |
| 2024-08 | none | 1 |
| 2024-09 | major | 1 |
| 2024-09 | none | 3 |
| 2024-10 | major | 1 |
| 2024-10 | minor | 1 |
| 2024-10 | none | 3 |
| 2024-11 | critical | 2 |
| 2024-11 | major | 1 |
| 2024-11 | minor | 1 |
| 2024-12 | critical | 1 |
| 2024-12 | major | 3 |
| 2024-12 | minor | 3 |
| 2025-01 | major | 1 |
| 2025-01 | minor | 2 |
| 2025-01 | none | 2 |
| 2025-02 | critical | 1 |
| 2025-02 | major | 5 |
| 2025-02 | minor | 2 |
| 2025-03 | major | 3 |
| 2025-03 | minor | 1 |
| 2025-03 | none | 3 |
| 2025-04 | critical | 1 |
| 2025-04 | major | 1 |
| 2025-04 | minor | 1 |
| 2025-04 | none | 2 |
| 2025-05 | major | 2 |
| 2025-05 | minor | 4 |
| 2025-05 | none | 1 |
| 2025-06 | critical | 1 |
| 2025-06 | major | 3 |
| 2025-06 | minor | 1 |
| 2025-07 | major | 3 |
| 2025-07 | minor | 3 |
| 2025-07 | none | 3 |
| 2025-08 | critical | 1 |
| 2025-08 | minor | 1 |
| 2025-09 | major | 2 |
| 2025-09 | minor | 4 |
| 2025-10 | critical | 1 |
| 2025-10 | major | 3 |
| 2025-10 | minor | 4 |
| 2025-10 | none | 1 |
| 2025-11 | major | 1 |
| 2025-11 | minor | 3 |
| 2025-12 | major | 1 |
| 2025-12 | minor | 1 |
| 2025-12 | none | 1 |
| 2026-01 | major | 1 |
| 2026-02 | major | 5 |
| 2026-02 | minor | 2 |
| 2026-03 | major | 3 |
| 2026-04 | major | 2 |
| 2026-04 | none | 1 |
| 2026-05 | major | 3 |
| 2026-06 | major | 2 |
| 2026-06 | minor | 4 |
| 2026-06 | none | 1 |
| 2026-07 | minor | 2 |
| 2026-07 | none | 1 |
| 2026-08 | major | 2 |
| 2026-08 | none | 1 |
| 2026-09 | major | 6 |
| 2026-09 | minor | 3 |
| 2026-09 | none | 1 |
| 2026-10 | major | 3 |
| 2026-10 | minor | 1 |
| 2026-10 | none | 1 |
Silent edits
No silent edits or deletions detected for Confluent yet. We compare every 10-minute snapshot of each incident.
The Weekly Rewind: one short weekly email on what changed at Confluent and the other vendors we track, including silent edits. Subscribe →
Pricing, trust and legal pages
Page snapshot history
Data table
| Date | Page | Change |
|---|---|---|
| 2026-10-17 | Pricing | baseline |
| 2026-10-17 | Privacy policy | baseline |
| Page | URL | Versions | Last changed | Last fetched OK | History |
|---|---|---|---|---|---|
| Privacy policy | confluent.io/privacy | 1 | 2026-10-17 | 2026-10-17 | none yet |
| Pricing | confluent.io/pricing | 1 | 2026-10-17 | 2026-10-17 | none yet |
No changes since the first snapshot. Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
Incident timeline
Latest 100 of 750 incidents. Full list: last 90 days · JSON · Markdown