Get Started

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

EngineeringCloud InfrastructureNetworkingBackend

First reported · 11h ago · 1 source

Crest summary — written by AI from the 1 source below; every figure is checked against them · model deepseek-flash

Summary

Cloudflare rebuilt its cache architecture in Pingora to coordinate partial fetches automatically, so customers can serve large files without tuning range requests.

Key facts

  • Cloudflare said the change cuts R2 p99 latency in half.
  • The rebuild targets byte-range caching that can waste origin bandwidth on small requests.
  • The work was done in Pingora, Cloudflare's proxy framework.

Why it matters

Teams serving large files through Cloudflare's cache can get faster tail latency on R2 without configuring range requests themselves.

Companies

Technologies

  • Pingoraframework
  • R2product

Related on Crest

Matched by rule, not by AI: a repository linked in the coverage, or a technology or company in this event that Crest tracks.

Repositories

Packages

Original sources (1)

The report this event was built from. Crest of Tech keeps no article bodies: the full text is at each source.

  1. Cloudflare BlogOfficial · Primary
    Origin Range Requests: Serving large files without range-request tuning · By Matthew Gumport
    Read at Cloudflare Blog
Origin Range Requests: Serving large files without range-request tuning — Crest of Tech