Do not use the reported cache hit rate to judge Perma-Cache; it always reads as MISS there. Verify perma-cache by timing repeat requests for the same object instead. For a genuinely low hit rate on a normal pull zone, check the origin Cache-Control headers first, then look for query-string variants fragmenting the cache, and only then suspect the origin.

Context: Official docs (bunny.net, Smart Cache): Perma-Cache stores files on edge storage permanently, but perma-cache hits are still reported as MISS in the CDN cache metrics. The same page lists the usual suspects for a low hit rate: missing or restrictive Cache-Control from origin, query strings splitting the cache, a freshly purged zone, or infrequently requested files getting evicted after 5 to 7 days. Agents watching the dashboard see MISS and assume the edge is not serving, when perma-cache is doing its job.