Confluent.
Last Resolved Incident
2 days ago · lasted 7h 2m · None
7d Uptime
88.109%
30d Uptime
43.559%
90d Uptime
75.263%
180d Uptime
87.631%
1y Uptime
93.900%
Daily Uptime · 180 days
147/180 clean days
Recent Incidents
3
Community Reports (7d)
0
Official status page: https://status.confluent.cloud (opens in new tab)
Recent Incidents
Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
NoneExperiencing delays in Tableflow external catalog syncs in AWS
MajorElevated error rates in AWS me-south-1 and me-central-1 regions
MajorFrequently Asked Questions
Is Confluent currently down?
Confluent is currently Operational. CheckUpstream tracks Confluent in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
When did Confluent last have an outage?
Confluent's last resolved incident started 2 days ago and lasted 7h 2m (an incident).
What's Confluent's 30-day uptime?
Confluent's 30-day customer-perceived uptime is 87.631%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
How do I monitor Confluent in production?
Sign up to CheckUpstream and add Confluent to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
How does CheckUpstream track Confluent?
We poll Confluent's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.
Looking for the live "is Confluent down" view? Check the Confluent Status page.