Connection issues

[Taika]

Hello!

I'm experiencing severe connection issues which have been going on for over 6 hours now. Earlier today I got a couple of R0s and disconnects from the game but around 6 hours ago (3:30 pm GMT) I disconnected from the game completely and wasn't able to get back in. Tracert traceip showed me this (sorry about the foreign language):



And here are the different error messages I've been getting:









In addition to problems with connecting to the game, I'm also having problems connecting to the Lodestone site and forums and Square Enix Support Centre site.

Why don't you let me connect your servers.

[vax]

I had the same problem, but now the game and lodestone are working w/o problem.

[Taika]

Same issue happening right now again (5:20 pm GMT).

Also:

[vax]

Yes, i'm having the same problem now and two friends too. One of them the saturday when i couldn't log he was playing w/o problem.

[Taika]

Yes, i'm having the same problem now and two friends too. One of them the saturday when i couldn't log he was playing w/o problem.

Thanks for posting, I guess this is "good" to know in the way that it's even more likely an issue on SE's side.

May I ask if you and the other people having the same issue are from the same country or from EU?

[vax]

We're 3 people from Argentina and one from Chile.

[Taika]

Thanks for the info! We're from Finland. Not limited to one country then.

Edit: Can't believe I messed up like this, sorry! Was thinking about "non-JP" and "non-NA" meaning "other" areas but typed EU...

[vax]

Argentina and Chile are from South America .

[Aistalia]

I have the same problem, but on a smaller scale. I can actually log ingame but it takes ages to properly load lodestone.
It happens on all my network (even on phones and tablets) so you don't really need my computer specifications.
I guess a routing issue between japanese nodes and EU ISPs?

My Provider is Telecom Italia, and this is a traceroute:

traceroute to traceip.ffxiv.com (202.67.52.81), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.266 ms 1.628 ms 0.810 ms
2 192.168.100.1 (192.168.100.1) 21.927 ms 24.626 ms 20.808 ms
3 172.17.145.141 (172.17.145.141) 21.238 ms 21.405 ms 20.743 ms
4 172.17.144.25 (172.17.144.25) 21.134 ms 22.349 ms 21.654 ms
5 172.17.9.161 (172.17.9.161) 29.263 ms 29.535 ms 27.712 ms
6 172.17.10.181 (172.17.10.181) 35.686 ms 35.721 ms 35.814 ms
7 172.17.10.69 (172.17.10.69) 39.963 ms 38.817 ms 39.277 ms
8 pos1-13-0-0.milano50.mil.seabone.net (93.186.128.97) 40.899 ms 40.127 ms 38.578 ms
9 te7-4.losangeles1.loa.seabone.net (89.221.35.146) 338.067 ms
te1-2.losangeles1.loa.seabone.net (89.221.35.128) 211.676 ms
te7-4.losangeles1.loa.seabone.net (89.221.35.146) 216.663 ms
10 pacnet.losangeles1.loa.seabone.net (89.221.35.186) 213.022 ms * *
11 po15-1-1.cr1.nrt1.asianetcom.net (202.147.61.186) 350.426 ms 327.816 ms 566.705 ms
12 * gi1-0-0.gw1.nrt5.asianetcom.net (202.147.0.178) 528.401 ms *
13 squareco.asianetcom.net (203.192.149.210) 528.059 ms * 358.282 ms
14 61.195.56.129 (61.195.56.129) 614.373 ms * 336.556 ms
15 * * 219.117.144.2 (219.117.144.2) 389.137 ms
16 * 219.117.146.149 (219.117.146.149) 527.721 ms *
17 219.117.146.129 (219.117.146.129) 350.342 ms 473.707 ms 614.177 ms
18 * 219.117.146.46 (219.117.146.46) 528.409 ms
219.117.146.38 (219.117.146.38) 327.798 ms
19 202.67.52.81 (202.67.52.81) 613.817 ms 616.298 ms 612.019 ms

Have fun.

[Shokun]

I just actually realized, when I was checking your traceroutes and comparing it to mine, your connections are routed through different line in NA than what my are.

Here's a traceroute from connection/computer that CAN log in to game:

Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 30 hops:

1 17 ms 3 ms 3 ms 78-27-64-2.bb.dnainternet.fi [78.27.64.2]
2 3 ms 23 ms 3 ms lah1-tr1.dnaip.fi [62.78.105.96]
3 12 ms 12 ms 12 ms hel5-tr3.dnaip.fi [62.78.107.126]
4 12 ms 12 ms 12 ms hel1-tr2.dnaip.fi [62.78.107.124]
5 13 ms 15 ms 14 ms hel2-tr1.dnaip.fi [62.78.107.9]
6 12 ms 13 ms 13 ms tuk2-tr1.dnaip.fi [62.78.107.57]
7 17 ms 22 ms 22 ms 10gigabitethernet1-3.core1.sto1.he.net [194.68.1
28.187]
8 37 ms 38 ms 48 ms 10gigabitethernet3-2.core1.ams1.he.net [72.52.92
.45]
9 45 ms 49 ms 47 ms 10gigabitethernet6-1.core1.lon1.he.net [184.105.
213.245]
10 115 ms 114 ms 111 ms 10gigabitethernet7-4.core1.nyc4.he.net [72.52.92
.241]
11 180 ms 177 ms 172 ms 10gigabitethernet5-3.core1.lax1.he.net [72.52.92
.226]
12 197 ms 203 ms 201 ms pacnet.10gigabitethernet2-3.core1.lax1.he.net [2
16.218.223.206]
13 299 ms 302 ms 304 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]

14 308 ms 317 ms 301 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 301 ms 300 ms 304 ms squareco.asianetcom.net [203.192.149.210]
16 312 ms 304 ms 305 ms 61.195.56.129
17 291 ms 295 ms 298 ms 219.117.144.2
18 295 ms 297 ms 298 ms 219.117.146.149
19 299 ms 300 ms 297 ms 219.117.146.129
20 300 ms 301 ms 302 ms 219.117.146.38
21 293 ms 308 ms 293 ms 202.67.52.81

Trace complete.

As you can see, your connections are using seabone to go through NA, I'm using core1. Could maybe be a problem somewhere in NA too? Seems like your timeouts start after entering NA networks.