Site not updating – shows old version in UK, France and Romania

Support
,
1

Hello,

I deployed my static site for the domain mateimiron.link, but it still shows the old version. I tested from 3 different countries (UK, France, Romania) and cleared cache, tried incognito mode, and also redeployed several times from Netlify.

Everything is set up correctly, including DNS and domain settings.

Can someone help me force the update or check if something is stuck in deployment?

Thank you very much!

2

Hi @Matei,

Thanks for reaching out!

I’ve tested the site using a VPN, multiple browsers (to rule out caching), and locations across several countries (that you mentioned), but I haven’t been able to reproduce the issue.

To help us investigate further, could you please provide two x-nf-request-id headers:

  1. One from a request where the correct content is displayed
  2. One from a request where the old or unexpected content appears

You can find the x-nf-request-id by opening your browser’s developer tools and checking the response headers for the relevant request. We have a Support Guide here on how to find the x-nf-request-id.

3

Hi, thanks for the reply!
I’m currently using only an iPad, so I can’t access browser developer tools to extract the x-nf-request-id.

Just to clarify, I’ve had this same issue before with my old domain: mateimiron.link, and now it’s happening again with the new one: shopcraftdesign.com.

On both domains, even after redeploying and updating DNS, the old version of the site continues to display in many locations (tested via VPN and tools like GeoPeeker).

Can you help force a cache purge or full update from your side?

Thanks again for your help!

4

Hi, @Matei. There has only been one version of that site deployed to Netlify so it is impossible for this to be a CDN caching issue. There has never been a previous version of the site served by Netlify so it is impossible for us to have a previous version cached. We cannot cache something that never existed in the first place.

I believe what you are seeing is caching of DNS records in downstream DNS resolvers. That is not something Netlify can control nor can we purge those caches. There is a support guide with more information about this below:

6

Hi,

I am opening a new topic as my previous one got closed, but the issue is not yet resolved.

Domain: shopcraftdesigcom

Issue:
• I have deployed a new version of the site successfully on Netlify.
• DNS is fully propagated and correct (checked viaDN S Checker and GeoPeeker).
• On the Netlify subdomain the correct version shows.
• On shopcraftdesigcom, in many countries (UK, France, Romania, Germany), the old version is still showing even after 5-6 days.
• I tested with clean VPN from Germany (Frankfurt) — verified IP, same old version still served.
• I tested with multiple devices and networks, incognito, clear cache — same result.

This is now clearly a CDN caching or DNS caching issue outside my control. I already had this same problem a few weeks ago with my previous domain mateimiro link , and it required manual purge or deeper investigation.

I am currently using only an iPad so I cannot provide x-nf-request-id headers.

Can you please assist and force a full cache purge or verify why the old version is still served globally?
Thank you very much
P.S.: Please do not close this topic until the issue is fully resolved.
I am still seeing the old version globally even after multiple days and confirmed VPN tests.
Thank you very much for your support!

7

Hi, @Matei. This is the blocker right here:

Only you can see the issue occurring so only you can gather the information to troubleshoot it. If you cannot figure out how to get headers or additional information from the device you are using to test, no one is going to be able to assist you.

About this:

Can you please assist and force a full cache purge or verify why the old version is still served globally?

I already told you there is nothing cached at Netlify. Something else is happening here but we cannot tell what is happening unless you provide the information that only you have access to. We cannot help you until you learn to help yourself by getting the information required to troubleshoot this issue - information only you can get.

What I think is happening is that your have a hard coded DNS record locally (in an device or in a router) pointing to the old version or that the mobile device has the version cached locally. The caching issue definitely is not at Netlify, though, that much I can say with certainty.

There are instructions to see the headers on an iPad here:

https://stackoverflow.com/questions/5734323/ipad-safari-development-toolbar

This is what we need to troubleshoot. Either:

  • the x-nf-request-id HTTP response header for an incorrect response

or, if that header cannot be found for some reason, we need the information it replaces which is this:

  • the full URL requested
  • the client IP address making the request
  • the server IP address that responds
  • the date and time of the request (with the timezone for the time)

That is the bare minimum amount of information needed to troubleshoot. Only you can get that information to share with us. If you share it, we will help you. If you cannot figure out how to get that information, please let us know what you attempted and what the results were. We’ll try to help you get this information but this is something only you can do.

8

Hi,

I was able to access the request details now from a Windows laptop.
• Domain: shopcraftdesign. com
• Date & Time (UTC): Sat, 14 Jun 2025 22:07:13 GMT
• x-nf-request-id: 01JXR7Q1W09P3AV943WSSFWE93
• Issue: The old version of the site is still being served globally, even after several days and full redeploys.

Please check the request ID above and confirm whether something is stuck or misconfigured on the CDN/DNS edge.

Thank you for your help!

10

Hi, @Matei. That request id was for this URL below:

https://shopcraftdesign.com/

We served a 304 response and the content used was for deploy 68410ef32473d3acfb9996bc, which is the only deploy for this site. This is the only version of this site ever uploaded to Netlify and it is the version we served.

If you know you site’s name, you can see the deploy by replacing <site name here> with the site’s name in the URL below:

https://app.netlify.com/sites/<site name here>/deploys/68410ef32473d3acfb9996bc

There are only two files in that deploy and there versions we send when an HTTP request is made matches the versions uploaded.

I don’t think there is anything wrong with the CDN or caching. Can you explain what you expect to see different and why you expect it to be different?

I think something is being missed here. For example, I think you may have an assumption that making a change somewhere is making a change at Netlify when it is not. This site is using manual deploys so it won’t change until a new manual deploy is made.

This manual deploy (68410ef32473d3acfb9996bc) was made June 4th and Netlify has served only that one version since that day. We could not serve an “old” version as there has never been a previous version of this site.