Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
Apr 24, 17:18 UTCApr 25, 00:14 UTC
Duration
6h 56m
Impact
Informational
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved.
Timeline
- Resolved · Apr 25, 00:14 UTC
This incident has been resolved.
- Monitoring · Apr 24, 23:06 UTC
A fix has been implemented and we are monitoring for next hour.
- Identified · Apr 24, 22:27 UTC
Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.
- Identified · Apr 24, 20:14 UTC
The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.
- Investigating · Apr 24, 17:18 UTC
We are currently investigating this issue.
More from Confluent
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2311:47 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 11h 30m |
| Sep 2215:09 UTC | Elevated error rates in Azure Germany West Central region | major | 4h 50m |
| Sep 2116:15 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 9h 16m |
| Sep 1717:49 UTC | Confluent Cloud Metrics API experienced elevated latency and error rates | none | 0m |
| Sep 1523:59 UTC | Multiple Confluent Cloud services are in a degraded state - All regions | major | 1h 22m |
| Sep 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.