Risks in Cloudflare, Fastly, and AWS CloudFront for CDN teams
Cloudflare offers significant savings for high-egress workloads, potentially saving $85,507 over three years compared to AWS. However, providers face distinct risks including HTTP/3 vulnerabilities, service outages, and regulatory fines like Cloudflare's €14 million penalty in Italy.
HTTP/3 vulnerabilities and connection limits
Researchers at the National University of Singapore, Fuzhou University, the University of Sheffield, and Johns Hopkins identified two denial of service techniques that exploit the gap between HTTP/3 and HTTP/1.1. These attacks, named HBA and HCA, turn a content delivery network against the origin server. Cloudflare remains the exception to the connection exhaustion vulnerability because it buffers the complete request before opening an origin connection. While Alibaba, CloudFront, and Fastly discussed mitigations internally, Cloudflare does not support the QPACK dynamic table. This absence of dynamic table support excludes Cloudflare from the 350x amplification figure that applies to providers supporting the dynamic table. While CloudFront accounts for 17,433 of the 42,330 potentially vulnerable subdomains, Cloudflare accounts for 12,371, while Fastly accounts for 11,606 of the total subdomains identified by the research team during their testing across six different providers. The HBA attack uses QPACK’s static table to refer to common headers, which keeps the request leaving the attacker tiny while the CDN reconstructs a larger request for the origin server. This method achieves bandwidth amplification between 36.41x and 66.06x. The HCA attack allows an attacker to hold connections open and exhaust the origin’s connection pool. During tests, connections from the CDN to the origin exceeded 300. The researchers used a VPS in Singapore to conduct tests and capped attacker bandwidth at 30 megabits per second. The HCA attack remains quieter than the HBA variant. The researchers identified 42,330 HTTP/3-enabled subdomains as potentially vulnerable. Fastly experienced a global outage due to a service configuration error that disrupted its points of presence. Cloudflare also experienced a 2020 outage following a configuration error.
The cost of moving data
Migration from AWS to Cloudflare depends entirely on monthly egress bills. A mid-sized business with 50 million monthly requests and 8 TB of storage costs $34,982.64 per year on AWS. The bulk of this cost, 89 percent, comes from S3 egress. Cloudflare costs $2,575.80 per year for the same workload using Workers and R2. This $2,915.22 monthly difference generates $85,507 in savings over three years. If a business moves only 200 GB of egress per month, the $13.05 saving fails to cover any migration effort. Below 1 TB of monthly egress, the numbers collapse and migrating becomes a waste of money. AWS provides free data transfer to the internet for eligible customers who move all their data off AWS.
| Item | AWS Cost | Cloudflare Cost |
|---|---|---|
| Monthly Total | $2,915.22 | $214.65 |
| 3-Year Total | $104,948 | $19,441 |
The decision to move depends on the specific workload. For a system with 30 TB of monthly egress and 8 TB of S3 storage, the cost on AWS reaches $2,915.22 per month. Cloudflare brings that cost down to $214.65. This saving covers the engineering costs of moving and the period of running both stacks in parallel. A system with 50 million requests, 250 ms wall-clock latency, 10 ms CPU, and 256 MB memory costs $55.22 per month in Lambda compute. The S3 component costs $184 for storage, $60 for GET requests, and $25 for PUT requests.
Regulation and control
Regulatory disputes create legal and reputational risks for infrastructure providers. Cloudflare faced a €14 million fine from Italian authorities regarding the Piracy Shield system. This system empowers regulators to order the blocking of IP addresses, which can disrupt unrelated websites that share the same infrastructure. The fine, pegged to global revenue rather than Italian turnover, signals that the regulator expects full compliance from multinational firms. You should realize that vendor-managed services require you to trust the provider to resolve service failures. This distinction between application-level failures, which users can fix, and service-level failures, which depend on the vendor, creates significant operational pressure.
Cloudflare reported an incident affecting users for 6 hours and 39 minutes on 23 October 2026. In North America, Durable Objects saw an increased error rate in colos due to a sudden increase in traffic on 12 November 2026. Moving to serverless architectures with Amazon, Microsoft, or Google means you lose the ability to tune Linux kernel parameters or optimize at a granular level. Cloudflare even threatened to withdraw free cybersecurity services from the Milano-Cortina Winter Olympics to protest these regulatory powers. How long until the next regulatory clash occurs? Cloudflare provides the best value for high-egress workloads despite these infrastructure risks.