Skip to content

WarpStream BYOC SLAConfluent · Messaging · Confluent · Messaging

MessagingSLA of Jul 25, 2025Checked 15h ago

Promise vs reality

Downtime used against the allowance

33 h of major incidents, 372.1x the allowance5.3 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: 26 s

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

Commitments and credits

  • Fundamentals clusterWarpStream BYOC Fundamentals99.9%

    Monthly uptime below, credit of the bill

    1. Below 99.9%10%
    2. Below 99%25%
    3. Below 95%100%
  • Pro clusterWarpStream BYOC Pro99.95%

    Monthly uptime below, credit of the bill

    1. Below 99.95%10%
    2. Below 99.9%15%
    3. Below 99%25%
    4. Below 95%100%
  • Enterprise cluster (single region)WarpStream BYOC Enterprise, single region99.99%

    Monthly uptime below, credit of the bill

    1. Below 99.99%10%
    2. Below 99.95%10%
    3. Below 99.9%15%
    4. Below 99%25%
    5. Below 95%100%
  • Enterprise cluster (multi region)WarpStream BYOC Enterprise, multi region99.999%

    Monthly uptime below, credit of the bill

    1. Below 99.999%10%
    2. Below 99.99%10%
    3. Below 99.95%10%
    4. Below 99.9%15%
    5. Below 99%25%
    6. Below 95%100%

Terms

Measured
Minutes per Platform cluster; down when all monitoring probes fail within a minute (Materially Degraded)
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.999% ≥ 99.99% - - - 10%
Confluent, July 25, 2025 (Confluent Cloud Unified SLA). Read the SLA

Multi-region Enterprise tier (99.999%) is new in the July 25, 2025 version.

Evidence: incidents, last 365 days

SLA changes

  • Jul25WarpStream BYOCWarpStream BYOC schedule changed between the March 19, 2025 and July 25, 2025 SLA PDFs: March had 3 columns (Fundamentals/Pro/Enterprise, top band '< 99.99% ≥ 99.95%' for Enterprise, bands like '< 99.94% ≥ 99.90%'); July adds 'Enterprise Cluster (Multi Region)' at 99.999% ('< 99.999% ≥ 99.99% ... 10%') and re-cuts bands to '< 99.95% ≥ 99.90%'. The Kafka, Flink, Connector, ksqlDB and Schema Registry tables are identical in both.Source

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.