I did some researching doing TCPView software. When I start Diablo 3 it connected to 126.96.36.199 and the connection is ok. PingPlotter shows no issues either. Then once I press ‘Start a game’ button, Diablo 3 tries to connect to 188.8.131.52 . And it is there where it has troubles. Because PingPlotter shows 100% packet loss for that server. It can’t connect to it. And diablo 3 can’t start a new game either. So maybe you should test if that server is really working and up? Can someone test if he/she can ping 184.108.40.206 ?
As for now any 37.244.32.xx server range is down for me.
Another server that seems to be down - 220.127.116.11 . It is used when I try to join a public game. Can’t connect either.
Will you fix those servers plz? 18.104.22.168 is not working properly either. 37.244.33.xx and 37.244.32.xx needs thorough testing. Because if you use
check-host.net you will see that for example, 22.214.171.124 is can’t be pinged , no answer for TCP or UPD protocols.
I now CAN start a game. And in town the ping is playable though high. But as soon as I enter a GR or normal rift latency grows up to 2k-3k !