Increase in ping and lag

[Exmo]

That's pretty funny

But looks like hop 6 is the interesting thing here. Would your ISP shed light on this?

[SoloD007]

That's pretty funny

But looks like hop 6 is the interesting thing here. Would your ISP shed light on this?

As far as I know. I remember when I use to play on JP data center from Oceania. I did a trace route and the packet of data had to route to Hong Kong first before it can route to Japan data center. So In this case, I believe it's a routing issue in square-enix network setting. But, to why it routes to other data center location after routing to JP such as U.S and EU and then back to AU. I wouldn't have a clue. Lol.

P.S I did ping and tracert to another AU server and I'm getting around 40 - 45 ms ping so. It's definitely not an issue with my ISP.

DNS servers in Australia ; 123.200.168.132, Brisbane, Australia 9723 iseek Communications Pty Ltd

C:\Users\OEM>ping 123.200.168.132

Pinging 123.200.168.132 with 32 bytes of data:
Reply from 123.200.168.132: bytes=32 time=47ms TTL=55
Reply from 123.200.168.132: bytes=32 time=48ms TTL=55
Reply from 123.200.168.132: bytes=32 time=48ms TTL=55
Reply from 123.200.168.132: bytes=32 time=46ms TTL=55

Ping statistics for 123.200.168.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 48ms, Average = 47ms

C:\Users\OEM>tracert 123.200.168.132

Tracing route to 123.200.168.132 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.xxx.xx.1
2 * * * Request timed out.
3 6 ms 3 ms 3 ms 203.109.129.97
4 10 ms 3 ms 3 ms 203.109.129.98
5 * * 4 ms 202.50.233.222
6 * * * Request timed out.
7 45 ms 47 ms 47 ms be202.lsr01.bour.nsw.vocus.network [103.1.77.14]
8 46 ms 47 ms 47 ms be801.lsr01.crek.qld.vocus.network [103.1.76.138]
9 * * * Request timed out.
10 46 ms 43 ms 43 ms be1.bdr02.bne03.qld.vocus.network [114.31.194.49]
11 43 ms 44 ms 47 ms static-230.89.255.49.in-addr.VOCUS.net.au [49.255.89.230]
12 45 ms 47 ms 47 ms 123.200.168.132

[SoloD007]

That's pretty funny

But looks like hop 6 is the interesting thing here. Would your ISP shed light on this?

and another ping and trace route to an Australia server located in Sydney.

170.64.147.31 Sydney, DIGITALOCEAN-ASN

C:\Users\OEM>ping 170.64.147.31

Pinging 170.64.147.31 with 32 bytes of data:
Reply from 170.64.147.31: bytes=32 time=33ms TTL=51
Reply from 170.64.147.31: bytes=32 time=30ms TTL=51
Reply from 170.64.147.31: bytes=32 time=31ms TTL=51
Reply from 170.64.147.31: bytes=32 time=30ms TTL=51

Ping statistics for 170.64.147.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 33ms, Average = 31ms

C:\Users\OEM> tracert 170.64.147.31

Tracing route to 170.64.147.31 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.xxx.xx.1
2 * * * Request timed out.
3 7 ms 3 ms 3 ms as9500.auckland.megaport.com [43.243.22.92]
4 7 ms 7 ms 7 ms as4826.auckland.megaport.com [43.243.22.18]
5 29 ms 31 ms 31 ms be101.bdr01.akl05.akl.nz.vocus.network [114.31.202.50]
6 * * * Request timed out.
7 32 ms 31 ms 31 ms be1.bdr04.syd03.nsw.vocus.network [114.31.192.115]
8 33 ms 31 ms 31 ms ip-250.71.254.124.static.VOCUS.net.au [124.254.71.250]
9 32 ms 31 ms 31 ms 143.244.224.180
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 31 ms 31 ms 31 ms 170.64.147.31