Skip to content

Confluent Cloud (Kafka clusters) SLAConfluent · Messaging · Confluent · Messaging

MessagingSLA of Jul 25, 2025Checked 15h ago

Promise vs reality

Downtime used against the allowance

33 h of major incidents, 37.2x the allowance53 min 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: 4.4 min

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

Commitments and credits

  • Basic clusterBasic clusters99.5%

    Monthly uptime below, credit of the bill

    1. Below 99.5%10%
    2. Below 99%25%
    3. Below 95%100%
  • Standard (1 eCKU) or Enterprise (1 eCKU) clusterSingle-eCKU Standard or Enterprise clusters99.9%

    Monthly uptime below, credit of the bill

    1. Below 99.9%10%
    2. Below 99%25%
    3. Below 95%100%
  • Dedicated single-zone clusterDedicated (Single Zone) clusters, header notes '(Including Jio region)'99.95%

    Monthly uptime below, credit of the bill

    1. Below 99.95%10%
    2. Below 99%25%
    3. Below 95%100%
  • Multi-zone (Standard 2 eCKU, Enterprise 2 eCKU, Dedicated multi-zone)Standard (2 eCKU), Enterprise (2 eCKU), or Dedicated (Multi-zone) clusters99.99%

    Monthly uptime below, credit of the bill

    1. Below 99.99%10%
    2. Below 99%25%
    3. Below 95%100%

Terms

Measured
Monthly Uptime Percentage per cluster; a minute is down if all continuous write attempts by Confluent's monitoring system fail
Credit cap
100% of the monthly fees for the affected Cloud Service function (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.99% ≥ 99% - - - 10% [Standard (2 ECKU), Enterprise (2 ECKU), or Dedicated (Multi-zone) Cluster column]
Confluent, July 25, 2025 (Confluent Cloud Unified SLA). Read the SLA

Table columns were mapped by position in the PDF layout. The '(Including Jio region)' label sits under the Dedicated (Single Zone) header in the layout. Credits are a % of monthly fees for the affected cluster and expire 12 months after issue.

Evidence: incidents, last 365 days

Other messaging 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.