Confluent Cloud incident: Confluent Cloud Connector event logs - Unavailable - All clusters - All regions

Affected components

• Confluent Cloud

1. resolvedNov 17, 2025, 21:07 UTC

   This issue has been resolved, and there should be no further log loss. All subsequent connector log events are now accessible.

2. monitoringNov 17, 2025, 19:53 UTC

   A fix has been implemented, ensuring no further log loss. All subsequent connector log events are now available, and we will continue monitoring the results.

3. identifiedNov 17, 2025, 15:29 UTC

   We have identified the cause of the issue and have begun mitigation steps. Our investigation confirmed that some connector log events were lost as a result of this issue. The mitigation currently in progress will prevent further log loss, but we will be unable to recover the events that were previously lost. The full mitigation is expected to take up to 8 hours to complete for all clusters. We will provide a further update within the next 2 hours.

4. investigatingNov 17, 2025, 14:38 UTC

   We are continuing to investigate this issue.

5. investigatingNov 17, 2025, 14:28 UTC

   We are experiencing issues with the availability of recent Connector event logs across all regions and cluster types. The problem started at 09:00 UTC on November 17, 2025. 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.

• 1Password: Item Usage Metrics Not Updating in Real TimeMinor · Nov 13, 2025, 23:55 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