My live site isn't showing my latest deploy

Updated 2026-10-17

Short answer: a deploy can say "success" while the live site still serves an older version: a cache, a custom domain attached to a different project, or a failed build that left the last good one in place.

How to check it yourself

  1. Check your host's deploy history: did the latest production deploy succeed?
  2. Open the deploy's own preview address and compare it with your live domain.
  3. If they differ, check which project or branch your custom domain is attached to, and purge any CDN cache.
  4. Check that your DNS points at the project you're deploying to.

Why it matters

If the live site serves an older version than the one you deployed, a fix you think is live isn't, and visitors keep hitting the bug. It also makes testing confusing, because what you see in one browser can differ from what visitors see through a cache.

Common causes

  • A CDN or host cache is still serving the old files.
  • The deploy went to a preview or staging branch, not production.
  • The domain points at a different project or server than the one you deployed.
  • The browser cached old JavaScript or CSS files with long cache times.

What Preventionlabs shows

With a read-only Cloudflare token connected, every report checks whether the latest production deploy of each Cloudflare Pages site succeeded, whether the live homepage is the one that deploy serves, and recent Worker updates, so a problem can be matched to the change before it.

Price

First report free, no card needed. Then A$50 a month, up to 10 domains.

Run your first report free