Bad lag again with NTT's NA server network

[felgryn]

Has the audio issue been solved in this latest patch? I was one of the ones where the audio cut-out after 30-40 minutes. I've help back on progressing quest line as i would like to hear the sound. The issues was recognized two weeks ago - and it was said it would take two weeks to resolve - but i have not heard any further comment from SE as to whether the issue has been resolved....

[Janyd]

Has the audio issue been solved in this latest patch? I was one of the ones where the audio cut-out after 30-40 minutes. I've help back on progressing quest line as i would like to hear the sound. The issues was recognized two weeks ago - and it was said it would take two weeks to resolve - but i have not heard any further comment from SE as to whether the issue has been resolved....

Yes, it was part of the hotfixes that were included in this week's maintenance.

https://na.finalfantasyxiv.com/lodes...d378cf14ec4020

[TaleraRistain]

I ran EX last night multiple times without the VPN and with no lag. Still not going to say it's fixed until this is consistent over longer than it's been.

[Rekts]

Still no issues, but as others have said I'm not going to call it "fixed" until we get a true stress test, which fortunately will probably be a little while.

[felgryn]

Yes, it was part of the hotfixes that were included in this week's maintenance.

https://na.finalfantasyxiv.com/lodes...d378cf14ec4020

Great News! Thanks Janyd, i didn't catch that one sentence in the update - back to the quest line!

[Kwehvehpeh]

So It seems that it has eased up. So much so that nord VPN is actually make my connection far worse, especially in frontlines.

So I get to save $12 again!

[Ahumaya]

Everything looks like it's working now, which is good.

While we will likely never know what the true root cause is, as no one involved will ever have any reason to reveal the cause of a 3+ week issue, we can make a few inferences, and a reasonable idea as to what happened, based on the evidence provided in this thread.

It looks most likely that NTT had a dying node. They were resistant to investigate and resolve this issue, as the replacement of the node would be a cost measured both in a large amount of time and a large amount of money. During this slow death, the node would thrash the very moment it became saturated, causing excessive latency, and worse packet loss.

After about 3 weeks, it is very likely that the node simply died, and automatic network routing within the NTT infrastructure re-routed around the failed node (rather than through it), and thus the issue was resolved. And as the device has entirely failed, NTT will need to replace it, and in the meantime the automatic reroute around it has resolved the immediate issue.

Looking at logs, the specific node which was causing the vast majority of issues within the NTT infrastructure no longer appears in traceroutes, which adds credence to this theory. But alas, we will very likely never know.

Much love, glad we got through this.

[Uno_Amaretto]

Good thread, see you guys next time! Maybe we can get the next one to 200 pages!

Because this can and most likely will happen again as long as all the NA data centers are centralized in one location.

[RyuezaneWithersoul]

even if the latency issues died out. we should bring up this topic if anyone going to fanfest. because this could happen to anyone who has other ISP's and it is more annoying to deal with. Plus this wouldn't fly on other games with node issues. if Square wants xiv to be online then they gotta fix there severs nodes for the next 10 years. because this game will be active for that long.

[Janyd]

Everything looks like it's working now, which is good.

While we will likely never know what the true root cause is, as no one involved will ever have any reason to reveal the cause of a 3+ week issue, we can make a few inferences, and a reasonable idea as to what happened, based on the evidence provided in this thread.

It looks most likely that NTT had a dying node. They were resistant to investigate and resolve this issue, as the replacement of the node would be a cost measured both in a large amount of time and a large amount of money. During this slow death, the node would thrash the very moment it became saturated, causing excessive latency, and worse packet loss.

After about 3 weeks, it is very likely that the node simply died, and automatic network routing within the NTT infrastructure re-routed around the failed node (rather than through it), and thus the issue was resolved. And as the device has entirely failed, NTT will need to replace it, and in the meantime the automatic reroute around it has resolved the immediate issue.

Looking at logs, the specific node which was causing the vast majority of issues within the NTT infrastructure no longer appears in traceroutes, which adds credence to this theory. But alas, we will very likely never know.

Much love, glad we got through this.

You might be right, Ahumaya. I haven't noticed that node come up in my traceroutes since the start of the month.

Hopefully, the node kicking the bucket was the "fix" for the moment.