Confluent Cloud incident: Missing metrics in some Confluent Cloud Kafka clusters

Affected components

• Confluent Cloud

1. resolvedDec 10, 2025, 04:48 UTC

   This issue has been resolved.

2. monitoringDec 9, 2025, 14:51 UTC

   Normal metrics operations have been restored for all originally affected clusters. We are actively monitoring for any new occurrences of the issue.

3. identifiedDec 9, 2025, 01:13 UTC

   The mitigation is nearing completion and we have seen recovery on most clusters. The root cause has been identified.

4. investigatingDec 8, 2025, 20:44 UTC

   We are mitigating the impacted clusters and continuing to investigate the root cause.

5. investigatingDec 8, 2025, 17:48 UTC

   We are investigating an issue with missing metrics affecting a small number of Confluent Cloud Kafka clusters.

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.

• Sanity: Vercel - Unable to create new Sanity integrationsMajor · Dec 8, 2025, 09:50 UTC
• Mapbox: Delayed delivery of Mapbox Traffic DataMinor · Dec 6, 2025, 00:46 UTC
• Sanity: Elevated API and API CDN error rate for a small subset of customersMinor · Dec 9, 2025, 08:50 UTC
• Pinecone: Increased file processing time for AssistantMinor · Dec 9, 2025, 20:15 UTC
• Datadog: Metrics data ingestion delayed and monitor evaluations degradedMinor · Dec 9, 2025, 20:16 UTC

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