Cloudflare provides service level agreements for its Business and Enterprise plans, including a 100% uptime commitment. For buyers, the practical question is not whether the phrase sounds strong, but what service is actually covered, what exclusions apply, and how service credits are claimed if Cloudflare misses the target.
What it is and who it’s for
A service level agreement, or SLA, is a contractual commitment that defines a service target and the remedy if that target is missed. In Cloudflare’s case, the Business SLA applies only to Business Level customers, and the company’s plans FAQ says Cloudflare provides SLAs for both Business and Enterprise plans.
Cloudflare says Business customers get a 100% uptime commitment for Customer Content. For Enterprise customers, Cloudflare says the SLA includes a 100% uptime commitment globally.
That scope distinction matters for procurement and operations teams. A buyer evaluating the Cloudflare SLA should first separate Business from Enterprise, because the Business SLA is a standalone policy for Business customers, while Enterprise customers are directed to Enterprise terms that also include support commitments, service-specific overrides for R2, Queues, and Workers, and different success offerings.
How it works
On both plans, service credits are the customer’s sole and exclusive remedy for an SLA violation — Cloudflare points customers to credits rather than another form of compensation if the service misses its target.
The claims process is time-bound and works the same way on both plans: a claim must be submitted within five business days after the incident and by the end of the billing month following the incident month. Cloudflare says customer support validates claims using reasonably available information, while also stating that it is not responsible for comprehensive monitoring of Customer Content.
Enterprise adds one procedural restriction Business does not have: only Authorized Users may submit a claim.
The plans FAQ adds an important interpretation layer for Business buyers: Cloudflare says Business downtime credits are proportional to disruption and affected customer ratio. For Enterprise, Cloudflare says customers in the Standard Success Offering receive a 10x credit, while the Premium Success Offering includes a 25x reimbursement uptime SLA.
Pricing and cost considerations
The source pack does not provide Business or Enterprise list pricing, so buyers should not treat this guide as a price sheet. What it does confirm is the cost base against which credits are calculated.
For Business, Cloudflare says service credits are calculated only against monthly recurring fees for the service, and annual service credits cannot exceed one month of cumulative monthly service fees over a twelve-month period. That means the Cloudflare SLA on Business limits the credit pool to a relatively small share of total annual spend even if there are multiple qualifying incidents.
For Enterprise, Cloudflare says service credits are calculated only against fixed Monthly Fees unless otherwise stated, and annual service credits cannot exceed six months of cumulative Monthly Fees actually paid. The plans FAQ also says Enterprise customers receive either 10x or 25x reimbursement terms depending on whether they are on the Standard Success Offering or Premium Success Offering.
There are a few adjacent billing facts in Cloudflare’s plans FAQ that may matter during plan evaluation. Cloudflare says pricing is per-domain, not per-subdomain, the first selected paid plan sets the recurring billing date, upgrades are billed pro-rata until the end of the billing cycle, additional zones are charged pro-rata for the selected plan, and downgrades take effect immediately while billing changes at the next cycle.
How to choose
For most teams, the choice starts with whether SLA coverage is needed at all. Cloudflare says the Free plan provides basic website performance and security features, but the FAQ states that SLA coverage is available for Business and Enterprise plans.
Business appears aimed at teams that want an uptime-backed commitment for Customer Content without moving into Enterprise support structures. Enterprise adds broader contractual machinery around support and operations, including online support center access, dedicated telephone support engineers, separate security incident response times for SOC Service, and a 30-minute initial response for P1 issues under TAM Service.
Success offering selection is another buyer decision. Cloudflare says Standard and Premium success offerings have different support response times, and the FAQ ties those tiers to different reimbursement terms for uptime incidents.
Enterprise support also has a defined boundary: Cloudflare says customer support does not include code development or debugging of the customer’s own websites or software.
Limitations and gotchas
The headline promise is narrower than many buyers assume. On Business, Cloudflare says the 100% uptime commitment is for Customer Content, not a blanket statement about every product behavior or every support scenario.
Both SLAs include exclusions. Cloudflare says Unscheduled Service Outages exclude customer planned downtime, and the Business policy also excludes force majeure. Cloudflare also excludes beta and trial service on Business, while the Enterprise policy says beta and trial services are excluded unless otherwise agreed in writing.
Another practical gotcha is that credits are not described as automatic in the source material used here. The documented process requires a customer claim, and on Enterprise that claim must come from an Authorized User.
Support and uptime are also distinct commitments under the Enterprise SLA. Alongside 100% uptime, Cloudflare commits to a Measurable Performance Enhancement: the service will serve customer content measurably faster than the customer’s own website would without it.
FAQ
What has to be included when a customer files an SLA claim?
Cloudflare says a claim must include a description of the incident, its duration, network traceroutes, the affected URL(s), and any steps the customer already took to resolve it.
Does downtime the customer schedules itself count against the uptime SLA?
No. Cloudflare excludes Customer Planned Downtime from Scheduled Availability, so time the customer requests offline does not count as an Unscheduled Service Outage.
What are the actual support response times under Enterprise’s Standard and Premium success offerings?
For P1 issues, Cloudflare commits to under 2 hours on Standard and under 1 hour on Premium; P2 is under 4 hours versus under 2 hours; P3 and P4 are under 48 hours versus under 24 hours.
Can a claim Cloudflare marks as resolved be reopened?
Yes. Cloudflare says an Enterprise claim closed because the customer didn’t respond within seven days can be reopened if the customer later reports the issue is still unresolved.
Are R2, Queues, and Workers covered by the general Enterprise SLA?
No. Cloudflare says those products have their own service-specific SLAs, which override the general Enterprise agreement for claims related to them.
