Confluent Outage History

Confluent is up right now

Confluent had 53 outages in the last 2 years totaling 30h 19m of downtime — averaging 2.2 incidents per month.

There were 53 Confluent outages since June 24, 2025 totaling 30h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.confluent.cloud

Major June 28, 2025

Confluent Cloud Flink - Customers may experience increased authorization failure rate for new statements

Detected by Pingoru
Jun 28, 2025, 12:43 AM UTC
Resolved
Jun 28, 2025, 06:46 PM UTC
Duration
18h 3m
Affected: Confluent Cloud
Timeline · 5 updates
  1. identified Jun 28, 2025, 12:43 AM UTC

    Starting 6/27 7:00 AM UTC, customers may be experiencing increased authorization failure rate for new statements on the Confluent Cloud Flink service. The issue has been identified and a fix is being implemented. This incident replaces an earlier one (https://status.confluent.cloud/incidents/dkpy59xgrx11) that was incorrectly closed.

  2. identified Jun 28, 2025, 12:43 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jun 28, 2025, 05:24 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jun 28, 2025, 08:41 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 28, 2025, 06:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 24, 2025

Confluent Cloud Metrics API is currently experiencing elevated error rates on certain historical queries for longer time ranges.

Detected by Pingoru
Jun 24, 2025, 09:21 PM UTC
Resolved
Jun 25, 2025, 09:37 AM UTC
Duration
12h 16m
Affected: Confluent Cloud
Timeline · 5 updates
  1. investigating Jun 24, 2025, 09:21 PM UTC

    We are currently investigating this issue.

  2. identified Jun 24, 2025, 10:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jun 25, 2025, 01:32 AM UTC

    We are continuing to roll out a fix for the issue and will provide updates.

  4. monitoring Jun 25, 2025, 08:00 AM UTC

    This incident is mitigated now. We have restarted all the nodes Since 25th June 2025, 7:35 UTC , our availability SLO is 100%

  5. resolved Jun 25, 2025, 09:37 AM UTC

    Marking at as resolved

Read the full incident report →