connection errors

[fawlgaiy]

i am having the same friggen issue since 8am est this morning. i tried everything like all of you. i also was given the same copy paste blame everyone else from the chat support. i heard or read somewhere that connecting via vpn can be a band aid on the problem. this is true although the current vpn is connected through the Netherlands. it's also a free vpn called proton so not sure if that is helpful. i wouldn't want to pay for a vpn for a game i already pay to play so that is why i tried this free one.

Thanks a lot for also confirming a VPN is a potential option. This just tells me there's further evidence of it not being a user-end error (I doubt everyone posting in this thread is on the same ISP, for example).

Personally, I finally had the opportunity to cycle the router/modem as one of the few options I have yet to try and still no luck. Hoping we hear some sort of confirmation this is being looked into soon...

[Raba_Robo]

indeed, i also decided to try a little idea. i then switched from the netherlands to a usa vpn on proton. i wasn't able to connect though until the 3rd try. after that i disconnected from the vpn and tried to reconnect. however i should state that i first logged out to the character selection screen first before i disconnected from the vpn service.
once i was disconnected from the vpn i then tried to reconnect to my character on malboro. it only took one try but i was surprised i was on! i am still on and waiting in queue for heaven on high. i don't know why this worked but here i am. maybe this will work for some or all of you? this has to be an issue on SE's side for sure as most of you postulated.

[Strider_xiii]

Same issue with me, I was playing ffxiv on the steam deck around 2am eastern when it booted me out of a trust run. I couldn't log back in. This morning I logged in on my laptop, was booted off shortly after and again I can't get to the character select screen. Tried all afternoon and nothing. I work 2 hours away from where I live, tried there on the deck and it worked. Get back home to nj and same issue. I've reset my router and have a solid 450mb connection but can't get in.

[GuthriesGuitar]

Still happening for me, even in the early morning when traffic should be low.

[Sensus]

Still a problem... @Square please fix your game.

[Hav3nsblade]

Still a problem right now. JPN connects just fine. NA/EU is barely connecting. If I get past error 2002 logging into the data center, then I have to fight the possible 90002 error when actually getting into the game.

Also NA Eastern here and Optimum customer

[GuthriesGuitar]

I emailed support and they told me it's an ISP problem and that there's nothing they can do. Not really sure what there is to do besides run a VPN, which is baffling and frustrating.

[YakuzaKiryu]

Adding myself here as I have had this issue since 6AM EST yesterday- as of 8:58AM EST I still cannot log in I get either 90002, 2002, or 10105 errors.

I have done dnsflush, replace and renewed my IP and I still cannot log onto NA, OCE. EU and JP are fine however. I have tried everything and I couldn’t raid yesterday so we cancelled.

I wish SE would fix this man.

[Vicious915]

I’m also having this issue since early yesterday morning when congestion is normally low. I too can connect to JP and EU data centers no problem. It’s connecting to the NA servers that is the issue; today I’m no longer able to connect to the Oceania servers whereas yesterday I was able to. Eventually I can connect to the NA data center and play the game which runs fine despite it telling me my connection is “Poor”. Once I log out it’s back to countless 2002 errors and on the rare occasion the 10105 error. The support rep who responded to my reply was most unhelpful and provided a link and told me to post here. So here I am posting hoping to give this issue more traction so it can fixed ASAP. I’m on PS5 so I unfortunately have no diagnostics to report. And I’m also in the Northeast and an Optimum customer.

[DDRDiesel]

Reporting back to say this issue still persists as of 9:00 AM EST. Running the commands I mentioned previously seems to help, but it's still a roll of the dice from what I can see. Using the information below, I'll post the ping and tracert results

As per Square's page for reporting lag issues:
IP addresses for each of the physical data centers are as follows:
Japan: 124.150.157.15 (traceroute 124.150.157.15)
North America: 204.2.29.122 (traceroute 204.2.29.122)
Europe: 80.239.145.101 (traceroute 80.239.145.101)
Oceania: 153.254.80.65 (traceroute 153.254.80.65)
-----------------------
-----------------------
JP ping:
Pinging 124.150.157.15 with 32 bytes of data:
Reply from 124.150.157.15: bytes=32 time=185ms TTL=43
Reply from 124.150.157.15: bytes=32 time=179ms TTL=43
Reply from 124.150.157.15: bytes=32 time=179ms TTL=43
Reply from 124.150.157.15: bytes=32 time=178ms TTL=43

Ping statistics for 124.150.157.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 185ms, Average = 180ms
-----------------------
JP tracert:
Tracing route to 124.150.157.15 over a maximum of 20 hops

4 7 ms 4 ms 4 ms 451be0fc.cst.lightpath.net [65.19.99.252]
5 4 ms 3 ms 4 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42]
6 6 ms 4 ms 3 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
7 4 ms 4 ms 5 ms nyk-bb2-link.ip.twelve99.net [62.115.143.12]
8 76 ms 76 ms 75 ms sjo-b23-link.ip.twelve99.net [62.115.119.229]
9 182 ms 182 ms 181 ms tky-b2-link.ip.twelve99.net [62.115.123.141]
10 179 ms 180 ms 179 ms squareenix-ic-371309.ip.twelve99-cust.net [62.115.38.91]
11 178 ms 178 ms 181 ms 219.117.144.118
12 180 ms 179 ms 180 ms 219.117.144.45
13 177 ms 180 ms 177 ms 219.117.144.29
14 180 ms * 180 ms 219.117.147.182
15 178 ms 179 ms 180 ms 124.150.157.15

Trace complete.
-----------------------
NA ping:
Pinging 204.2.29.122 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 204.2.29.122:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
-----------------------
NA tracert:
Tracing route to 204.2.29.122 over a maximum of 20 hops

4 4 ms 4 ms 4 ms 65.19.100.4
5 3 ms 3 ms 3 ms 64.15.5.80
6 4 ms 3 ms 3 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
7 8 ms 6 ms 5 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
8 4 ms 4 ms 5 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
9 * * * Request timed out.
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.

Trace complete.
-----------------------
EU ping:
Pinging 80.239.145.101 with 32 bytes of data:
Reply from 80.239.145.101: bytes=32 time=93ms TTL=50
Reply from 80.239.145.101: bytes=32 time=89ms TTL=50
Reply from 80.239.145.101: bytes=32 time=89ms TTL=50
Reply from 80.239.145.101: bytes=32 time=91ms TTL=50

Ping statistics for 80.239.145.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 93ms, Average = 90ms
-----------------------
EU tracert:
Tracing route to 80.239.145.101 over a maximum of 20 hops

4 6 ms 4 ms 4 ms 64.15.4.58
5 6 ms 4 ms 12 ms 64.15.0.80
6 7 ms 3 ms 4 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
7 7 ms 4 ms 8 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
8 * * * Request timed out.
9 86 ms 85 ms 84 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
10 92 ms 97 ms * ffm-bb2-link.ip.twelve99.net [62.115.122.139]
11 91 ms 93 ms 90 ms ffm-b11-link.ip.twelve99.net [62.115.124.119]
12 90 ms 88 ms 90 ms squareenix-ic-369631.ip.twelve99-cust.net [80.239.195.85]
13 90 ms * * 80.239.145.241
14 90 ms 90 ms 90 ms 80.239.145.101

Trace complete.
-----------------------
OCE ping:
Pinging 153.254.80.65 with 32 bytes of data:
Reply from 153.254.80.65: bytes=32 time=213ms TTL=236
Reply from 153.254.80.65: bytes=32 time=213ms TTL=236
Reply from 153.254.80.65: bytes=32 time=214ms TTL=236
Reply from 153.254.80.65: bytes=32 time=216ms TTL=236

Ping statistics for 153.254.80.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 216ms, Average = 214ms
-----------------------
OCE tracert:
Tracing route to 153.254.80.65 over a maximum of 20 hops

4 6 ms 4 ms 6 ms 64.15.4.56
5 6 ms 3 ms 3 ms 451be0ce.cst.lightpath.net [65.19.120.206]
6 5 ms 4 ms 3 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
7 6 ms 4 ms 5 ms nyk-bb1-link.ip.twelve99.net [62.115.143.10]
8 7 ms 4 ms 4 ms nyk-b1-link.ip.twelve99.net [62.115.135.131]
9 20 ms 7 ms 4 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
10 8 ms 4 ms 5 ms ae-16.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
11 23 ms 24 ms 16 ms ae-3.r25.asbnva02.us.bb.gin.ntt.net [129.250.6.116]
12 72 ms 78 ms 71 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
13 74 ms 71 ms 72 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
14 217 ms 214 ms 214 ms ae-5.r20.sydnau05.au.bb.gin.ntt.net [129.250.2.53]
15 216 ms 215 ms 215 ms ae-3.a00.sydnau06.au.bb.gin.ntt.net [129.250.4.28]
16 213 ms 216 ms 215 ms 199.245.24.25
17 215 ms 212 ms 213 ms 153.254.80.65

Trace complete.
-----------------------

I don't really know what else can be added to the thread with regards to significance. This isn't an ISP issue, nor is it a simple "Fix your internet at home" problem. The copy/paste responses from SE are getting stale. This is very obviously an issue with the routing from East Coast to the physical datacenter location, specifically right after the 8th hop listed above (nyk-b1-link.ip.twelve99.net [62.115.135.131]). That node itself most likely isn't the problem, it's whatever node is supposed to follow that hop that's either down, faulty, or otherwise problematic. Although this may not be an issue that Square can personally resolve, they most certainly have a responsibility to reach out to their NA providers to at least see if an investigation can take place at the node and fix the problem