Minor impactResolvedDatabases

Confluent Cloud incident: Intermittent Produce/Consume Unavailability in Azure Dedicated clusters

Confluent Cloud reported this minor-impact incident on its official status page on Jun 16, 2026, 16:02 UTC. It was resolved after 1h 57m.

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

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Jun 16, 2026, 16:02 UTC
started
Jun 16, 2026, 17:58 UTC
resolved
1h 57m
duration
Minor
impact

Affected components

  • Confluent Cloud
  1. resolvedJun 16, 2026, 17:58 UTC

    No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

  2. monitoringJun 16, 2026, 17:58 UTC

    No further issues have been observed. The incident is now resolved as of 2026-06-16 17:58 UTC.

  3. monitoringJun 16, 2026, 16:43 UTC

    We have found the root cause and have mitigated the problem as of 2026-06-16 16:09 UTC. We will monitor for any residual issues before resolving this incident in 1 hour.

  4. investigatingJun 16, 2026, 16:02 UTC

    We are currently experiencing Intermittent Produce/Consume Unavailability in Azure Dedicated clusters. The problem started at 2026-06-16 13:20 UTC. We are currently investigating and will update as we know more.

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

Confluent Cloud incident on Jun 16, 2026: Intermittent Produce/Consume Unavailability in Azure Dedicated clusters · APIStatus.watch