Bad lag again with NTT's NA server network

[ntt_routing_is_an_issue]

Either the lsanca07 node is completely broken (timed out), or today my traffic is not routed to that node. More or less, this is a normal tracert for me. Cautious optimism may be allowed!

Keep in mind routers along the way don't always respond to pings, and its completely normal.

[burgerfall]

No replies today, is it finally over?

[Illyrian94]

No replies today, is it finally over?

Personally I'm reserving judgement (and not resubscribing) until I see a solid week without this issue, but there does seem to have been some sort of potential change starting on Friday. Could be that they fixed something, could also be that the simultaneous release of Diablo 4 early access and Street Fighter 6 drew enough traffic away that the congestion isn't bad enough to cause problems.

Fingers crossed, but I'm not necessarily holding out hope at this point. It'd be nice to play my silly explosion cat again, though.

[RyuezaneWithersoul]

I agree, plus lately, since the ping issue, my game would freeze a bit not sure if it's my end or the severs. but ya.

[Merricat]

I'm cautiously optimistic. I'm still not getting the kind of (good) performance I did before this issue started. But it's a thousand times better than it was at the worst, so I'll take it for now.

[laurayco]

I'm still having consistency issues, personally speaking. It seems to get turbo bad around 830pm CST and just be flaky other times.

laurayka@yshtola  ~  traceroute neolobby02.ffxiv.com
traceroute to neolobby02.ffxiv.com (204.2.29.6), 30 hops max, 60 byte packets
1 172.29.176.1 (172.29.176.1) 0.189 ms 0.182 ms 0.179 ms
2 10.10.10.1 (10.10.10.1) 3.056 ms 3.563 ms 1.409 ms
3 192.168.1.254 (192.168.1.254) 7.145 ms 6.423 ms 6.623 ms
4 108-226-52-1.lightspeed.fyvlar.sbcglobal.net (108.226.52.1) 7.876 ms 7.639 ms 7.870 ms
5 75.14.128.90 (75.14.128.90) 9.284 ms 9.508 ms 9.505 ms
6 * * *
7 * * *
8 * * *
9 32.130.25.65 (32.130.25.65) 21.901 ms 17.874 ms 21.130 ms
10 ae-5.a00.dllstx14.us.bb.gin.ntt.net (129.250.8.237) 16.351 ms 22.525 ms 23.702 ms
11 ae-2.r20.dllstx14.us.bb.gin.ntt.net (129.250.4.9) 31.911 ms 31.908 ms 31.905 ms
12 ae-2.r24.lsanca07.us.bb.gin.ntt.net (129.250.7.69) 97.653 ms 97.649 ms *
13 ae-5.a01.scrmca03.us.bb.gin.ntt.net (129.250.2.7) 55.068 ms 55.066 ms 56.319 ms
14 ae-1.a00.scrmca03.us.bb.gin.ntt.net (129.250.4.76) 61.233 ms 56.371 ms 60.339 ms
15 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 57.992 ms 57.724 ms 58.996 ms
16 204.2.29.241 (204.2.29.241) 54.629 ms 54.323 ms *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

[TaleraRistain]

Been running checks all weekend that were good and just now about 9pm EDT and things are clear

6 9 ms 15 ms 13 ms cgcil402igs.ip.att.net [12.122.133.161]
7 12 ms 8 ms 10 ms 192.205.32.194
8 13 ms 21 ms 15 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 55 ms 59 ms 55 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 58 ms 58 ms 57 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 58 ms 66 ms 62 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 59 ms 58 ms 58 ms 204.2.29.6

I'm still a bit gun shy to try doing EX without a VPN but I may try tonight

[Jenna_Leowulf]

The issue is mostly resolved for me at least. I live in the Atlanta, GA area, and pings have been pretty stable, even improved by a few ms. I have gotten a minor lag spike a couple of times, but I got those before all this mess started.

[Lahtori]

3 4 ms 3 ms 3 ms 71.155.29.140
4 * * * Request timed out.
5 7 ms 7 ms 7 ms 32.130.25.65
6 26 ms 27 ms 24 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
7 26 ms 13 ms 10 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
8 82 ms 85 ms 86 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 42 ms 43 ms 44 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 44 ms 43 ms 43 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 44 ms 43 ms 44 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 45 ms 43 ms 43 ms 204.2.29.6

Today got some response from lsanca07 and its still in the 80ms. At least the other nodes seem to be consistent and normal.

[Janyd]

Yeah, same for me, Lahtori. Averaging around 58 to 60 ms at the Aether DC on the end of my traceroutes.

Was able to do Normal reclears of Anabaseios and roulettes with no issues, with the VPN turned Off for testing.

It feels like it's back to the way it was before all this mess, at least for the moment.

Still not sure if AT&T did some rerouting, or if the launch of Diablo 4 and Street Fighter 6 were both factors in easing traffic to those nodes, or if it's something else, but so far so good.

Give it another few days before we can call it "solved" at least.