Skip to main content
← All Comparisons

Cloudflare vs Fastly.

Live

Over the last 30 days CheckUpstream measured both at 100.000% availability (n=2824 and n=2825). Over the last 30 days Cloudflare posted 60 incidents and Fastly posted 28.

Cloudflare
Degraded

30d measured availability

100.000%

Incidents posted (30d)

60

Days Cloudflare declared impact, last 30 days2026-08-02 · 100.00%2026-08-03 · 76.51%2026-08-04 · 70.00%2026-08-05 · 90.10%2026-08-06 · 100.00%2026-08-07 · 78.28%2026-08-08 · 70.00%2026-08-09 · 70.00%2026-08-10 · 70.00%2026-08-11 · 70.00%2026-08-12 · 89.28%2026-08-13 · 81.14%2026-08-14 · 70.00%2026-08-15 · 70.00%2026-08-16 · 70.00%2026-08-17 · 76.90%2026-08-18 · 87.82%2026-08-19 · 70.49%2026-08-20 · 83.66%2026-08-21 · 81.07%2026-08-22 · 70.00%2026-08-23 · 70.00%2026-08-24 · 70.00%2026-08-25 · 81.37%2026-08-26 · 86.93%2026-08-27 · 77.47%2026-08-28 · 70.00%2026-08-29 · 70.00%2026-08-30 · 70.00%2026-08-31 · 69.52%
30 days agotoday
Fastly
Partial Outage

30d measured availability

100.000%

Incidents posted (30d)

28

Days Fastly declared impact, last 30 days2026-08-02 · 100.00%2026-08-03 · 100.00%2026-08-04 · 100.00%2026-08-05 · 100.00%2026-08-06 · 100.00%2026-08-07 · 100.00%2026-08-08 · 100.00%2026-08-09 · 100.00%2026-08-10 · 98.31%2026-08-11 · 90.05%2026-08-12 · 100.00%2026-08-13 · 100.00%2026-08-14 · 100.00%2026-08-15 · 100.00%2026-08-16 · 100.00%2026-08-17 · 100.00%2026-08-18 · 100.00%2026-08-19 · 73.02%2026-08-20 · 87.59%2026-08-21 · 98.18%2026-08-22 · 100.00%2026-08-23 · 100.00%2026-08-24 · 55.06%2026-08-25 · 46.30%2026-08-26 · 92.10%2026-08-27 · 100.00%2026-08-28 · 96.41%2026-08-29 · 100.00%2026-08-30 · 100.00%2026-08-31 · 98.89%
30 days agotoday

Disclosure by window

Share of each window with no impact declared, for Cloudflare and Fastly, across five time windows
WindowCloudflareFastly
7d77.703%98.201%
30d76.008%94.530%
90d75.393%97.847%
180d75.591%92.432%
1y87.963%96.268%

Share of each window in which the vendor declared no customer impact, from their own status posts. A higher figure means fewer or shorter declared incidents — it is not a measurement of availability, and it does not make one vendor more reliable than the other. The measured availability figures are in the cards above, and only where we run a probe.

Time to resolve, from each vendor's own incident posts (30 days)

Median and 90th-percentile time to resolve for Cloudflare and Fastly, from their own published incidents in the last 30 days
MeasureCloudflareFastly
Median4h 8m36m
Slowest 10%1d5h 8m
Incidents measured5826

Time from each vendor's own incident start to their own resolution, over the last 30 days. It describes how long each takes to close an incident they have acknowledged. The incident counts are the sample size, not a score — vendors publish at very different granularities, and one that files a notice per affected region will always show more.

Cloudflare: recent incidents (30d)

Full scorecard →
Show 55 older incidents

Fastly: recent incidents (30d)

Full scorecard →
Show 23 older incidents

Published SLA terms

Cloudflare publishes 1 product-level uptime commitment with service-credit tiers. When a commitment is missed, credits are owed, but only if you file inside the window.