Minor impactResolvedDatabases

Confluent Cloud incident: BYOK-enabled Tableflow deployments may experience data inconsistencies when executing queries that include filter predicates

Confluent Cloud reported this minor-impact incident on its official status page on Nov 28, 2025, 13:25 UTC. It was resolved after 5h 8m.

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

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Nov 28, 2025, 13:25 UTC
started
Nov 28, 2025, 18:33 UTC
resolved
5h 8m
duration
Minor
impact

Affected components

  • Confluent Cloud
  1. resolvedNov 28, 2025, 18:33 UTC

    This incident has been resolved.

  2. identifiedNov 28, 2025, 18:02 UTC

    We have fixed the issue, and are now monitoring the few affected tables to ensure they all return to full operation. As of Nov 28th 6:00PM UTC customers should see normal operations with Confluent systems.

  3. identifiedNov 28, 2025, 13:25 UTC

    We've identified the issue; a hotfix is on its way to production.

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 Nov 28, 2025: BYOK-enabled Tableflow deployments may experience data inconsistencies when executing queries that include filter predicates · APIStatus.watch