Disclosure: I work at AWS where I build cloud infrastructure My hypothesis is that the client connected to Cloudflare and performed a HTTP range request for a

Disclosure: I work at AWS where I build cloud infrastructure My hypothesis is that the client connected to Cloudflare and performed a HTTP range request for a portion of the 13.7 GB file. For an unknown reason, Cloudflare did not preserve this range request to S3 as the origin. It transferred the entire file, returned the range requested by the client, and dropped all bytes transferred into /dev/null because it is not caching. The end result is that Cloudflare pulled down 30 TB of data while delivering 67 GB to clients in the one month period shown in the screenshots from the blog post. See also https://blog.vbgn.be/2019/06/20/nextcloud-cloudflare.html https://blog.vbgn.be/2019/06/20/nextcloud-cloudflare.html