Bad lag again with NTT's NA server network

[Alajandria]

I've also been having issues all week on at&t just to add to the voices here. I did install ProtonVPN (free version) and am having no issues now as long as I use that. Def Recommend for anyone that doesn't want to pay extra just to play.

[juniperspring]

I've also been having issues all week on at&t just to add to the voices here. I did install ProtonVPN (free version) and am having no issues now as long as I use that. Def Recommend for anyone that doesn't want to pay extra just to play.

You are so beautiful thank you

[Thistlefox]

I've also been having issues all week on at&t just to add to the voices here. I did install ProtonVPN (free version) and am having no issues now as long as I use that. Def Recommend for anyone that doesn't want to pay extra just to play.

Thank you for recommending this! I did same tonight, and went to Paradigm's to test it...I am reasonably functional again.

And I'm really curious what was done a week or so ago to cause all this lag. I feel like some change was made somewhere and it didn't have the right results.

[Janyd]

Thank you for recommending this! I did same tonight, and went to Paradigm's to test it...I am reasonably functional again.

And I'm really curious what was done a week or so ago to cause all this lag. I feel like some change was made somewhere and it didn't have the right results.

Aye, if I had to guess, something was changed at the node last weekend/before Monday (May 15) that wasn't a good change at all.

But, lest we forget, there was a reply on Reddit that NTT was still working on the issue (as of Saturday, May 20) with AT&T: https://www.reddit.com/r/ffxiv/comme...mment/jkwjums/

[RyuezaneWithersoul]

I've been lagging for the past 6 days and almost in 6.4 patches not sure if they will fix it but willing to share my traceroute over and over till they fix the problem I understand everyone is frustrated like myself. I just hope there fixing it kind of sucks they kept us in the dark since maintenance happened a week ago this issue has been going on I just hope they really fix this problem before Tuesday because there is going to be a lot of angry people on patch day if this isn't fixed.

[ToxLayzer]

I thought I was just going crazy, tried every fix I could find until I stumbled on this thread. Same issues for me, also on ATT. I will have to try a VPN while we wait for a fix.

[KuroEmiya]

Kinda hoping when patch drops with loads of ppl logging back in and finding the same issue will force SE to do something. At the very least be more communicative.

[ntt_routing_is_an_issue]

Kinda hoping when patch drops with loads of ppl logging back in and finding the same issue will force SE to do something. At the very least be more communicative.

NTT already has this on their radar and claim to be working on it. It's just unfortunate it took people emailing their NOC to find out wtf is going on vs SE putting something out saying NTT is working the issue.

[brnslpy]

Its 2:15AM EDT, the usual time when things start to clear up, and still getting lag:

Ping:

$ ping 204.2.29.122
PING 204.2.29.122 (204.2.29.122): 56 data bytes
64 bytes from 204.2.29.122: icmp_seq=0 ttl=48 time=112.574 ms
64 bytes from 204.2.29.122: icmp_seq=1 ttl=48 time=112.086 ms
64 bytes from 204.2.29.122: icmp_seq=2 ttl=48 time=97.176 ms
Request timeout for icmp_seq 3
64 bytes from 204.2.29.122: icmp_seq=4 ttl=48 time=111.966 ms
64 bytes from 204.2.29.122: icmp_seq=5 ttl=48 time=111.932 ms
64 bytes from 204.2.29.122: icmp_seq=6 ttl=48 time=112.411 ms
64 bytes from 204.2.29.122: icmp_seq=7 ttl=48 time=111.154 ms
64 bytes from 204.2.29.122: icmp_seq=8 ttl=48 time=101.274 ms
^C
--- 204.2.29.122 ping statistics ---
9 packets transmitted, 8 packets received, 11.1% packet loss
round-trip min/avg/max/stddev = 97.176/108.822/112.574/5.648 ms

Currently on a different ISP so I can play FFXIV instead of using my ATT Fiber connection, which this new ISP is a world of improvement but I wish the ATT network and all using it can be resolved soon. Heard NTT is aware of congestion but it's a peer-to-peer "who's going to pay for expansion issue" whatever that is worth.