Oh wow I didn't realize it was such a big issue, kinda sad tbh that this seems to be such a huge issue and evidently IS on Sqenix's side as from what I've seen here it's most often if not always the 11th hop that's registered to a IP that's related to Sqenix.. Big sad. Anyways, I can't delete the thread I created but I guess I can post some info here too at least.
Here's my TraceRT:
Code:
Tracing route to 195.82.50.9 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms xxx.xxx [192.168.x.x]
2 27 ms 14 ms 9 ms 83-169-x-x-X.x.de [83.169.x.x]
3 15 ms 9 ms 8 ms ipxxxxebd1.static.x-x.de [88.134.x.x]
4 12 ms 14 ms 14 ms 145.254.3.78
5 * * 9 ms 145.254.2.195
6 14 ms 19 ms 14 ms ae6-100-xcr2.fri.cw.net [195.89.100.33]
7 11 ms 54 ms 19 ms ae4-pcr1.fnt.cw.net [195.2.16.33]
8 21 ms 14 ms 15 ms telia-gw.fnt.cw.net [195.2.22.238]
9 17 ms 12 ms 22 ms ffm-bb2-link.ip.twelve99.net [62.115.124.118]
10 36 ms 11 ms 16 ms ffm-b1-link.ip.twelve99.net [62.115.121.7]
11 13 ms 17 ms 20 ms kddi-ic319844-ffm-b1.ip.twelve99-cust.net [62.115.32.106]
12 12 ms 10 ms 14 ms 195.82.61.14
13 * * 1329 ms 195.82.50.230
14 8 ms 14 ms 14 ms 195.82.50.9
x=removed due to possibly personal information, I dunno. better safe than sorry
Proof that the IP thats causing the time-outs SquareEnix related: