This issue seems to be ISP specific. I receive this error on my Comcast and my Optimum connections, but never on Verizon. I was able to log in using my Verizon ISP at the same time the other two were giving me issues.
I'm fairly sure this has to do with DNS propagation. If you're accessing a nameserver that hasn't been updated then you're going to see this. Not sure what caused the initial issue though - like what kind of server-side update to the game or is someone messing with the DNS settings, no idea.
| 
02-27-2020, 10:09 AM
Threaded Mode