WarpStream 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

No SLA

Apple Push Notification service (APNs)

Apple publishes no SLA for it; its status page has no history this site can read.

Kept its SLA99.9%

Cloudflare Queues

Cloudflare promises 99.9% uptime, with a 10% credit when it misses; its status page showed no major outage in the 71 days on file.

Observed 100% over 365 days

Kept its SLA99.99%

Confluent Cloud (Kafka clusters)

Confluent promises 99.99% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.

Observed 100% over 365 days

Kept its SLA99.99%

Confluent Cloud Fully Managed Connectors

Confluent promises 99.99% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.

Observed 100% over 365 days

Kept its SLA99.99%

Confluent Cloud Schema Registry (Stream Governance)

Confluent promises 99.99% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.

Observed 100% over 365 days

Kept its SLA99.99%

Twilio APIs (Twilio-branded APIs)

Twilio promises 99.99% uptime, with a 10% credit when it misses; its status page showed no major outage in the 56 days on file.

Observed 100% over 365 days

Kept its SLA99.99%

Twilio SendGrid Mail Send API

Twilio promises 99.99% uptime, with a 10% credit when it misses; its status page showed no major outage in the 56 days on file.

Observed 100% over 365 days

ServicePromisedFirst creditObserved 365d

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
Weighted uptime: All incidents, weighted: 97.635% · Downtime

< 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 SLAs How this is measured