Noticing bad rubberbanding / lag in game? SE needs to dump their ISP NTT

[Deceptus]

From the technical forums (emphasis mine):

For what it's worth, here is what AT&T has given me back after some fairly insistent "please escalate this appropriately" requests on my part:

I sincerely apologize for the inconveniences caused based on info found AT&T's services to get you to the ISPs of those you want to contact. Square Enix subscribes to NTT's services to allow you to connect to their servers.

Every traceroute I've seen shows that the latency issues begin inside NTT after AT&T hands off the traffic. NTT is not processing traffic properly from AT&T (and, based on the Square Enix posts, some other ISPs as well). So, the correct takeaway is the Square Enix should find a different ISP than NTT, not that any player should switch. A possible workaround would be the VPN solutions work is because it routes the traffic around the bottleneck in NTT's network near the AT&T consumer peering where a lot of consumers come in to a less congested connection.

I dunno what to do next about this. We aren't NTT's customer. AT&T is saying that it's not their problem. NTT says it's both their problems (generally). Kinda leaves us stuck not being able to do a whole lot, and thus the "please contact your ISP" request from the Lodestone doesn't feel like it's going to get us much of anywhere.

Wish I could play the game with my kids right now without having to spend a bunch more money and time on VPN re-rerouting. (There's three of us playing, two on PS5.) And I'm not super-interested in the circus that is switching ISPs right now.

IMHO SE / CBU3 should be providing at minimum weekly updates on what they're doing to help resolve this issue (daily would be ideal). At some point, they share responsibility for this.

[NekoMataMata]

Someone with ComCast(I think it was) said they had the same issue and that it was never fixed. They said that they've been using a VPN to deal with it, and I've seen so many other people asking about VPNs that it makes me fear people are just going to deal with it... which I refuse to do.

I hate having to say this because I feel like someone is going to call me a Karen for saying it, but this isn't our problem, and as consumers we shouldn't have to be paying more for other services to solve that problem. Since so many people are doing so I really fear that I might have to quit because SE isn't going to do anything and I don't want to get a VPN to play.

[Valkyrie_Lenneth]

https://www.reddit.com/r/ffxiv/comme...lity_to_north/
This has info from ntt.

[EZGIL]

yea, I noticed

[KeshLives]

I'm on ATT, in the midwest, on 300/300 fiber, and I'm simply not having this issue, at all. However, I do not play on weekdays before about 3 PM pacific time, most days. Weekends, I don't have any of this.

So, while the NTT/ATT peering site could be part of the problem, there's more to it somewhere. I cannot duplicate these issues at all.

[Deceptus]

I'm on ATT, in the midwest, on 300/300 fiber, and I'm simply not having this issue, at all. However, I do not play on weekdays before about 3 PM pacific time, most days. Weekends, I don't have any of this.

So, while the NTT/ATT peering site could be part of the problem, there's more to it somewhere. I cannot duplicate these issues at all.

Also midwest, 1gig fiber ATT. Don't really notice it until the afternoons but it is prevalent. Dungeons/PvP/Raids, even in cities.

But Square Enix is usually good about it and proactively contacts the ISP themselves to resolve the issue or setup countermeasures against a DDoS. So it's rare that they respond like this.
.

Yoshi straight up said "It's not on our end, call AT&T".
AT&T said, "It's not on our end, it's NTT. They're screwing up multiple games" (What their data shows)
NTT has said "Crickets". Admit NOTHING!

Since the reddit post seems to explain that it's a political problem, it does explain why Square Enix can't do anything about.

But they can do something about it. Simply say "If you don't figure out a way to resolve this we will be forced to find another provider to handle our traffic and you will lose out on whatever figure we are paying you and we'll not recommend you to anyone else in the industry"

[DrWho2010]

But they can do something about it. Simply say "If you don't figure out a way to resolve this we will be forced to find another provider to handle our traffic and you will lose out on whatever figure we are paying you and we'll not recommend you to anyone else in the industry"

well depends on the terms of their contract with them are. they might not be able to do that. you don't know what might or might not be in it. there could be massive penalties for breaking it on their end.

[Deceptus]

well depends on the terms of their contract with them are. they might not be able to do that. you don't know what might or might not be in it. there could be massive penalties for breaking it on their end.

Every contract worth a d@mn has a "expected workmanship" clause that basically says that if something isn't meeting a standard that a reasonable workman could perform it generally allows for restitution / resolution.

[Valkyrie_Lenneth]

Every contract worth a d@mn has a "expected workmanship" clause that basically says that if something isn't meeting a standard that a reasonable workman could perform it generally allows for restitution / resolution.

Changing isp within a data center is far more difficult than for consumers or small businesses.

[TaleraRistain]

Every contract worth a d@mn has a "expected workmanship" clause that basically says that if something isn't meeting a standard that a reasonable workman could perform it generally allows for restitution / resolution.

Even if they are able to get released from the contract, there's the logistics of transferring their system infrastructure to a new one. They may be working on this behind the scenes and just can't say anything. Or might still be in some sort of negotiations. It's frustrating and I'm affected by it and do wish their was a bit more of some sort of acknowledgment, but I can also see where they may not be able to make changes quickly. Twelve knows even at my smaller business trying to make that sort of change takes time (and if you miss one path update suddenly your customers can't access the customer-facing application) so I can only imagine the red tape and headache at a larger scale.