CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Cache / CDN
  4. ›Update

Feature•May 4, 2026

Pingora now powers Cloudflare's cache

Cache / CDNCloudflare · Application performance

Cloudflare's cache now runs on a new proxy built on Pingora, the Rust-based framework that already serves a significant portion of Cloudflare's network traffic. The new proxy is faster, more memory-safe, and designed to evolve our cache architecture. It delivers immediate performance improvements and enables new caching capabilities.

What this brings

  • Lower latency: The new proxy reduces per-request overhead through improved connection reuse.
  • Reduced cache MISSes: Enhanced cache retention improves origin offload.
  • Better RFC compliance: Caching behavior more closely follows HTTP caching standards.
  • Foundation for future features: The new architecture enables upcoming improvements to cache functionality and efficiency.

New features

  • Asynchronous stale-while-revalidate: Every request returns stale content immediately while revalidation happens in the background, instead of the first request after expiry blocking on the origin. Refer to the asynchronous stale-while-revalidate changelog for details.
  • Unbuffered bypass by default: Responses that bypass cache are streamed directly to the client without buffering, reducing time-to-first-byte for uncacheable content.

Behavioral changes

The new architecture introduces the following behavioral changes to improve RFC compliance and correctness:

  • Vary: * results in cache bypass: According to RFC 9110 Section 12.5.5, a Vary header value of * indicates the response varies on factors beyond request headers and must not be served from cache. Cloudflare now bypasses cache for these responses instead of storing them.
  • Set-Cookie stripped on MISS and EXPIRED: For cacheable assets, Set-Cookie is now stripped on MISS and EXPIRED responses, not only on HITs.
  • Floating-point TTL values: Floating-point time-to-live values (for example, max-age=1.5) are rounded down to the nearest integer instead of being rejected as invalid.

What's next

A deeper look at the new cache proxy is coming soon to the Cloudflare blog. For background on the underlying framework, read:

  • Open sourcing Pingora: our Rust framework for building programmable network services
  • How we built Pingora, the proxy that connects Cloudflare to the Internet

Read the original announcement↗

More from Cache / CDN

All Cache / CDN updates →
  1. Invalidate cached content instead of purging it

    You can now invalidate cached content instead of purging it. Invalidation marks matching content as stale. On the next request, Cloudflare revalidates the content with your origin.

    Cache / CDN•Feature•Sep 28, 2026
  2. Purge now forces a cache miss for Cache Reserve content

    Purge requests now force a cache miss for Cache Reserve content, regardless of purge type. Previously, purging by cache tag, hostname, prefix, or everything marked matching Cache Reserve content for revalidation.

    Cache / CDN•Feature•Sep 28, 2026
  3. Configure Origin Range Requests with the Rulesets API

    The Rulesets API now supports Origin Range Requests in Cache Rules. This setting lets Cloudflare fetch large files from your origin in cache-aligned byte ranges. Cloudflare may expand a client range and issue several single-range origin requests.

    Cache / CDN•Feature•Sep 2, 2026
  4. Cache multiple versions of a URL with Vary

    Your origin can serve different responses for the same URL — different languages based on Accept-Language, or different formats based on Accept — by returning a Vary response header.

    Cache / CDN•Feature•Jul 2, 2026
  5. BYPASS status now returned for uncacheable responses

    Cloudflare now returns a BYPASS cache status whenever a response is not cacheable, instead of the previous mix of BYPASS and MISS that depended on why Cloudflare chose not to cache the response.

    Cache / CDN•Feature•May 26, 2026