Major impactResolvedDatabases

Confluent Cloud outage: Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC

Confluent Cloud reported this major-impact incident on its official status page on Mar 5, 2026, 04:40 UTC. It was resolved after 2h 42m.

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

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Mar 5, 2026, 04:40 UTC
started
Mar 5, 2026, 07:22 UTC
resolved
2h 42m
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

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

    Confluent Cloud Metrics API are now fully functional. The incident has been resolved and systems are functioning as normal.

  2. monitoringMar 5, 2026, 04:40 UTC

    Confluent Cloud Metrics API was unavailable from 2026-03-05 03:23 UTC to 2026-03-05 03:58 UTC, the incident has been mitigated and the systems are functioning well. We are continuing to monitor and will provide an update on or before 2026-03-05 06:40 UTC.

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: Elevated error rates in AWS me-south-1 and me-central-1 regions (Mar 2, 2026)Next: Elevated error rates in AWS me-south-1 and me-central-1 regions (Apr 1, 2026) →
Confluent Cloud outage on Mar 5, 2026: Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC · APIStatus.watch