Bad lag again with NTT's NA server network

[Brynwolf]

Haven’t been able to successfully connect a VPN to my playstation console as connection strength is too low.

I’ve been unable to play the game because of huge lag spikes and crashes. If this issue doesn’t get resolved soon, I’m going to miss out on the new savage tier with my static. I’m hoping these issues will work itself out before next Tuesday.

[Rekts]

Haven’t been able to successfully connect a VPN to my playstation console as connection strength is too low.

I’ve been unable to play the game because of huge lag spikes and crashes. If this issue doesn’t get resolved soon, I’m going to miss out on the new savage tier with my static. I’m hoping these issues will work itself out before next Tuesday.

I'm in the same boat. On console so VPN isn't viable. I'd love to have optimism for a fix soon but since NTT is still pointing fingers at ATT(even tho everything we've seen shows it's NTT), I'm losing hope.

Hopefully SE is applying pressure since they pay NTT for their services, but they've been silent about this issue as well. Some sort of concrete communication would be nice.

[Arion_x3]

If this doesn’t get resolved within the next week ill be unsubscribing, sorry SE but i cant keep paying for a game i cant even play. Also im a console player so vpn is out of the question.

[brnslpy]

For those on Console, VPN is viable without mucking up one's entire network/router/modem. If one can stomach a $5 / month VPN service to keep playing, a RaspberryPi+Wireguard or a $30 OpenWRT router on Amazon can get you on one of the many VPN services out there (OpenVPN or Wireguard) with a PS4/PS5 and gets you around the bad nodes.

Tried it out today and I'm getting better pings and latency on the VPN than a direct connection with ATT Fiber. If anyone's interested in learning more, look up RaspberryPi+Wireguard, or GL.INET router devices on Amazon and I have links for setting it up. Took 30 min to get my PS5 to route through a RaspberryPi with Mullvad's Wireguard VPN.

... Or, NTT and ATT can undo whatever the heck they did on May 15th... one can dream.

[Janyd]

https://na.finalfantasyxiv.com/lodes...6a07e92f6a0f29

Finally, a proper Lodestone post about it. Took them far too long, but at least the situation is still being addressed.

Keep fighting.

[Aranthon]

I'm happy to see the SE has finally given us proper communication, but this situation still looks dire. Maybe something is lost in translation, but it sounds like every party involved is unsure who is responsible for fixing the faulty connection. I'm hoping and praying that we will have a solution before savage is unlocked.

[DES_VII]

https://na.finalfantasyxiv.com/lodes...6a07e92f6a0f29

Finally, a proper Lodestone post about it. Took them far too long, but at least the situation is still being addressed.

Keep fighting.

I'm glad they responded I tried calling AT&T didn't get anywhere. I wonder what or if they can get this resolved. Its hard playing a game with so much rubber banding and lag spikes.

[Janyd]

I'm glad they responded I tried calling AT&T didn't get anywhere. I wonder what or if they can get this resolved. Its hard playing a game with so much rubber banding and lag spikes.

I wish I knew what that'd take, but at least it isn't hopeless. Not now, not ever.

See? Cynicism gains us NOTHING. Late-stage Capitalism my ass, there's no time for that kind of dour kvetching.

What works is pressure and reports, and a few angry phone calls/DMs to affected ISPs.

That, and keep some bitter resentment towards paying for a VPN, if you're like me have no choice but to do so. Spite's a good motivator when tempered.

But on that note, I seem to recall earlier in the thread that some CenturyLink users are now being affected. Keep 'em coming, everyone!

[Rekts]

Finally some communication, even tho it didn't bring good news.

It seems to me that NTT is very much responsible, but since most of the traffic is AT&T they have some leverage. That's just how I'm reading this situation tbh.

[lolnotacat]

Finally some communication, even tho it didn't bring good news.

It seems to me that NTT is very much responsible, but since most of the traffic is AT&T they have some leverage. That's just how I'm reading this situation tbh.

Yup, this exact same thing happened a few years ago. It's clearly NTT when looking at Trace routes. It's even the same node as last time if I'm not mistaken. Unfortunately Squenix probably doesn't have much recourse, despite being NTT's customer because NTT is enormous and FFXIV's US income is for NTT is probably equivalent to a rounding error for them. This is why Squenix probably wants us going through AT&T. They're also huge and probably have more pull. Unfortunately AT&T also doesn't care because it's not their infrastructure that's causing the problem and the amount of FFXIV players on their service isn't worth the effort to get someone to hassle NTT either.