Confluent incident
Elevated error rates in AWS me-south-1 and me-central-1 regions
Affected components
Update timeline
- monitoring Mar 20, 2026, 01:58 PM UTC
AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
- monitoring Apr 01, 2026, 07:52 PM UTC
Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
- monitoring Apr 02, 2026, 03:40 PM UTC
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.
Looking to track Confluent downtime and outages?
Pingoru polls Confluent's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Confluent reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Confluent alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required