Connection issues

[vax]

Can play now. Fixed at the same time on saturday.

[Taika]

Same thing here. The problems lasted from 5:20pm GMT to 9:45pm GMT.

[vax]

Problem started again and i was crafting with HQ items D:.

But now a friend that had r0 early can play w/o a problem, but another and me have r0.
Now can play ffxi, there are some r0, but it's a little more playable than ffxiv.

[CycMarques]

I have the same exact problem and it's ongoing again at this time. Had it first time on 7th of July which sorted by itself in 6 hours or so. Connection went back to normal and went out again yesterday for few hours. Came back and dropped off again just hour into playing.

I can't connect into the game and any Square Enix site is really sluggish to load (I'm amazed if I succeed posting this). I'm located in Finland, but what's funny there are some swedish LS mates of mine who don't have any problems with this. My connection too travels through loa.seabone.net as does the starter of this topic.

I assume SE can't really do anything about this 'cause the problem is somewhere in mid-Kansas?

[Aistalia]

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.

Yeah, looks like the problem is on the "jump" between NA nodes and Japan. Now (7.17 GMT) lodestone still loads very slowly.

[Taika]

Unable to log in again (8:30 am GMT now). I don't know where the problem is but if this keeps happening I simply can't continue playing the game. I contacted SE support through Square Enix Support Centre but haven't received an answer yet.

Vax: Could you post your tracert results to see if your connection is going through the same route than ours? Here are the instructions:

How to obtain tracert results:

1. Run cmd.exe or command.exe
   If you are using Windows XP, Vista, or Windows 7:
   Select Start > All Programs > Accessories > Command Prompt
2. Type the command "tracert traceip.ffxiv.com" (without quotes) on Command Prompt and press Enter.
3. Copy and paste a tracert result.

1. Click the "Command Prompt" icon located at the title bar to open a menu. Select Edit > Mark.
2. Mark the tracert result in Command Prompt (from “Tracing route to...” to “Tracing complete.”). Click the icon again to select Edit > Copy.
3. Paste the result in your reply.

[vax]

Here is the result, same things.

Traza a la dirección traceip.ffxiv.com [202.67.52.81]
sobre un máximo de 30 saltos:

1 * * * Tiempo de espera agotado para esta solicitud.
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 20 ms 11 ms 23 ms 173-165-89-200.fibertel.com.ar [200.89.165.173]

5 13 ms 15 ms 15 ms 130-165-89-200.fibertel.com.ar [200.89.165.130]

6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 15 ms 11 ms 11 ms 213-164-89-200.fibertel.com.ar [200.89.164.213]

9 19 ms 11 ms 23 ms 222-165-89-200.fibertel.com.ar [200.89.165.222]

10 13 ms 12 ms 12 ms te4-3.baires3.bai.seabone.net [195.22.220.117]
11 232 ms 233 ms 233 ms te1-1.losangeles1.loa.seabone.net [89.221.40.131
]
12 211 ms * * pacnet.losangeles1.loa.seabone.net [89.221.35.18
6]
13 325 ms * 324 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

14 306 ms * 307 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 * * 318 ms squareco.asianetcom.net [203.192.149.210]
16 310 ms 310 ms 310 ms 61.195.56.129
17 315 ms 316 ms 316 ms 219.117.144.2
18 * 328 ms 329 ms 219.117.146.149
19 317 ms 316 ms * 219.117.146.129
20 * * 320 ms 219.117.146.38
21 * * * Tiempo de espera agotado para esta solicitud.
22 326 ms 325 ms 326 ms 202.67.52.81

Traza completa.

[Taika]

I got an answer from the Square Enix Support Centre:

We understand that you have a problem with connecting to our servers as we were doing some maintenance work on them.

However, we think that this issue should be solved by now. If this problem still occurs for you, please do not hesitate to contact us via phone or chat Monday to Friday 09:00 – 18:00.

So hopefully the issue is fixed now and won't happen again. However, I wish they would let us know about these maintenances and the possibility of connection issues in the future.

[Nayito]

I had this same problem too, same times and all, and it would be nice if SE would let us know that some of the player base was gonna be having problems with connection. on sat i reinstall the game, and last night i was about to do the same with windows. Is it that hard to let ppl know, we won't hate or wuit if you are doing a maint on some servers, leaving me in dark and trying to fix something that wasn't my problem makes me very angry and makes me wanna quit. So if anyone from SE is reading this plz have that in mind next time you have to do maintenance on some of your servers.


PD Vax, yo tambien soy de Argentina. En que server estas? yo estoy en Gugnir

[Taika]

I had this same problem too, same times and all, and it would be nice if SE would let us know that some of the player base was gonna be having problems with connection. on sat i reinstall the game, and last night i was about to do the same with windows. Is it that hard to let ppl know, we won't hate or wuit if you are doing a maint on some servers, leaving me in dark and trying to fix something that wasn't my problem makes me very angry and makes me wanna quit. So if anyone from SE is reading this plz have that in mind next time you have to do maintenance on some of your servers.

Yes I agree. It would have been just fine if I had known there might be some connection issues. But what happened was we scheduled a CC run for Saturday. We weren't able to log in and had to reschedule the run for Monday. Then the same thing happened again, right as we were entering.

The way SE handled this caused a lot of frustration to all the players experiencing the issue and the groups those people were playing with. It all could have been avoided with a simple announcement of server maintenance and possible connection issues.