Uptimeby GlyphCloudflare Business plan (CDN / application services) SLA
Cloudflare · Edge and CDN · promises up to 100% · checked 47d ago
1 major outage in the 71 days of history: 11 min counted, 99.989% observed against the 100% Business plan.
1 of 3 months fell below it (credits are claimed per month).
Last 90 days: 11 min counted, 99.989% observed.
Incidents, last 365 days
Elevated errors for some requests in Ashburn, Virginia
A minor incident on CDN/Cache, Workers, Ashburn, United States - (IAD) for 30 min, not counted as downtime.
2 weeks ago
Increased Latency in IndiaA minor incident on CDN/Cache for 3.3 h, not counted as downtime.
2 weeks ago
Increased HTTP 502 ErrorsA minor incident on CDN/Cache, Network for 9.9 h, not counted as downtime.
3 weeks ago
Cloudflare Network Performance IssuesA minor incident on CDN/Cache for 7.5 h, not counted as downtime.
4 weeks ago
Cloudflare CDN experiencing increase in errors.A major outage on CDN/Cache, CDN Cache Purge for 11 min, counted as downtime.
5 weeks ago
Major outage time per month
Commitments and credits
Business plan
Customers who purchased and enabled Services at the Business Level
Credit: No credit schedule published
More in edge and cdn
Cloudflare promises 100% uptime; its status page showed 11 min of major outage in the 71 days on file.
Observed 99.989% over 365 days
Fastly Network Services (CDN / edge delivery)Fastly promises 100% uptime, with a 1% credit when it misses; its status page has no history this site can read.
Fastly Next-Gen WAF (Hosted Dashboard and Cloud WAF Hosted Services)Fastly promises 99.9% uptime, with a 5% credit when it misses; its status page has no history this site can read.
Cloudflare Enterprise (CDN / application services)Cloudflare promises 100% uptime; its status page showed 11 min of major outage in the 71 days on file.100%First creditn/aObserved 365d99.989%All incidents 99.951%
Terms, exclusions and sources
- Measured
- Outage Period minutes weighted by Affected Customer Ratio (share of unique visitor IPs affected), against Scheduled Availability minutes in the month
- Credit cap
- Total Service Credits in any 12-month period shall not exceed one (1) month of cumulative total monthly service fees
- Claim window
- Notify Customer Support within five business days of the Incident; submit the Claim by the end of the billing month following the billing month of the Incident
- How to claim
- Contact Customer Support with incident details, duration, traceroutes and affected URLs
- Not covered
- Factors outside Cloudflare's reasonable control; Customer or third-party hardware or software; Actions or inactions of Customer or third parties; Continued use after Cloudflare advised a change; Beta and trial services
- Status history
- Status history since Aug 27, 2026
- Weighted uptime
- All incidents, weighted: 99.951% · Downtime
1.1 100% Uptime. The Service will serve Customer Content 100% of the time without qualification.
No fixed credit table: credit is proportional, 'Service Credit = (Outage Period minutes * Affected Customer Ratio) / Scheduled Availability minutes' (Section 6.1), i.e. a 1x multiplier of the outage fraction, unlike the 10x/25x Enterprise formula. Page carries no version date. Free and Pro plans have no published uptime SLA.