Cache - Purge now forces a cache miss for Cache Reserve content

UpdateSep 28, 20265d5 days ago·Unverified·Added Oct 2, 2026

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. Purging by URL already removed content from Cache Reserve and is unchanged. This change applies to purge requests from the API and the dashboard.

Topics: Governance, Pricing, BI, Developer tools