Vercel is serving an old page. A redeploy may not be enough.

How to tell it’s Vercel

Vercel sends x-vercel-cache on every response. There are six values. source

Don’t over-read a MISS. Vercel’s docs warn that for dynamic routes and fetches using the runtime cache, this header “often shows MISS even if the data is served from the runtime cache”. source The runtime cache is regional and persists across deployments. source

How to clear it

1. Dashboard: open your project, choose CDN in the sidebar, then Caches. Under Purge cache pick what to purge and press Purge. Invalidate marks a tag stale and refreshes in the background; Delete revalidates in the foreground and Vercel does not recommend it. * purges the whole project. source
2. CLI: vercel cache purge, or narrow it with --type cdn or --type data. By tag: vercel cache invalidate --tag blog-posts. source
3. Next.js, in code: revalidatePath(), revalidateTag() or updateTag(). source

If the old page comes straight back

• You redeployed and expected a purge. Each deployment has its own cache key, so a promotion sidesteps the old cache rather than clearing it — and Vercel notes that purging also clears Image Optimization and ISR content, “which is usually preserved between deployments”. source
• You shortened Cache-Control and nothing changed. On Vercel, Vercel-CDN-Cache-Control has top priority, CDN-Cache-Control always overrides Cache-Control, and Cache-Control comes last. Fix the header that actually wins. source
• Static files. They are cached on Vercel’s network for the lifetime of the deployment after the first request, and Vercel does not allow bypassing the cache for them by design. source

Working without it for a while

There is no global development mode for the CDN, but a request carrying Pragma: no-cache — which browsers send with devtools open — makes Vercel revalidate a stale resource synchronously. Draft Mode also produces BYPASS. source

Other fix guides