CDN Edge Cache Stuck — Old Version Persists Despite Multiple Purges

Help
1

Project: use-ai-writer
Custom Domain: tryaiwriter.com
Latest Commit: 999ead9
Plan: Hobby

Current Behavior

  • Custom domain tryaiwriter.com serves an old version of the site (3+ deployments behind).
  • Default Vercel domain use-ai-writer.vercel.app returns ERR_CONNECTION_TIMED_OUT.
  • All deployments show “Ready” status.

Expected Behavior

  • The latest deployment (commit 999ead9) should be served on both domains.

What I’ve Tried (All Failed)

  • Purged CDN cache (All content) multiple times.
  • Redeployed 4+ times without “Use existing Build Cache”.
  • Removed and re-added the custom domain.
  • Tested in incognito windows and with cache disabled.
  • Added vercel.json with Cache-Control: no-cache, no-store, must-revalidate.
  • Audited entire codebase — zero ISR, cache, or stale-time configurations exist.

Vercel AI Agent’s Diagnosis

  • CDN edge cache was purged but old content persists.
  • Response headers showed age of 2970 seconds with stale time of 300 seconds.
  • Agent recommended manual hard CDN edge node cache flush, but I’m unable to submit a Severity 1 ticket on a Hobby plan.

Request

Can the Vercel engineering team manually perform a hard flush of the CDN edge cache for this project? This appears to be a CDN bug where purged content is still being served from edge nodes.

Thank you!