Confluent incident

Elevated Error Rates in AWS me-central-1 region

Major Resolved View vendor source →
Started
Mar 01, 2026, 06:08 PM UTC
Resolved
Mar 01, 2026, 10:05 PM UTC
Duration
3h 57m
Detected by Pingoru
Mar 01, 2026, 06:08 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Mar 01, 2026, 06:08 PM UTC

    We are experiencing increased error rates in some of our Confluent Cloud services in the AWS me-central-1 region. This began at approximately 12:51 PM UTC today and is linked to a disruption in one of AWS’s availability zones (mec1-az2). Our team is actively applying mitigation steps and will provide updates as the situation evolves.

  2. identified Mar 01, 2026, 06:48 PM UTC

    We have identified the cause of the problem to be disruption in one of AWS’s availability zones (mec1-az2). We are taking steps to confirm the safest path to mitigation for any impacted Confluent Cloud services in this region.

  3. monitoring Mar 01, 2026, 09:41 PM UTC

    The problem has been mitigated as of 21:15 PM UTC today. All Confluent Cloud services are now healthy in me-central-1 region and we will monitor for any residual issues before resolving this incident in 1 hour.

  4. resolved Mar 01, 2026, 10:05 PM UTC

    This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 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
Start monitoring Confluent for free

5 free monitors · No credit card required