Like Ostheim89, I was able to get a sprout alt logged in briefly and thought that meant the issue was resolved, but it's right back to 2002, 10105, and 90002 errors again after I went back to trying my main character.
Ran my own trace route, used the info provided in this lodestone post: https://na.finalfantasyxiv.com/lodes...a451d5a8daa66f
(this post shows the NA address as 204.2.29.112, with a note that it was updated April 3, 2023)
Also ran the same as others in this thread, to 204.2.29.70:Tracing route to 204.2.29.122 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 9 ms 11 ms 67.59.237.89
4 11 ms 12 ms 18 ms opti37-8.nassau.cv.net [167.206.37.8]
5 14 ms 12 ms 11 ms 451be0fc.cst.lightpath.net [65.19.99.252]
6 11 ms 26 ms 12 ms 64.15.1.88
7 12 ms 12 ms 13 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 11 ms 13 ms 12 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
9 11 ms 13 ms 12 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
10 13 ms 14 ms 16 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 592 ms 20 ms 14 ms ae-16.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 34 ms 37 ms 37 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 34 ms 33 ms 32 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
14 * 81 ms 88 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
15 93 ms 82 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 84 ms 85 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 82 ms * * 204.2.29.241
18 81 ms 81 ms 81 ms 204.2.29.122
Trace complete.
2:53 PM Eastern update: I WON THE LOG-IN GAMBLE. Just kept trying and eventually hit a stretch with no server disconnects I guess!Tracing route to 204.2.29.70 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 8 ms 9 ms 67.59.237.89
4 10 ms 10 ms 13 ms opti37-10.nassau.cv.net [167.206.37.10]
5 11 ms 13 ms 11 ms 451be0fe.cst.lightpath.net [65.19.99.254]
6 11 ms 11 ms 11 ms 64.15.1.88
7 11 ms 11 ms 12 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 11 ms 15 ms 11 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
9 14 ms 12 ms 12 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
10 11 ms 13 ms 14 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 15 ms 13 ms 13 ms ae-16.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 34 ms 43 ms 38 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 45 ms 35 ms 39 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
14 * * 80 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
15 83 ms 97 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 93 ms 89 ms 84 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * 84 ms 204.2.29.241
18 85 ms 87 ms 85 ms 204.2.29.70
Trace complete.
Sure hope there is some formal/official post sometime soon about this issue since it's been going on for over 10 hours by some reports!!