Lag Spikes // 90k Error // Log-in issues // Black screen // Error booting etc.

[Raist]

The problem potentially affected everyone because the two regions communicate to each other in the background as well. Note that it also states specifically communication between the data centers, not just the clients to the JP datacenter. Your client periodically communicates with a JP server as well. Granted, the client may only communicate with the JP server in small instances or bursts (like maybe an authentication when zoning, when you use Duty finder, etc.). But it does try to maintain a connection to a JP server as well, even though it is mainly using the NA/EU servers. So it may have directly affected NA/EU clients if that secondary connection was unstable.

The point was the poster was asking for details about the networking issues, and there was a recent announcement about an issue they identified, worked on, and eventually resolved. They had something definitive they could pass along, so they did. SE is very cautious about posting on issues... always have been very tight-lipped.

As for your ping and tracert coming up "normal", it may have been normal in that particular instance. Timing is more critical with tracert if you are just running it once--need to hit it right when you know the connection is flaking out. Sometimes you have to run them repeatedly to catch the odd timeout or ramped up delay. Remember, a tracert is only 3 quickpings per hop in sequence to each router it detects in your path. Pathping runs them 100 times each... naturally, it takes a lot longer to run, so it's usually more convenient to hit a couple quick tracerts right away when you experience something odd going on.

As for what you can do, not much outside of forwarding details on your connection to your ISP and SE to see if they can get someone to investigate potential routing issues--unless you want to pay for a VPN service to try to skirt around the troubled segments. It is important to get as many samples to them so they can start to connect the dots. The same ISP names (and even the same routers) keep showing up in the routes for people who are experiencing issues. They need to get enough data to see that pattern more clearly and <hopefully> look into it more closely to see just what may be going on in those segments.

A few common KNOWN offenders (not just from FFXIV, but a host of other online games going back several years) are companies like Cogent, TATA (they often have as6453.net in the names), i-Web, alter.net, tinet... some others that escape my memory atm. But it's getting to be about 8 or 10 that are regularly coming up between NA, Oceania, and Europe.

[TuriousHD]

I have noticed that, but that was only posted recently, this is an on-going problem that has been apparent from launch.

[mayonnegg]

My issues didn't start at the 2.05 patch, it was a patch before that that kicked things off for me. Maybe a month ago I think.

[Boretalith]

Greetings,

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.