Bad lag again with NTT's NA server network

[Plaides_Nova]

I have been experiencing some rubber-banding since 6.3, at first i though it was my graphics but i played at min specs and the issue persisted, then i though it was my ISP but then i can play other MMOS like wow and guild wars without rubber banding not to mention other online games. this Seems to be a specific issue with FF14 it gets really bad in alliance raids, on dungeons is noticeable and even in trust is present. i have re-installed multiple times and even updated my graphics card. i been keeping an eye on the send and receive(wifi icon in game) and its all over the place it goes from 20 to 300 to 900 in a matter of second and it coincided with the rubber-banding. has anyone found a workaround or a fix to this problem or this is an ongoing issue?

[Illyrian94]

I have been experiencing some rubber-banding since 6.3, at first i though it was my graphics but i played at min specs and the issue persisted, then i though it was my ISP but then i can play other MMOS like wow and guild wars without rubber banding not to mention other online games. this Seems to be a specific issue with FF14 it gets really bad in alliance raids, on dungeons is noticeable and even in trust is present. i have re-installed multiple times and even updated my graphics card. i been keeping an eye on the send and receive(wifi icon in game) and its all over the place it goes from 20 to 300 to 900 in a matter of second and it coincided with the rubber-banding. has anyone found a workaround or a fix to this problem or this is an ongoing issue?

This is an ongoing issue for folks with AT&T internet (and some folks with other ISPs as well)--your best bet is to use something like Cloudflare Warp or a VPN service as these are workarounds that the community has figured out.

[Rekts]

This is confusing ngl. Either it's an NTT node problem or an ATT peer point issue. But neither of them will give a clear answer. I suppose it's not conceivable for SE to just reroute away from the problem area is it?

[Illyrian94]

As expected, AT&T's response is to point a finger back at Square and NTT and say we need to reach out to them.

https://forums.att.com/conversations...05de56a01bcff0

I'm going to open yet another support ticket with SE. Not that I expect anything to come of it, but I figure I can at least be a continual support issue for them if they're going to continue to refuse to acknowledge the issue and bounce us back and forth to AT&T. What a joke of a situation.

[Rekts]

As expected, AT&T's response is to point back at Square and NTT and say we need to reach out to them.

https://forums.att.com/conversations...05de56a01bcff0

I'm going to open yet another support ticket with SE. Not that I expect anything to come of it, but I figure I can at least be a continual support issue for them if they're going to continue to refuse to acknowledge the issue and bounce us back and forth to AT&T. What a joke of a situation.

From the response of the "expert"(not even an AT&T employee), it's an issue between both NTT and ATT. Everyone really does suck here.

[Kayetiln]

I did a traceroute, and found NTT screwing up. Googled NTT outage issues and found this thread. Glad to see I'm not alone seeing the network issues with FF14. Not glad to see people are having issues. Hopefully NTT can get this resolved :P

[gameofscones]

We're still in it, huh. I've got about a week and a half left on my sub, and I don't think this will be resolved by the time it expires. Ah, well.

My current trace route (and for reference, I'm up on Lake Erie):

  5     *        *        *     Request timed out.
  6    36 ms    48 ms    12 ms  32.130.17.75
  7    14 ms    15 ms    14 ms  cgcil402igs.ip.att.net [12.122.133.161]
  8    13 ms    18 ms    14 ms  192.205.32.194
  9    14 ms    14 ms    17 ms  ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
 10     *       64 ms    70 ms  ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 11   121 ms   119 ms   120 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 12     *      120 ms   120 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 13   119 ms   123 ms     *     204.2.29.241
 14   119 ms   120 ms     *     204.2.29.6
 15   119 ms     *      119 ms  204.2.29.6

My ping is better connecting to the European data centers than it is the NA ones. Yikes.

[GaiusDrakon]

Guys. Just use Mudfish. It's extremely cheap and there are multiple nodes to choose from so if one doesn't work out just pick another one.

I know it's far more unintuitive than other VPNs though.

[aerimisia]

Guys. Just use Mudfish. It's extremely cheap and there are multiple nodes to choose from so if one doesn't work out just pick another one.

I know it's far more unintuitive than other VPNs though.

Not everyone can use a VPN sadly. Console doesn’t let you add one and AT&T blocks all of the work arounds that would potentially allow you to use one on your PS. Some people might also not have the extra funds for a second sub to something they shouldn’t even need to be able to play in the first place.

Definitely if you can use a VPN I encourage it and Im happy for everyone who has that option, but at the end of the day what we need is for something to be done and to not allow this problem to get swept under the rug.

[Rekts]

Guys. Just use Mudfish. It's extremely cheap and there are multiple nodes to choose from so if one doesn't work out just pick another one.

I know it's far more unintuitive than other VPNs though.

It's already been pointed out, but yes console players can't use a VPN. Regardless PC players shouldn't have to use a VPN either.

ATT pretty much said definitively that it's an NTT issue on one of the threads of their forum(the problem node is outside their network). If that's actually true, we're not NTT's customer. SE is, they're the ones who will have to pressure NTT to fix it.

And since we still hadn't had any real communication outside of "call your ISP" I don't think we're looking at a resolution anytime soon.