Live / Confluent Cloud / Incident
Confluent Cloud: Experiencing high error rate in AZURE in West Europe region
Confluent Cloud · confluent.cloudMajor incidentResolved2026-10-10 09:36 UTC
Public — what happened
Summary
Confluent Cloud said customers using its service on Azure in the West Europe region could see higher error rates and slower performance, beginning at 13:34 UTC on 2026-10-09. By 16:46 UTC the company reported that Azure had found the problem and was working on recovery, though a small number of clusters stayed affected through the night and Azure gave no estimated time for a fix. Confluent reported recovery spreading across affected clusters by 04:15 UTC on 2026-10-10, said a fix was in place at 08:47 UTC, and marked the incident resolved at 09:36.
Affected
Confluent Cloud
Timeline
- Started — 2026-10-09 13:34 UTC
- Investigating — 2026-10-09 13:34 UTC
- Identified — 2026-10-09 16:46 UTC (9 updates)
- Monitoring — 2026-10-10 08:47 UTC
- Resolved — 2026-10-10 09:36 UTC · 20h 02m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Confluent Cloud report →
More from Confluent Cloud
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.