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:
- One from a request where the correct content is displayed
- 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.