Major impactResolvedDatabases

Confluent Cloud outage: Elevated Error Rates in AWS me-central-1 region

Confluent Cloud reported this major-impact incident on its official status page on Mar 1, 2026, 18:08 UTC. It was resolved after 3h 57m.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Mar 1, 2026, 18:08 UTC
started
Mar 1, 2026, 22:05 UTC
resolved
3h 57m
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

updates from Confluent Cloud's status page ↗
  1. resolvedMar 1, 2026, 22:05 UTC

    This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.

  2. monitoringMar 1, 2026, 21:41 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.

  3. identifiedMar 1, 2026, 18:48 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.

  4. investigatingMar 1, 2026, 18:08 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history

← Previous: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing (Feb 26, 2026)Next: Elevated error rates in AWS me-south-1 and me-central-1 regions (Mar 2, 2026) →
Confluent Cloud outage on Mar 1, 2026: Elevated Error Rates in AWS me-central-1 region · APIStatus.watch