Major impactResolvedDatabases

Confluent Cloud outage: Experiencing delays in Tableflow external catalog syncs in AWS

Confluent Cloud reported this major-impact incident on its official status page on Apr 21, 2026, 09:34 UTC. It was resolved after 15 min.

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

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Apr 21, 2026, 09:34 UTC
started
Apr 21, 2026, 09:49 UTC
resolved
15 min
duration
Major
impact

Affected components

  • Confluent Cloud

Timeline

updates from Confluent Cloud's status page ↗
  1. resolvedApr 21, 2026, 09:49 UTC

    This incident has been resolved.

  2. monitoringApr 21, 2026, 09:34 UTC

    We are experiencing delays Tableflow external catalog sync in AWS. Our team has added a fix to resolve the situation and are monitoring the same.

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

← Previous: Elevated error rates in AWS me-south-1 and me-central-1 regions (Apr 1, 2026)Next: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4 (May 8, 2026) →
Confluent Cloud outage on Apr 21, 2026: Experiencing delays in Tableflow external catalog syncs in AWS · APIStatus.watch