Frequent 90002 Error

[Raist]

Can someone make sense of this?

Tracing route to 191.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 49 ms 13 ms 10.1.11.1
4 12 ms 12 ms 12 ms 10.1.0.129
5 28 ms 15 ms 25 ms 10.1.0.18
6 11 ms 15 ms 24 ms 10.1.0.210
7 14 ms 12 ms 12 ms 213.140.51.249
8 38 ms 39 ms 35 ms Te0-6-0-0-grtmiabr6.red.telefonica-wholesale.net
[84.16.13.149]
9 * 36 ms * Et-27-0-0-0-5-grtmiabr4.red.telefonica-wholesale
.net [84.16.15.131]
10 41 ms 39 ms 35 ms Hu-0-11-0-0-grtmiana4.red.telefonica-wholesale.n
et [84.16.12.238]
11 32 ms 35 ms 36 ms ix-11-2-0-0.tcore1.MLN-Miami.as6453.net [63.243.
152.49]
12 126 ms 35 ms 42 ms ix-11-2-0-0.tcore1.MLN-Miami.as6453.net [63.243.
152.49]
13 157 ms 124 ms 122 ms 63.243.152.6
14 133 ms 121 ms 121 ms cable190-248-88-229.une.net.co [190.248.88.229]

15 * * * Request timed out.
16 * * * Request timed out.
17 3991 ms 1818 ms * 191.91.189.57
18 * * * Request timed out.
19 * 2135 ms 1083 ms 191.91.189.57

Trace complete.

At first glance, there's routing issues...but then I realized the IP you traced. It's not even the proper subnet...should start with 199. That address appears to be something down in Colombia, not Canada.

It looks like you meant to trace to 199.91.189.57? That is one of the IP's that seemed to be taken out of the pool when they changed things up with the 2.55 update (included infrastructure maintenance). Since then, a lot of us have noticed our assigned IP address has changed. Need to double check which one you are using with either netstat or resmon once you are logged fully into the game. Alternatively, you could use what appears to be the Aether lobby server address (neolobby02.ffxiv.com, which should resolve to 199.91.189.74).

Otherwise, there appears to be some issues along your route. Too much jitter and even signs of packet loss early on, and then there appears to be some heavy congestion/loss kicking in further down the line as well (colored the hops that look out of sorts). Once you confirm you have a proper IP address, if you still see the same kinds of things going on then you should contact your ISP to take a closer look at the route.