high latency at certain hours on Chaos data center

[KaguyaTempest]

Just wanted to drop in and report that this is still an issue that has yet to be resolved.

In my scenario 195.82.50.234 (the problem node) is the very last hop which means I can't go around it using a VPN.

This is a traceroute during the morning to neolobby06.ffxiv.com

traceroute to neolobby06.ffxiv.com (195.82.50.9), 64 hops max, 52 byte packets
1 ttrouter (192.168.1.1) 2.015 ms 1.114 ms 1.152 ms
2 ae50-ner002.msp.as13285.net (78.144.1.35) 6.091 ms 6.800 ms 125.954 ms
3 ae50-scr002-msp.as13285.net (78.144.1.34) 5.540 ms 5.777 ms 5.254 ms
4 ae63-scr102.loh.as13285.net (78.144.1.132) 12.064 ms 124.843 ms 126.209 ms
5 ae7.cr10-lon2.ip4.gtt.net (87.119.122.225) 14.014 ms 13.251 ms 13.584 ms
6 ae18.cr11-lon2.ip4.gtt.net (89.149.141.213) 11.679 ms 124.995 ms 11.822 ms
7 ldn-b2-link.ip.twelve99.net (62.115.47.218) 12.168 ms 12.579 ms 14.887 ms
8 ldn-bb4-link.ip.twelve99.net (62.115.120.238) 143.217 ms 14.706 ms
ldn-bb1-link.ip.twelve99.net (62.115.122.188) 12.438 ms
9 * prs-bb2-link.ip.twelve99.net (62.115.133.239) 27.638 ms
prs-bb2-link.ip.twelve99.net (62.115.114.229) 26.279 ms
10 ffm-bb1-link.ip.twelve99.net (62.115.123.12) 25.440 ms 25.000 ms 26.044 ms
11 ffm-b1-link.ip.twelve99.net (62.115.121.1) 25.165 ms
ffm-b1-link.ip.twelve99.net (62.115.121.7) 26.100 ms 26.115 ms
12 kddi-ic301630-ffm-b10.ip.twelve99-cust.net (62.115.32.110) 24.955 ms 24.926 ms 25.709 ms
13 195.82.60.29 (195.82.60.29) 25.684 ms
195.82.61.14 (195.82.61.14) 26.036 ms 26.399 ms
14 195.82.50.234 (195.82.50.234) 24.911 ms 24.960 ms
195.82.61.14 (195.82.61.14) 26.694 ms
15 195.82.50.234 (195.82.50.234) 25.819 ms 26.273 ms 26.218 ms

Trace route during the evening

traceroute to neolobby06.ffxiv.com (195.82.50.9), 64 hops max, 52 byte packets
1 ttrouter (192.168.1.1) 2.302 ms 1.543 ms 1.700 ms
2 ae50-ner002.msp.as13285.net (78.144.1.35) 5.898 ms 5.708 ms 5.668 ms
3 ae50-scr002-msp.as13285.net (78.144.1.34) 6.594 ms 6.679 ms 6.477 ms
4 ae63-scr102.loh.as13285.net (78.144.1.132) 15.785 ms 11.989 ms 22.763 ms
5 ae7.cr10-lon2.ip4.gtt.net (87.119.122.225) 40.650 ms 16.417 ms 11.933 ms
6 ae18.cr11-lon2.ip4.gtt.net (89.149.141.213) 35.134 ms 19.566 ms 27.310 ms
7 ldn-b2-link.ip.twelve99.net (62.115.47.218) 12.369 ms 12.051 ms 12.528 ms
8 ldn-bb4-link.ip.twelve99.net (62.115.120.238) 12.013 ms 12.944 ms
ldn-bb1-link.ip.twelve99.net (62.115.122.188) 12.181 ms
9 prs-bb1-link.ip.twelve99.net (62.115.135.25) 25.105 ms
prs-bb2-link.ip.twelve99.net (62.115.114.229) 25.602 ms 26.053 ms
10 ffm-bb1-link.ip.twelve99.net (62.115.123.12) 24.996 ms 25.382 ms 25.042 ms
11 ffm-b10-link.ip.twelve99.net (62.115.137.227) 24.855 ms
ffm-b10-link.ip.twelve99.net (62.115.137.211) 29.949 ms 25.393 ms
12 kddi-ic319844-ffm-b1.ip.twelve99-cust.net (62.115.32.106) 24.799 ms 24.944 ms 25.324 ms
13 195.82.61.14 (195.82.61.14) 25.126 ms
195.82.60.29 (195.82.60.29) 29.577 ms 25.526 ms
14 195.82.61.14 (195.82.61.14) 24.792 ms 24.541 ms
195.82.50.234 (195.82.50.234) 1358.122 ms

Please look into this, this isn't something we can fix by just contacting our ISPs