Skip to content

Cloudflare Workers SLACloudflare · Compute · Cloudflare · Compute

ComputeSLA of Apr 1, 2026Checked 17h ago

Promise vs reality

Downtime used against the allowance

0 min of major incidents2.3 min allowed in 16 days

0 major and 3 minor incidents. 2.6 d degraded (not counted). History covers 16 of 365 days.

Major incident minutes per month

Allowed per month: 4.4 min

All incidents, weighted: 99.984% · Downtime
Promised
99.99%
Observed, 365d
100%
Major incident time
0 min
Credit on first breach
10%

Commitments and credits

  • EnterpriseEnterprise customers' use of Workers99.99%

    Monthly uptime below, credit of the bill

    1. Below 99.99%10%
    2. Below 99.9%25%
    3. Below 95%50%

Terms

Measured
100% minus the average Error Rate Percentage (5xx on valid requests per 5-minute interval) over a 30-day period
Credit cap
Enterprise SLA cap applies (six months of Monthly Fees per annual billing period)
Claim window
Same as Enterprise SLA (notify within 5 business days; claim by end of following billing month)
How to claim
Per Enterprise SLA claim procedure

Not covered

  • Customer returning custom 500/503 status codes
  • Misconfigured routes, bindings or secrets
  • Exceeding CPU/memory resource limits
  • Unavailability of interdependent Cloudflare services (CDN, DNS, WAF, storage bindings)
  • Enterprise SLA exclusions
2.1 Cloudflare will use commercially reasonable efforts to provide a Monthly Uptime Percentage of 99.99% for Customer's use of Workers
Cloudflare, Effective Date: April 1, 2026. Read the SLA

Credit is a percentage of Workers fees paid in the 30 days preceding the claim. Cannot claim under both this SLA and the Enterprise SLA for the same Incident.

Evidence: incidents, last 365 days

Other compute SLAs

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

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.