WORLD WATCH · October 23, 2026 · RESEARCH
Cloudflare cuts origin bandwidth use
Cloudflare cut origin bandwidth use for large file requests by changing range caching.
- Reported by
- Cloudflare
- Outlets reporting
- 1
- Category
- RESEARCH
- Newest report
- October 23, 2026
Plain-English brief. Written for readers who work in a second language.
Key takeaways
- Cloudflare rebuilt range caching in Pingora
- Partial fetches now coordinate automatically
- R2 p99 latency fell by half
What happened
The report comes from Cloudflare. Cloudflare rebuilt its cache architecture in Pingora. The new design coordinates partial fetches automatically. Naive byte-range caching previously wasted origin bandwidth on small requests. The change cut R2 p99 latency in half.
Why it matters
The change affects origin bandwidth use for large file delivery. Lower latency affects R2 response times for partial requests. The update targets coordination between cache and origin for range requests.
What to do
- Review range caching behavior for large files at origin.
- Test partial fetch limits against current origin capacity.
- Monitor R2 latency for range requests after any related change.
SOURCE: INTEL128 WORLD WATCH (UPDATED OCT 24, 2026). This brief summarizes reporting by Cloudflare. Intel128 writes the summary and credits the outlet. Read the summary as a starting point, not as a substitute for the original reporting.