-
Big latency change.
Hello.
I play on Valefor and lately experience very high latency in-game. Usualy my ping to the server ip 124.150.157.47 (got it from my task manager resourse monitor as the main connection of FFXIV.exe process) was 49-60 ms. And now the traceroute shows:
___
7 5 ms 5 ms 4 ms 10.255.25.2
8 4 ms 4 ms 4 ms 95.167.172.97
9 15 ms 16 ms 16 ms 95.167.95.254
10 40 ms 37 ms 50 ms 188.254.55.226
11 36 ms 36 ms 36 ms 106.187.6.161
12 40 ms 37 ms 37 ms 118.155.197.178
13 236 ms 236 ms 247 ms 106.187.28.198
14 237 ms 237 ms 237 ms 61.195.56.133
15 239 ms 240 ms 239 ms 219.117.144.78
16 242 ms 243 ms 242 ms 219.117.144.49
17 245 ms 237 ms 238 ms 219.117.144.29
18 240 ms 236 ms 239 ms 219.117.147.186
19 237 ms 237 ms 237 ms 124.150.157.47
the main ip hop that gets 200+ latency is Japan to Japan.
After that i checked the current ip connected and found there 124.150.157.36 as the main connection for ff14 process. And its even much worse:
____
6 4 ms 4 ms 6 ms 10.250.248.1
7 4 ms 4 ms 4 ms 10.255.25.2
8 6 ms 4 ms 4 ms 217.150.57.94
9 176 ms 176 ms 177 ms 80.81.194.117
10 174 ms 173 ms 185 ms 80.81.193.47
11 324 ms 323 ms 323 ms 202.147.50.168
12 429 ms 431 ms 433 ms 202.147.0.33
13 433 ms 433 ms 433 ms 202.147.0.178
14 429 ms 431 ms 430 ms 203.192.149.210
15 452 ms 428 ms 428 ms 61.195.56.129
16 431 ms 430 ms 430 ms 219.117.144.66
17 433 ms 434 ms 433 ms 219.117.144.45
18 429 ms 431 ms 441 ms 219.117.144.29
19 482 ms 485 ms 431 ms 219.117.147.182
20 432 ms 432 ms 432 ms 124.150.157.36
As i see according to WHOIS the trace goes to Germany first and after that to Japan.
Could you please help me with this issue. I would like to know if something happened lately with servers. This started nearly a week ago.
Playing with current ping is nearly impossible. Also my FC mates from other countries expirience same problems.
-
The changes happening along your route are far more likely to be the result of changes in or a result of your ISP's established policies or those of their routing partner(s). They are the ones establishing the parameters for how you get routed to Ormuco if connecting to Canada or to asianet/JPNIC if connecting to Japan. Your ISP sets the policy that determines which routing partner to use based on analytics run for the destination ISP, and the route used to get to that partner. Then that partner makes routing decisions based on their analytics. While either of those phases may be influenced by peering/transit agreements, those would be agreements made with the ISP's, and as such are by design influenced by their policies before any content provider's needs/wants should influence routing policy.
So, basically...it points back to the ISP's mostly, except under very limited circumstances. Things like malformed data packets or something like not including a proper flag in the headers that results in shaping rules of an ISP delaying/dropping packets due to congestion. Which can still point back to that ISP because they have an issue with over utilization in general that they need to address outside of anything that SE may or may not be doing with their data.
-
Thx for the answer, Raist
I tryed connecting from 3 diffirent proveders. The route was nealy same every time (exept for first hops ofcourse). And also as you can see at first traceroute. I succesfully get to japan network and after that the big change.
12 40 ms 37 ms 37 ms 118.155.197.178
inetnum: 118.152.0.0 - 118.159.255.255
netname: KDDI
descr: KDDI CORPORATION
descr: Garden Air Tower,3-10-10,Iidabashi,Chiyoda-ku,Tokyo,102-8460,Japan
13 236 ms 236 ms 247 ms 106.187.28.198
inetnum: 106.128.0.0 - 106.191.255.255
netname: KDDI
descr: KDDI CORPORATION
descr: GARDEN AIR TOWER,3-10-10,Iidabashi,Chiyoda-ku,Tokyo
Both are registered for 1 company. Should be some more description for such a process
-