Statuspy
Databases

Is Confluent Cloud down right now?

No, it’s up.

Confluent Cloud appears to be up and running normally.

checked responded in 21msHTTP 200

Over the last 7 days, Confluent Cloud has answered our automated checks with 100.00% availability and a typical response time of ~33 ms. According to Confluent Cloud's official status page, the most recent outage began 2026-08-25 04:17 UTC and lasted 3h 11m (severity: down). It was reported as "Elevated error rates and latencies in Azure Southeast Asia region".

Confluent Cloud is fully managed Apache Kafka, carrying event streams between services for many large platforms. Kafka's buffering usually absorbs short disruptions, so the symptom is consumer lag growing rather than immediate failure, and the damage becomes visible only once downstream systems fall behind.

Is Confluent Cloud down for everyone or just you?

Our automated checks are reaching Confluent Cloud normally right now, and it answered our last one in 21ms. That makes any trouble you are hitting more likely to be local to your connection, account or network than a full outage, which usually means you can fix it from your end.

Still not working for you?Try the fixes

Confluent Cloud response time (last 24h)

Last 24hpeak 159 ms

Confluent Cloud incident history (last 90 days)

SepOctNov
  • up
  • slow
  • down
  • no reading
All 42 recorded outages
DateWhat happenedDurationSeverity
Elevated error rates and latencies in Azure Southeast Asia regionReported by Confluent Cloud3h 11mDown
Elevated error rates and latency in GCP us-west1Reported by Confluent Cloud3h 7mDown

Confluent Cloud uptime

100.00%
7 days
100.00%
30 days
99.98%
90 days

Measured since 2026-08-12. Windows reaching further back are averaged over the 86 days we watched, not the full period. Counts our own checks. Days Confluent Cloud reported an incident are coloured in the timeline above but do not change this figure.

What to do if Confluent Cloud is down for just you

  • Check your connection limit and pool settings first, since exhausting connections looks exactly like the database being down.
  • Retry with a longer timeout, because a serverless or scale-to-zero instance may simply be waking up.
  • Confirm your credentials and IP allowlist have not changed, as an auth or firewall denial reads as a failed query.
  • Query from another network or client to establish whether the cluster or your route to it is the problem.

Frequently asked questions

Confluent Cloud appears to be up and running normally. Last checked 2026-11-05 13:28 UTC.

Confluent Cloud’s official status page

Related services