Prerendered pages served from the edge

Prerendered pages now come straight from the edge location that receives the request. Static HTML, fresh ISR pages, and Partial Prerendering (PPR) shells no longer wait on a round trip to your function’s region.

What the edge serves

• Static HTML: prerendered pages from your build
• ISR pages: fresh entries serve from the edge; regeneration still runs your function
• PPR shells: the static shell is sent from the edge, then your function resumes the dynamic parts with the request’s query string

Revalidation and tag expiry apply in order across every edge, so an invalidated page isn’t served again.

Caches stay warm

Edge caches now survive Easel’s own restarts and platform updates. Cached pages and assets stay cached instead of every region starting cold.

Each compression encoding is cached on its own, so a cache hit for Brotli or gzip is sent as stored without being compressed again.

Static files match Vercel

Static files from your deployment stay in the edge cache for the life of the deployment, even when their Cache-Control tells browsers to revalidate with max-age=0. Browsers still follow your headers. Query strings don’t create separate copies of a static file.

Not-found pages now return a 404 status instead of 200, and a not-found response is never cached under another route’s path.

See Caching and Invalidate and revalidate cached content for details.