Confluent Cloud SLA
99.5%–99.99% uptime guarantee (All Confluent Cloud customers under Cloud Services Agreement plan only)
Official SLA Commitment
Applies to
All Confluent Cloud customers under Cloud Services Agreement plan only
Scope
Confluent Cloud Service functions — primarily Kafka clusters, plus Flink, Connectors, ksqlDB, Schema Registry, and Warpstream BYOC each with separate terms
Measurement
Kafka: Monthly Uptime Percentage = (total minutes − Downtime minutes) ÷ total minutes. Downtime = minutes where all continuous monitoring write attempts to the cluster fail. Partial minutes not counted.
Exclusions
Late payment suspension; customer misuse/AUP violations; force majeure; third-party/cloud-platform failures; unauthorized customer actions; unsupported Kafka client configs; customer environment failures; failure to follow remedial recommendations; scheduled maintenance (5-day email notice); Jio region deployments (except as noted)
Not covered
Community-supported accounts without paid support may email cloud-support@confluent.io for credits; preview/custom connectors; Connect with Confluent connectors; customer-uploaded connectors
Promised vs Measured
SLA Promise
99.5%–99.99%
≤ 3h 36m downtime/month
Measured (30d)
—
Collecting data…
Verdict
—
24h Uptime
—
7d Uptime
—
30d Uptime
—
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Basic cluster | 99.5% | ~$0/mo (pay-as-you-go, first eCKU free then $0.14/eCKU-hr) | |
| Standard cluster (1 eCKU) | 99.9% | ~$385/mo estimated | |
| Standard cluster (2+ eCKUs) | 99.99% | ~$385/mo+ (2 eCKU minimum for four-nines) | |
| Enterprise cluster (1 eCKU) | 99.9% | ~$895/mo estimated | |
| Enterprise cluster (2+ eCKUs) | 99.99% | ~$895/mo+ | |
| Dedicated cluster (single-zone) | 99.95% | From $2.25/CKU-hr (min 2 CKUs) | |
| Dedicated cluster (multi-zone) | 99.99% | From $2.25/CKU-hr (min 2 CKUs, multi-AZ) | |
| Freight cluster | 99.99% | Consumption-based (relaxed latency tier) |
Source: confluent cloud.com/pricing
SLA Credit Policy
Service credits as percentage of monthly fees for the unavailable Cloud Service function. Credits applied to next billing cycle within one billing cycle of confirmed claim. Credits expire 12 months from issuance. Exclusive remedy.
| Monthly Uptime | Credit |
|---|---|
| Kafka < 99.99% ≥ 99% (2+ eCKU / multi-zone) | 10% of monthly fee |
| Kafka < 99.9% ≥ 99% (1 eCKU Standard/Enterprise) | 10% of monthly fee |
| Kafka < 99.5% ≥ 99% (Basic) | 10% of monthly fee |
| Kafka < 99% ≥ 95% (all cluster types) | 25% of monthly fee |
| Kafka < 95% (all cluster types) | 100% of monthly fee |
Credits capped at 100% of monthly fee. Must be claimed within 5 days. Applied within 30 days of approval.
Industry SLA Tier Compliance
| Tier | Downtime Budget/Month | 24h | 7d | 30d |
|---|---|---|---|---|
| 99.9%(three nines) | 43m 12s | |||
| 99.95% | 21m 36s | |||
| 99.99%(four nines) | 4m 19s | |||
| 99.999%(five nines) | 26s |
Equivalent Downtime
Last 24 hours
—
Last 7 days
—
Last 30 days
—
Incident Summary (90 days)
Total Incidents
18
Active Now
0
Resolved
18
Avg. Resolution
8h 24m
Confluent Cloud SLA: What You Need to Know
Confluent Cloud guarantees 99.5%–99.99% uptime measured as confluent cloud service functions — primarily kafka clusters, plus flink, connectors, ksqldb, schema registry, and warpstream byoc each with separate terms. This commitment applies exclusively to All Confluent Cloud customers under Cloud Services Agreement plan customers.
Based on DevHelm's continuous monitoring, Confluent Cloud currently shows a 30-day measured uptime of —. Uptime data is still being collected for a complete assessment.
What's Covered (and What Isn't)
Confluent Cloud's SLA specifically covers confluent cloud service functions — primarily kafka clusters, plus flink, connectors, ksqldb, schema registry, and warpstream byoc each with separate terms. It explicitly excludes: Community-supported accounts without paid support may email cloud-support@confluent.io for credits; preview/custom connectors; Connect with Confluent connectors; customer-uploaded connectors. This means outages in excluded components don't count toward SLA credits.
Impact on Your Application
Once sufficient monitoring data is collected, this section will show projected annual downtime. If your application depends on additional services, their independent failure probabilities compound — making dependency monitoring essential for maintaining your own SLA commitments.
Monitoring Methodology
DevHelm tracks Confluent Cloud's official status page continuously and aggregates component-level status data into uptime percentages. Data is refreshed every 5 minutes. Uptime is calculated as the percentage of time all components report operational status.
