Bad lag again with NTT's NA server network

[Elizasylen]

Google Fiber. Literally unplayable. This is what Dancer dance step look like with this lag. https://youtube.com/clip/Ugkx1PMU4ZJ...vSGY5qwyh1hvQx Aether Sargatanas.

[Esravei]

Spectrum in FL, game is basically unplayable with tons of lag even just opening a simple menu, takes several seconds to load and characters teleporting around etc.

[Neon231]

Posting to add awareness to this issue. Been lagging ALL day(logged off for most of it and suffered through Expert and Frontlines roulette.) I am located in Louisiana using COX and getting insane lag spikes making the game unplayable.

[Uno_Amaretto]

My ISP is Optimum and I've yet to see anyone else (that I know of) with that provider...but I've seen other users who've had issues being in Texas, so I guess I can at least add that I'm in the DFW area if it's relevant. I'm absolutely losing my mind here.

I have Optimum and my problems started just today. My two friends who are in DFW are on AT&T and were hit by the initial instance of this.

[Sunless_Sea]

Spectrum. Several members of my static were lagging tonight, P9S was unplayable for our group. After we gave up for the night, I found that even the market board and the animals on my island were lagging

[Gemmeni]

Sparklight, Houston, Tx. 13% average packet loss originating from ntt.net @ 1700 ms

[azhdaha]

Astound broadband, Houston area, here. My husband and I just started having this too, just today. Me on PC, him PS5. Lag making the game unplayable. Even the game launcher is taking longer to load, as well as in-game menus like summoning bell. Internet works perfectly otherwise, FFXIV is the only problem.

[jangetta]

I'm on google fiber, bad lag, and just looking at this post redirected me to the french website. I literally am in NA.

[Lizellea]

I am in Florida and have Spectrum. My best friend is in Texas and has Optimum with the same issues as the rest. Seeing that several people have different Service providers... I do think it's safe to say it isn't anything with us or our ISPs but with the NA servers themselves.

[MimikoMono]

Adding another report, Google Fiber from Austin, TX.

Tracing route to neolobby02.ffxiv.com [204.2.29.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 10.26.2.83
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 7 ms 7 ms 8 ms ae1.pr02.dfw101.googlefiber.net [192.119.17.142]
7 5 ms 7 ms 7 ms ix-ae-12-0.tcore1.dt8-dallas.as6453.net [216.6.53.62]
8 6 ms 7 ms 7 ms if-ae-2-2.tcore2.dt8-dallas.as6453.net [66.110.56.6]
9 6 ms 7 ms 6 ms ae-4.a01.dllstx14.us.bb.gin.ntt.net [129.250.9.193]
10 6 ms 7 ms 8 ms ae-3.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.23]
11 * * 137 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 139 ms 139 ms 142 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 * 140 ms 138 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 151 ms 151 ms 148 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 141 ms 142 ms 141 ms 204.2.29.6

------

By running a VPN connected to San Jose, CA, the problem is resolved as this geographically avoids the bad node (appears to be in Los Angeles, CA based on its hostname). Traceroute with VPN enabled below:

Tracing route to neolobby02.ffxiv.com [204.2.29.6]
over a maximum of 30 hops:

1 40 ms 39 ms 39 ms 10.64.0.1
2 45 ms 41 ms 41 ms 142.147.89.193.static.xtom.com [142.147.89.193]
3 39 ms 43 ms 38 ms a1.cr01.sjc.xtom.us [104.245.11.100]
4 40 ms 39 ms 41 ms xe-0-0-10-0.a02.snjsca04.us.bb.gin.ntt.net [157.238.226.244]
5 40 ms 40 ms 44 ms ae-9.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
6 43 ms 43 ms 45 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
7 43 ms 43 ms 44 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
8 * * * Request timed out.
9 43 ms 43 ms 42 ms 204.2.29.6

I know this was an issue last week for AT&T users. Hasn't been an issue for me for a few months until today. Last time it was busted for me, it was a different NTT node in Arizona that was the problem.

Not great when this raid tier requires very precise reactions/snapshots even in p9s and p10s...