connection errors

[mariannef]

early this morning ( eastern time around 4am or so), I got disconnected from Balmung

tried again, got 2002, did the usual at my end without success. Later ( after a brief nap) I tried again several time on different NA data centers, no luck. Then switching to a European one it worked just fine.

Looks like some network server between me and the data center died, here's the tracerts with my own ip address removed
(North America first , then a Euro one)


tracert 204.2.29.70

Tracing route to 204.2.29.70 over a maximum of 30 hops


5 12 ms 12 ms 12 ms 64.15.7.71
6 11 ms 12 ms 15 ms 451be0d2.cst.lightpath.net [65.19.120.210]
7 15 ms 12 ms 14 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 12 ms 14 ms 16 ms nyk-bb2-link.ip.twelve99.net [62.115.143.12]
9 12 ms 12 ms 11 ms nyk-b1-link.ip.twelve99.net [62.115.135.133]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

tracert 80.239.145.79

Tracing route to 80.239.145.79 over a maximum of 30 hops


5 10 ms 11 ms 11 ms 64.15.7.188
6 11 ms 19 ms 11 ms rtr1-tg10-1.mhe.prnynj.cv.net [64.15.6.2]
7 10 ms 11 ms 11 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 12 ms 21 ms 10 ms nyk-bb2-link.ip.twelve99.net [62.115.143.12]
9 85 ms 87 ms 87 ms ldn-bb1-link.ip.twelve99.net [62.115.113.21]
10 90 ms 91 ms 91 ms prs-bb1-link.ip.twelve99.net [62.115.135.25]
11 102 ms 103 ms 101 ms ffm-bb1-link.ip.twelve99.net [62.115.123.12]
12 100 ms 99 ms 99 ms ffm-b11-link.ip.twelve99.net [62.115.124.117]
13 113 ms 97 ms 97 ms squareenix-ic-369631.ip.twelve99-cust.net [80.23
9.195.85]
14 97 ms * 99 ms 80.239.145.241
15 98 ms 99 ms 96 ms 80.239.145.79

Trace complete.

[DDRDiesel]

Can confirm the same errors are happening to me. Attempting to login to any character gave me issues. At times couldn't even get to the character select screen. 90k and 2002 errors all morning. Currently running a repair as I thought that was part of the problem, but now I'm seeing the same results with ping and tracert. NA datacenters immediately time out, but JP/OCE datacenters work fine

EDIT: Using the most up-to-date IP addresses for the datacenters, I'm able to reach OCE and JP, but EU/NA datacenters are unavailable.

Ping stats to JP
Pinging 124.150.157.157 with 32 bytes of data:
Reply from 124.150.157.157: bytes=32 time=179ms TTL=43
Reply from 124.150.157.157: bytes=32 time=178ms TTL=43
Reply from 124.150.157.157: bytes=32 time=178ms TTL=43
Reply from 124.150.157.157: bytes=32 time=177ms TTL=43

Ping to OCE
Pinging 153.254.80.103 with 32 bytes of data:
Reply from 153.254.80.103: bytes=32 time=214ms TTL=44
Reply from 153.254.80.103: bytes=32 time=212ms TTL=44
Reply from 153.254.80.103: bytes=32 time=212ms TTL=44
Reply from 153.254.80.103: bytes=32 time=214ms TTL=44

Tracert to NA servers (Aether IP used, first three hops omitted for security)

Tracing route to 204.2.229.9 over a maximum of 30 hops
--
4 15 ms 4 ms 4 ms 64.15.4.76
5 4 ms 3 ms 3 ms 64.15.1.88
6 6 ms 3 ms 3 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
7 4 ms 4 ms 4 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
8 5 ms 4 ms 4 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
9 16 ms 7 ms 12 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

tracert to EU servers (Chaos datacenter used, first three hops omitted for security)

Tracing route to 192-82-50-9.static.ezlink.com [192.82.50.9]
over a maximum of 20 hops:
--
4 4 ms 4 ms 4 ms 64.15.5.142
5 4 ms 3 ms 3 ms 451be0c2.cst.lightpath.net [65.19.120.194]
6 3 ms 3 ms 4 ms be6061.ccr31.jfk04.atlas.cogentco.com [38.88.195.97]
7 5 ms 4 ms 4 ms be3363.ccr42.jfk02.atlas.cogentco.com [154.54.3.125]
8 58 ms 17 ms 16 ms be2890.ccr22.cle04.atlas.cogentco.com [154.54.82.245]
9 22 ms 23 ms 21 ms be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
10 34 ms 34 ms 34 ms be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169]
11 45 ms 45 ms 45 ms be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
12 45 ms 47 ms 47 ms be2402.rcr21.b006467-6.den01.atlas.cogentco.com [154.54.88.46]
13 45 ms 45 ms 46 ms be2259.nr51.b006467-5.den01.atlas.cogentco.com [154.24.32.34]
14 45 ms 47 ms 54 ms 38.32.95.10
15 49 ms 49 ms 49 ms 199.192.70.15
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

[NaiaLalita]

I'm also running into server connection issues this morning.
I tested connection to every available datacenter.

Aether, Crystal, and Oceania are returning constant 2002 errors.

I was able to connect without issue to all other datacenters.

Unfortunately, my character I'd like to play with is on Aether. Which seems to be inaccessible unless you're already logged in right now.

[CrispyChicken]

Same here, not able to connect to my main character in Leviathan, showing 2002 error. I tried EU servers and they are fine.

[NaiaLalita]

I am kicking myself for logging out of my Primal alt. I went away to cook lunch for an hour, and now I am no longer able to connect to Primal, either. I'd figured if I couldn't get to my raid craft orders on my main, I could at least go do some side content on my alt. But nope! Zero access to any of my characters now.

[GuthriesGuitar]

Also happened to me. Haven't been able to play for a few days. Tracert reaches a ntt.net node and then times out the rest of the way.

[Fox_Pocket]

I'm having the same issue, have not been able to connect to a US data center since around 4AM this morning.

Can connect to Euro and JP one fine though.

[wizisi2k]

I went to login today to the same 2002 errors listed above. It seems there may be a outage since there's a common problem with a couple posts of hop 9 being the last reachable IP. I also confirm the same issue. Oddly, initially I had the game running at character login screen. I WAS able to login but it would error me out to the start screen and loop the issue whenever I tried to select a character. Here's my tracert to the NA lobby server of 204.2.29.70 (I think I stopped it at 28/30 but the jist should be visible):
4 13 ms 11 ms 10 ms ool-4353fa16.dyn.optonline.net [67.83.250.22]
5 12 ms 13 ms 13 ms 64.15.7.71
6 13 ms 14 ms 12 ms 451be0d2.cst.lightpath.net [65.19.120.210]
7 13 ms 18 ms 16 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 11 ms 10 ms 11 ms nyk-bb2-link.ip.twelve99.net [62.115.143.12]
9 13 ms 14 ms 74 ms nyk-b1-link.ip.twelve99.net [62.115.135.133]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.

Oddly, just after posting this, I was able to login to my main character so it may be resolved.

[Ostheim89]

Reporting in that I'm having the same issue, with similar results when running a trace. I was able to log in with an alt (though I logged out after to try my main and couldn't connect to the DC), and able to log into a European DC. East coast, if that helps.

[NaiaLalita]

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)

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.

Also ran the same as others in this thread, to 204.2.29.70:

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.

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!
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!!