Now its totally different in-game, I am getting 300-600ms, the lag is worst than when the server was located in North America, I tried in game ping in Orsha and its 200-300ms.
Located in Sydney, Australia, was hoping for better in game ping, but it’s actually worst than it was before.
Pinging 52.77.112.61 with 32 bytes of data:
Reply from 52.77.112.61: bytes=32 time=164ms TTL=117
Reply from 52.77.112.61: bytes=32 time=166ms TTL=117
Reply from 52.77.112.61: bytes=32 time=169ms TTL=117
Reply from 52.77.112.61: bytes=32 time=164ms TTL=117
Ping statistics for 52.77.112.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 169ms, Average = 165ms
Tracing route to ec2-52-77-112-61.ap-southeast-1.compute.amazonaws.com [52.77.11
2.61]
over a maximum of 30 hops:
2 15 ms 16 ms 24 ms lo0.bras2.syd2.on.ii.net [150.101.32.108]
3 16 ms 15 ms 16 ms be2.cr2.syd2.on.ii.net [150.101.197.216]
4 15 ms 15 ms 15 ms ae19.br1.syd4.on.ii.net [150.101.40.130]
5 175 ms 182 ms 180 ms ae16.cr1.adl2.on.ii.net [150.101.33.189]
6 62 ms 63 ms 74 ms ae17.cr1.per1.on.ii.net [150.101.33.19]
7 135 ms 134 ms 134 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
8 192 ms 214 ms 163 ms 38895.sgw.equinix.com [27.111.228.87]
9 * * * Request timed out.
10 * * * Request timed out.
11 155 ms 163 ms 167 ms 203.83.223.17
12 168 ms 167 ms 167 ms ec2-52-77-112-61.ap-southeast-1.compute.amazonaws.com [52.77.112.61]