# Why does a deployed site still show an older version?

Canonical URL: https://help.iagenify.com/faqs/hosting/why-does-a-deployed-site-still-show-an-older-version

[← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)

HELP CENTER · FAQ Hosting 2 min read
# Why does a deployed site still show an older version?
A successful deployment can coexist with cached content or a request routed to a different host. Confirm the active deployment and hostname first, then compare a fresh request and the deployed files before rebuilding or changing DNS.
IaGenify
Hosting

## Confirm which version is being served
Check the hosting dashboard or deployment history for the latest successful release and its associated domain. A stale browser tab or cached asset can make a correct deployment appear outdated, while a second hostname may still point elsewhere.
Test in a private window or request the page with cache disabled, and inspect the asset URLs referenced by the HTML. If the HTML is current but one file is old, investigate caching for that specific asset rather than assuming the whole release failed.
## Trace routing before redeploying
Verify that the hostname resolves to the intended host and that any redirect sends visitors to the canonical address. Check whether a proxy, CDN, or service worker in your setup is serving cached responses.
If the deployment itself contains old files, review the build source, branch, and output directory, then create a new deployment after correcting them. Record the deployment identifier and test the public domain after the update completes. [← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)