Statuspy
Databases

Is Confluent Cloud down right now?

No, it’s up.

Confluent Cloud appears to be up and running normally.

checked responded in 18msHTTP 200

Over the last 7 days, Confluent Cloud has answered our automated checks with 100.00% availability and a typical response time of ~61 ms. The most recent outage began 2026-07-17 22:01 UTC and lasted 2h 58m (severity: degraded).

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.

Response time (last 24h)
Last 24hpeak 335 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading
DateDurationSeverity
2h 58mDegraded
13h 41mDegraded
2h 51mDegraded
1h 9mDegraded
1h 54mDown
2h 4mDegraded
1h 56mDegraded
4h 12mDegraded
15hDown
1mDown
27d 15hDown
Uptime
100.00%
7 days
100.00%
30 days
100.00%
90 days
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
Is Confluent Cloud down right now?
Confluent Cloud appears to be up and running normally. Last checked 2026-08-05 04:42 UTC (4 minutes ago).
When was Confluent Cloud's last outage?
The most recent outage began 2026-07-17 22:01 UTC and lasted 2h 58m (severity: degraded).
What should I do if Confluent Cloud is down for me?
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.
Confluent Cloud’s official status page

Related services

ClickHouse CloudCockroachDB CloudFirebaseMongoDB AtlasNeonPinecone