Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
Resolved
This incident has been resolved.
Jun 21, 7:14 AMResolved Jun 21, 9:21 AMMinorConfluent Cloud
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Real-time data streaming platform.
Source
auto
Category
Cloud
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 2h ago
1
Components
0
Active incidents
0
Maintenance
9.09%
90d uptime
Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2
Jun 21, 7:14 AM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 1 of 1 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Confluent Cloud Our systems for creating and using Confluent Clusters for setting data in motion. | Operational | Component | 6/21/2026 |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Confluent is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
9.09%
Known uptime
11 known history days
1
Components tracked
0 outage, 0 degraded
52
Incidents indexed
0 active right now
13
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Confluent Cloud
Operational
1
operational days
0
degraded days
9
outage days
1
maintenance days
79
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.
This incident has been resolved.
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
The incident has been resolved.
The incident has been resolved and us-east-1 (use1-az4) is fully operational.
The maintenance is complete.
This incident has been resolved.
This incident has been resolved.
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Confluent status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.confluent.cloud
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
