If this behavior it's not browser-dependent, another thing that comes in mind is a possible local dns cache conflict. For this there's the following command:
Source of the post
Perhaps this is an issue worth looking into rather than waiting for it to fix itself?
Of course, before doing this though we should exclude possible software caching problems.
Once the russian website provider has done with changes, its work is done. From that moment, other DNS servers, notably those of our own internet providers, must acknowledge the change, and this time varies. If they are big providers they could also use cache-only DNS servers, which could detain old information regarding the website for a period to their discretion, and obviously nobody else has control over this.
Another suggestion is to try and change DNS servers in your network apparatus (or your network card) if possible, by substituting those of your internet provider with others.
Personally I use Google DNS because I've noticed filtering behavior with those of my provider. Another one could be OpenDNS.
- Primary 18.104.22.168
- Secondary 22.214.171.124
- Primary 126.96.36.199
- Secondary 188.8.131.52
At the old website there's a request:
Please clear your browser cache. Requests to the old data on this website casues extreme load to the hosting. Thank you.