---
title: "Origin Range Requests: Serving large files without range-request tuning"
description: "Naive byte-range caching in CDNs can waste huge bandwidth when a small client request triggers a large origin fetch—for example, a seek request for a few megabytes could pull 128 MiB. Cloudflare’s previous implementation used fixed range sizes that created tradeoffs; the size was part of the cache key, so updates invalidated entries, and it could not combine with concurrent streaming, forcing downloads before serving. The new Origin Range Requests feature, a self-service option with no tuning, uses Pingora’s fixed-size chunks to align client ranges to chunk boundaries and fetch only the aligned chunk. A coordinator merges bytes from cache, in-flight downloads, and origin responses, checking entity tags and refusing to combine across representation changes. Enabling Origin Range Requests halved p99 time to first byte for R2, cut tiered cache traffic by roughly 6 percent, reducing petabyte-scale daily data movement."
---

# Origin Range Requests: Serving large files without range-request tuning

[Cloudflare](https://yomu.fyi/company/cloudflare) · Matthew Gumport · Oct 23, 2026

**Type:** Announcement

## Summary

Naive byte-range caching in CDNs can waste huge bandwidth when a small client request triggers a large origin fetch—for example, a seek request for a few megabytes could pull 128 MiB. Cloudflare’s previous implementation used fixed range sizes that created tradeoffs; the size was part of the cache key, so updates invalidated entries, and it could not combine with concurrent streaming, forcing downloads before serving. The new Origin Range Requests feature, a self-service option with no tuning, uses Pingora’s fixed-size chunks to align client ranges to chunk boundaries and fetch only the aligned chunk. A coordinator merges bytes from cache, in-flight downloads, and origin responses, checking entity tags and refusing to combine across representation changes. Enabling Origin Range Requests halved p99 time to first byte for R2, cut tiered cache traffic by roughly 6 percent, reducing petabyte-scale daily data movement.

## Context

HTTP range requests allow clients to fetch parts of a large file, but naive caching at CDN scale wastes bandwidth and disk operations when a small client request triggers a large origin fetch. Cloudflare’s previous range caching used a static, configurable range size that created tradeoffs and could not combine with concurrent streaming.

## Approach / What changed

Origin Range Requests aligns each client range to the cache’s fixed-size chunk boundaries, fetches only the aligned chunk from the origin if missing, and uses a coordinator to merge bytes from cache, in-flight downloads, and origin responses. It checks entity tags and avoids combining ranges across representation changes or compressed responses. It is available as a self-service Cache Rule with no tuning required.

## Takeaways

- Under Cloudflare’s old range caching, a small client seek could trigger a 128 MiB origin fetch, wasting bandwidth and disk operations.
- The new implementation reuses Pingora’s fixed-size cache chunks as the range unit, so the range size is no longer a customer-configurable setting that invalidates cache on update.
- For R2, Origin Range Requests halved p99 time to first byte and reduced tiered cache traffic by about 6 percent, saving petabytes of daily data movement.

## FAQ

### How does Origin Range Requests differ from the old range caching?

The old implementation used a fixed, configurable range size that was part of the cache key, causing tradeoffs and cache invalidation on size changes. The new system aligns client ranges to Pingora's fixed-size chunks and serves merged responses from cache, in-flight downloads, and origin.

### Does Origin Range Requests make uncacheable responses cacheable?

No. The feature does not change normal cache eligibility; it only changes how Cloudflare satisfies range requests for cacheable objects. The origin must still support byte ranges for partial fetches.

### What traffic is Origin Range Requests intended for?

It is designed for large cacheable objects where clients naturally request parts, such as progressive video (MP4), resumable downloads, software distributions, disk images, AI model files, and workloads that fetch small regions of large artifacts.

**Tags:** [Caching](https://yomu.fyi/topic/caching), [Cloudflare](https://yomu.fyi/topic/cloudflare), [Performance](https://yomu.fyi/topic/performance), [Product Announcements](https://yomu.fyi/topic/product-announcements), [Storage](https://yomu.fyi/topic/storage)

- Source: [Cloudflare](https://blog.cloudflare.com/origin-range-requests)
- Source URL: https://blog.cloudflare.com/origin-range-requests
- Ingested by Yomu: 2026-10-23T21:00:13.429Z

[Read original post](https://blog.cloudflare.com/origin-range-requests)
