Skip to content

Confluent Cloud ksqlDB SLAConfluent · Compute · Confluent · Compute

ComputeSLA of Jul 25, 2025Checked 18h ago

Promise vs reality

Downtime used against the allowance

33 h of major incidents, 3.7x the allowance8.8 h allowed in 365 days

2 major and 46 minor incidents; worst region us-east-1. 15 d degraded (not counted).

Major incident minutes per month

Allowed per month: 44 min

All incidents, weighted: 97.169% · Downtime
Promised
99.9%
Observed, 365d
99.628%
Major incident time
33 h
Credit on first breach
5%

Commitments and credits

  • Multi-zone ksqlDB with 8+ CSUsMulti-zone ksqlDB deployments using eight (8) or more Confluent Streaming Units99.9%

    Monthly uptime below, credit of the bill

    1. Below 99.9%5%
    2. Below 99.5%10%
    3. Below 99%25%

Terms

Measured
Five-minute periods per ksqlDB Instance; down if all Metadata Requests (LIST STREAMS/TABLES/QUERIES) fail
Credit cap
25% of monthly fees (lowest band)
Claim window
Within five (5) calendar days after the last day of the month in which the Service Level was missed
How to claim
Log a support ticket (community-supported customers email cloud-support@confluent.io) with 'SLA Credit Request' in the subject, client versions/configs and request logs of failed writes

Not covered

  • Suspension for late payment, misuse or violation of the Agreement/AUP
  • Factors outside Confluent's reasonable control incl. force majeure, DoS attacks, internet issues
  • Third-party services incl. failures of the underlying cloud platform
  • Use of unsupported Kafka clients or unacceptable client configuration
  • Scheduled maintenance with five (5) days email notice, or ad hoc maintenance
  • Deployment on any Jio region, except as noted
< 99.9% ≥ 99.5% 5%; < 99.5% ≥ 99.0% 10%; < 99.0% 25%
Confluent, July 25, 2025 (Confluent Cloud Unified SLA). Read the SLA

Instances under 8 CSUs, and single-zone instances, fall outside the ksqlDB Instance definition.

Evidence: incidents, last 365 days

Other compute SLAs

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

Weekly: SLA changes from cloud, data and AI vendors, Fridays.