Cloudflare SLA Credit Requirements and Claim Deadlines
| Applicable service | Cloudflare Business Plan Services |
|---|---|
| Official SLA source | https://www.cloudflare.com/business-sla/ |
| Availability target | 100% |
| Measurement period | monthly billing period |
| Credit tiers / formula | Service Credit (as a fraction of monthly recurring Service fees) = (Outage Period minutes x Affected Customer Ratio) / Scheduled Availability minutes. Section 6.1 of the fetched SLA. This is a formula, NOT a tier table; an estimate requires customer-supplied outage minutes, affected-customer ratio, and scheduled availability minutes. |
| Claim window (verified text) | Customer must notify Customer Support of the Incident within five business days following the Incident, and must submit the Claim by the end of the billing month following the billing month in which the Incident occurs (Sections 3.2 and 3.4). |
| Evidence requirements | Detailed description of the Incident(s); Incident duration; Network traceroutes; Affected URL(s); Attempts made to resolve the Incident |
| Official submission procedure | Notify Customer Support of the Incident within five business days. To submit a Claim, contact Customer Support with detailed descriptions of the Incident(s), duration, network traceroutes, affected URL(s), and resolution attempts (Section 3.3). |
| Important exclusions | Does not apply to issues due to factors outside Cloudflare's reasonable control, customer/third-party hardware or software, customer actions, use after advice to modify, beta/trial services, or acts of the customer's users/agents (Section 4). Total Service Credits in any 12-month period cannot exceed one month of cumulative monthly service fees (Section 5.3). |
| Monitoring limitations | CreditClaim monitors the vendor's official public status feed (https://www.cloudflarestatus.com/api/v2/incidents.json). A public incident is not, by itself, proof that your service breached its SLA; eligibility requires your measured uptime and the evidence above. |
| Last verification date | 2026-10-27 |
| Source content hash (SHA-256) | d2dc83058303d0c859ab134ba96308523bf1a19fc93e1583866b2b61c25f2657 |
| Verification status | VERIFIED |
100% uptime commitment (Section 1.1). Because the credit is formula-based, CreditClaim returns INSUFFICIENT_EVIDENCE for this vendor unless the customer supplies the formula inputs.