Why the netcode issue exists, and why it cannot be fixed.

[NeonC]

Close proximity (or low amount of hops) to the data servers. In low-latency scenarios, the server live-state model is superior in all regards to client live-state.

Hmm sounds like a certain small country that may or may not have produced the game benefits greatly while we eat all teh plumes.

[Sinth]

Hmm sounds like a certain small country that may or may not have produced the game benefits greatly while we eat all teh plumes.

Yes, it would also explain the lack of foresight into the potential gravity of the issue as the majority (if not all) of the QA testing was performed on said small country

[Hyrist]

Yes, it would also explain the lack of foresight into the potential gravity of the issue as the majority (if not all) of the QA testing was performed on said small country

This doesn't make sense to me.

QA testing could easily be done by Square Enix Headquarters USA, which is located in California, and more than likely was. Granted, this is California to Japan up until the later Beta testing. However I wouldn't go so far as to presume that they did not test, at least in the mid stages, the connection quality of the netcode outside of region.

How their connections would be solid while others are having difficulties, I cannot know. Perhaps this issue did not articulate itself gravely until stress tests began, which at that point it would be too late. But this is all just speculation on my end.

[AlmaMalma]

The other factor, is that instanced events like primals and coil are going to be at the moment full of players. That'll be more load on the servers that host them. In 2.1 when folks emigrate onto Extreme, empty Titan (Hard) servers will be whizzing along like mad things compared to now. Unless the Extreme versions are hosted on the same servers... that'll be fun for all.