90002 error every 56 minutes. Has anyone managed to fix it or did all quit?

So recently I've noticed this error has started to not as random as before in frequency so I decided to time it.

4 out of 4 times I got the 90002 error 56 minutes after loggin in on the dot.

I have done all I can with my ISP,they have checked the the route with the correct server IP address I gave them and they said there are no problems to be found>

I have forwarded all needed ports on my modem,tried turning the anti virus off,tried playing with UPNP on/off on both game and modem and I still get this error like clockwork.

I also replaced my modem with a brand new one and I will be replacing all cables this week (I am hard wired to the modem).

Honestly as much as this error means the problem lies on the client side,I have entertained all possibilities that it could be on my end but there is nothing more to be done.My ISP has found nothing and blames Square Enix servers and Square Enix keeps blaming my ISP.

I see a lot of posts about ppl with this error but not a single post of someone managing to fix it with their ISP yet some ppl insist that SE is not to blame at all and that it has to be the client side.

My question would be this:

If the client side is always to blame for this error and all you need is your ISP to use a different route or fix the route,how come I don't see 1 single post on the Internet of someone saying they managed to fix it?

For anyone willing to make sense of my tracert (since SE doesn't seem to care) here:

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 12 ms 12 ms 10.1.11.1
4 13 ms 12 ms 12 ms 10.1.0.129
5 16 ms 12 ms 12 ms 10.1.0.18
6 14 ms 12 ms 12 ms 10.1.0.210
7 25 ms 14 ms 12 ms 213.140.51.249
8 57 ms 39 ms 33 ms xe-10-0-4-0-grtmiabr4.red.telefonica-wholesale.n
et [84.16.14.229]
9 36 ms 35 ms 35 ms Et-27-0-0-0-5-grtmiabr4.red.telefonica-wholesale
.net [84.16.15.131]
10 44 ms 49 ms 48 ms et2-0-0-0-grtmiana2.red.telefonica-wholesale.net
[84.16.14.189]
11 37 ms 38 ms 37 ms ix-11-2-0-0.tcore1.MLN-Miami.as6453.net [63.243.
152.49]
12 85 ms 85 ms 86 ms if-7-2.tcore1.AEQ-Ashburn.as6453.net [66.198.154
.177]
13 86 ms 84 ms 89 ms 64.86.85.1
14 85 ms 89 ms 88 ms 64.86.85.1
15 82 ms 83 ms 83 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.
33]
16 85 ms 82 ms 84 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2
5]
17 87 ms 88 ms 86 ms 66.198.96.50
18 87 ms 86 ms 88 ms 192.34.76.2
19 88 ms 89 ms 88 ms 192.34.76.2
20 88 ms 88 ms 88 ms 199.91.189.234
21 91 ms 90 ms 88 ms 199.91.189.74

Trace complete.

There isn't a fire showing up in your tracert, but there is some smoke. The trick is finding the spark that ignites the flame eventually. Not sure what/where you've been searching, but there have been posts here where people have gotten their ISP to resolve issues--as well as other forums like Reddit, Battle.net, host of other games. Telfonica has shown up at other game forums as well as having issues in the past. You're also dealing with TATA, which is far from immune to these problems either.

But, back to your posted tracert. As noted in one of your other threads, you have too much jitter at some hops. The telefonica segments are having some problems. Not necessarily game-breaking jitter, but with a range spiking to 2x within in a single tracert...there is very likely something there that wants to rear it's ugly head once in a while. Could be just enough to cause packets to get far enough out of sorts to drop your session. When packets are received out of order (or presumed lost), the protocol in play will have them retransmitted. If it causes a long enough delay, the server may drop your session. Otherwise, you start seeing micro-stutter, staggered responses, people/monsters skipping around on your screen as your connection is trying to play catch-up. You are also coming from Spain, which means you are getting crammed in some undersea cables in order to get to Canada. Doesn't take much to knock things out of whack when you have such limited routing issues. Once the servers get setup in the EU region, those may be a better choice for you to play on....should be considerably smoother routes to them.

You could try running some pathpings (pathping neolobby02.ffxiv.com) or some tests to some of the servers around the Montreal area over at www.pingtest.net to see how much your scores may vary over longer testing periods (pathping hits each hop 100 times, and pingtest.net runs something like 250 pings). Sometimes you just need a larger sample set to capture the spike that is causing trouble. You could even try an extended ping yourself with the -n switch ("ping neolobby02.ffxiv.com -n 100" will ping it 100 times).

Another thing you could do is try some of the free trials for VPN services. If using one of their tunnels clears up your connection, it's strong evidence your ISP has routing problems they need to look into. VPN's have multiple locations you tunnel to as an encrypted connection (bypasses shaping rules) along a more optimized route. Then you get routed as a normal connection from where you exit. So for example, you may tunnel to Washington DC on an encrypted line at 100ms, then exit from there and get routed to Montreal at 67-90ms from that point forward. Latency might be slightly higher, but it remains constant and makes the game more manageable. Effectively what you are doing with a VPN is changing the path you take--if things improve, it confirms your ISP needs to work on it's routes.

Edit: I just pinged 213.140.51.249 (Telefonica segment). In just 4 pings, it swung from 88 to 210. I'm under 40ms all the way from here in the US through to the exchange into Telefonica in Spain, and then it goes bad. That indicates there may be a localized congestion problem for Telefonica in Spain. Ran another 100 ping test and it ranged from 87 to 201, with an average of 98. Jitter is way too high at that one hop. This game runs on roughly a 300ms boundary. It won't take much of a spike elsewhere to stack on top of that one hop to cause issues with this game.