Repeated 90k error

[JamesDevice]

Just further proves the point I made earlier. If a VPN/Proxy service resolves the problem, then it is a problem in route to the servers. Things are the same at both your local and ending network segments--what you've changed is how your data is handled in route between the two.





If you are tracing to an iWeb address, then you aren't tracing to the FFXIV servers. It sounds like you are making the same mistake I see on here a lot and are tracing to the www.eidos.com web server (184.107.107176...go ahead and ping or do an nslookup on the URL if you don't believe me). That server is NOT connected to this game, is physically in a different section of Montreal, hosted on someone else's network (XIV is on Ormuco, and not iWeb), and you take a different route to get there. You need to test against the IP your client actually uses. For Canada, it should start with 199.

I traced the foreign IP of the TCP connection the ffxiv.exe process (PID 4760) on my windows machine has connected according to netstat -n -o:

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    127.0.0.1:49810        127.0.0.1:49811        ESTABLISHED     2900
  TCP    127.0.0.1:49811        127.0.0.1:49810        ESTABLISHED     2900
  TCP    192.168.0.13:52629     195.145.147.91:80      TIME_WAIT       0
  TCP    192.168.0.13:52630     195.145.147.91:80      TIME_WAIT       0
  TCP    192.168.0.13:52637     173.194.113.97:80      TIME_WAIT       0
  TCP    192.168.0.13:52638     173.194.113.97:80      TIME_WAIT       0
  TCP    192.168.0.13:52639     173.194.113.97:80      TIME_WAIT       0
  TCP    192.168.0.13:52646     62.159.74.59:80        TIME_WAIT       0
  TCP    192.168.0.13:52647     62.159.74.59:80        TIME_WAIT       0
  TCP    192.168.0.13:52652     62.159.74.8:80         TIME_WAIT       0
  TCP    192.168.0.13:52659     199.91.189.106:54994   TIME_WAIT       0
  TCP    192.168.0.13:52660     199.91.189.145:54992   ESTABLISHED     4760
  TCP    192.168.0.13:52661     199.91.189.145:54992   ESTABLISHED     4760

The complete route was:

Host Information
1, -------------- ,192.168.0.253
2, -------------- ,217.0.117.77
3, -------------- ,87.190.188.202
4, -------------- ,217.239.48.170
5,xe-11-0-1.fra29.ip4.gtt.net,141.136.101.233
6,xe-4-2-0.mtl10.ip4.gtt.net,141.136.107.125
7,ormuco-gw.ip4.gtt.net,216.221.156.110
8, -------------- ,192.34.76.2
9, -------------- ,199.91.189.234
10, -------------- ,199.91.189.145

So I think the route I checked is actually the route to their data center servers.

Update: I now have massive packet loss on all hops starting in the gtt network up to the SE server IP.