Skip to content

Confluent Cloud Fully Managed Connectors 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

  • Connector to a multi-zone Dedicated, Enterprise or Standard clusterSupported fully managed connectors attached to multi-zone clusters99.99%

    Monthly uptime below, credit of the bill

    1. Below 99.99%10%
    2. Below 99%25%
  • Connector to a single-zone Dedicated or Standard clusterSupported fully managed connectors attached to single-zone clusters99.95%

    Monthly uptime below, credit of the bill

    1. Below 99.95%10%
    2. Below 99%25%
  • Connector to a Basic clusterSupported fully managed connectors attached to Basic clusters99.5%

    Monthly uptime below, credit of the bill

    1. Below 99.5%10%
    2. Below 99%25%

Terms

Measured
Consecutive five-minute periods per connector instance; down when all Tasks are in a Failed State due to Confluent
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.99% ≥ 99.95% ... < 99% 25% [10% cell spans the rows from < 99.99% down to ≥ 99%]
Confluent, July 25, 2025 (Confluent Cloud Unified SLA). Read the SLA

This table uses merged cells. The committed levels were read from word coordinates in the PDF: the multi-zone '10%' is vertically centred across the 99.99-99% rows, and the single-zone '10%' across the 99.95-99% rows. Custom, preview and 'Connect with Confluent' connectors are excluded. Max credit 25%.

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.