Statuspy
Databases

Is Confluent Cloud down right now?

No, it’s up.

Confluent Cloud appears to be up and running normally.

checked responded in 43msHTTP 200

Over the last 7 days, Confluent Cloud has answered our automated checks with 100.00% availability and a typical response time of ~45 ms. According to Confluent Cloud's official status page, the most recent outage began 2026-07-17 22:01 UTC and lasted 2h 58m (severity: degraded). It was reported as "Flink statements degraded in GCP us-central1 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.

Response time (last 24h)
Last 24hpeak 422 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading

11 of the incidents below were reported by Confluent Cloud on days we were not yet monitoring, so the timeline above leaves those days hatched rather than colouring them in.

DateWhat happenedDurationSeverity
Flink statements degraded in GCP us-central1 regionReported by Confluent Cloud2h 58mDegraded
Kafka cluster performance degradation for clusters in AWS region eu-central-1Reported by Confluent Cloud13h 41mDegraded
Kafka consumer and producer degradation in Azure spaincentralReported by Confluent Cloud2h 51mDegraded
Confluent Cloud Metrics API is currently experiencing elevated error ratesReported by Confluent Cloud1h 9mDegraded
Increased error rates in Metrics APIReported by Confluent Cloud1h 54mDown
Kafka cluster performance degradation for Basic and Standard clusters in AWS US-East-2Reported by Confluent Cloud2h 4mDegraded
Intermittent Produce/Consume Unavailability in Azure Dedicated clustersReported by Confluent Cloud1h 56mDegraded
Confluent Cloud — Degraded inter-region connectivity — AWS us-west-2Reported by Confluent Cloud4h 12mDegraded
Elevated error rates and latencies in Azure westus2 regionReported by Confluent Cloud15hDown
Connection failures in a set of PNI Gateways for Kafka Clusters in AWS us-east-1 and us-west-2Reported by Confluent Cloud1mDown
Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Reported by Confluent Cloud27d 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 06:54 UTC (3 minutes ago).
When was Confluent Cloud's last outage?
According to Confluent Cloud's official status page, the most recent outage began 2026-07-17 22:01 UTC and lasted 2h 58m (severity: degraded). It was reported as "Flink statements degraded in GCP us-central1 region".
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