Seems to be a local DNS cache issue. @pixelfan was able to solve it by resetting his router.
Whatever my hoster changed, the way it was done was not really professional in my eyes. I will take further steps...
Priority for realising a 'Local SteemWorld' has changed today.
It isn't DNS. I can't ping the site by name or IP.
Pinging by IP requires no DNS.
I don't know what else is being cached in the router. Since resetting the router solved the problem for him, there must be something with it. Did changing the local IP solve it? That would mean his previous IP was blocked... The ISP (First Colo) is the point before the final 37.17.224.60.
I tried the IP directly. I can’t ping it so there is nothing I can do to make it work. I have zero ability to contact the server in any fashion.
Rebooting router didn’t work (which make sense as it isn’t a DNS issue for me).
Not sure what you mean by changing the local IP but I cannot ping it so nothing else will work if I can’t even get a packet to and from the server.
Ok, so changing the local (router's) IP does not do the trick.
Do you get a packet from 212.224.102.133?
I have exactly the same problem.
Pinging steemworld.org 37.17.224.60 is not getting there.
I do get a packet from 212.224.102.133 after that its dead.
8 32 ms 27 ms 33 ms cr03.fra1.de.first-colo.net [212.224.102.133]
9 * * * Request timed out.
10 * * * Request timed out.
I can ping and get a response to 212.224.102.133 but I don't see any web page.
I am really not sure what you mean by changing local (router's) IP. I assume you mean hard coding steemworld.org to be a specific IP, but I get the correct IP I just can't ping it. DNS works and resolves to 37.17.224.60 it just doesn't accept traffic.
I mean the router's external IP but normally that can't be the reason, because that would mean your provider does not allow returning the packet to your IP, which would not make much sense (and as you said, my hoster upgraded something, not the whole world). But I'm still wondering how @pixelfan solved the issue by resetting his router...
The 37.17.224.60 is reachable from all over the world but not for all. I've never experienced such a strange networking issue.
I'm now in contact with my hoster... If they can't find anything by tomorrow, I will move SW to my dedicated server ;)
That's the last successful hop.
Firewall??? Or combo, port 443, so your cert ...
I would make a support call with your hosting provider. Succes.