Skip to content

WarpStream BYOC SLA

Confluent · Messaging · promises up to 99.999% · SLA of Jul 25, 2025 · checked 23h ago

2 major outages in the last 365 days. Worst region us-east-1: 33 h counted, 99.628% observed against the 99.99% Enterprise cluster (single region), which applies per region.

1 of 12 months fell below it (credits are claimed per month). The 99.999% Enterprise cluster (multi region) tier assumes failover to another region, so a one-region outage is not held against it.

Last 90 days: no major outage.

Incidents, last 365 days

Latest 25 of 50.

Major outage time per month

Allowed per month: 4.4 min

Commitments and credits

  • Fundamentals clusterWarpStream BYOC Fundamentals99.9%below 99.9%: 10% · below 99%: 25% · below 95%: 100%
  • Pro clusterWarpStream BYOC Pro99.95%below 99.95%: 10% · below 99.9%: 15% · below 99%: 25% · below 95%: 100%
  • Enterprise cluster (single region)WarpStream BYOC Enterprise, single region99.99%below 99.99%: 10% · below 99.95%: 10% · below 99.9%: 15% · below 99%: 25% · below 95%: 100%
  • Enterprise cluster (multi region)WarpStream BYOC Enterprise, multi region99.999%below 99.999%: 10% · below 99.99%: 10% · below 99.95%: 10% · below 99.9%: 15% · below 99%: 25% · below 95%: 100%

SLA changes

  • Jul 25, 2025WarpStream 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

More in messaging

Terms, exclusions and sources
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
Status history
Status history since Sep 22, 2025
< 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.

All Confluent SLAsHow this is measured

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.