Bad lag again with NTT's NA server network

[Dante505]

AT&T Fiber customer over here as well, just sent the support form in with the traceroute. I play with someone in Italy, but we are on Sargatanas and she has better connection than me at the moment lol.

[Rexxus]

I'd also like to point out that most of the free VPNs give you a bandwidth limit on their trials. But its super easy to turn them off and on when you're doing the content that requires it.

My 2GB a month with Windscribe will probably last me several weeks since I only need to turn it on when I'm running my Frontlines.

[Oxrel]

AT&T user and same thing here. Spiking as far up as 66k ms today during alliance raid roulette around 3pm PST. Was entirely unplayable. Trying to bear with it and get my daily things done, but other than that, I just don't even bother playing.

[samiam314]

Same issue here, Northeast Ohio

[rainhadar]

Krojack I wanted to thank you for the information you provided on all of this. I play on the NA server Aether and my game has been having major lag & packet loss since the update a bit ago. I submitted a ticket to SE yesterday. It seems that at least they at least posted on twitter, but no eta on the fix. I finally decided to go the vpn route via PIA with the list you provided and thank goodness that helped. I appreciate your post and just wanted to take a minute out and say Thank You! Hopefully AT&T, NTT.net, SE can get this worked out as I really hate having to pay extra for a vpn but I also hate not being able to play.

[HikariHoshino]

Just now finding this after doing some investigation on my own. I have normal traffic flow until I boot up XIV. Just tonight I got booted twice and get the freeze-move, freeze-move.
I did a packet trace on the connection and found packet drops and retransmissions every time I saw the freezing in game. I'm located in SE Ohio. Here's the trace for anyone interested.

39025 104.018019 0.481227 NTT XIV Server LocalMachine TCP 403 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=62850 Ack=1067 Win=33232 Len=349
39028 104.181888 0.002459 NTT XIV Server LocalMachine TCP 114 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=62790 Ack=1067 Win=33232 Len=60
39031 104.304381 0.064532 NTT XIV Server LocalMachine TCP 315 55022 → 55390 [PSH, ACK] Seq=63199 Ack=1067 Win=33232 Len=261
39032 104.308320 0.003939 ae-4.a00.scrmca03.us.bb.gin.ntt.net LocalMachine ICMP 70 Time-to-live exceeded (Time to live exceeded in transit)
39035 104.363358 0.013284 NTT XIV Server LocalMachine TCP 60 55022 → 55390 [ACK] Seq=63460 Ack=1122 Win=33232 Len=0
39036 104.429567 0.066209 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net LocalMachine ICMP 110 Time-to-live exceeded (Time to live exceeded in transit)
39041 104.838182 0.224026 NTT XIV Server LocalMachine TCP 488 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=63868 Ack=1122 Win=33232 Len=434
39045 105.360890 0.387070 NTT XIV Server LocalMachine TCP 462 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=63460 Ack=1122 Win=33232 Len=408
39047 105.482398 0.121445 NTT XIV Server LocalMachine TCP 743 55022 → 55390 [PSH, ACK] Seq=64302 Ack=1122 Win=33232 Len=689
39051 106.020195 0.245740 NTT XIV Server LocalMachine TCP 626 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=65249 Ack=1122 Win=33232 Len=572
39056 106.181434 0.014929 NTT XIV Server LocalMachine TCP 312 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=64991 Ack=1122 Win=33232 Len=258
39059 106.309410 0.062377 NTT XIV Server LocalMachine TCP 357 55022 → 55390 [PSH, ACK] Seq=65821 Ack=1122 Win=33232 Len=303
39061 106.470830 0.121769 NTT XIV Server LocalMachine TCP 591 55022 → 55390 [PSH, ACK] Seq=66124 Ack=1122 Win=33232 Len=537
39072 106.646217 0.010708 NTT XIV Server LocalMachine TCP 114 55022 → 55390 [PSH, ACK] Seq=66661 Ack=1122 Win=33232 Len=60
39074 106.696313 0.005532 NTT XIV Server LocalMachine TCP 60 55022 → 55390 [ACK] Seq=66721 Ack=1170 Win=33232 Len=0
39087 107.089420 0.062446 NTT XIV Server LocalMachine TCP 66 [TCP Previous segment not captured] 55022 → 55391 [ACK] Seq=382 Ack=232 Win=29200 Len=0 SLE=177 SRE=232
39092 107.129073 0.002126 NTT XIV Server LocalMachine TCP 107 [TCP Retransmission] 55022 → 55391 [PSH, ACK] Seq=329 Ack=232 Win=29200 Len=53
39094 107.173059 0.006464 NTT XIV Server LocalMachine TCP 401 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=66967 Ack=1170 Win=33232 Len=347
39098 107.332585 0.105271 NTT XIV Server LocalMachine TCP 300 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=66721 Ack=1170 Win=33232 Len=246
39106 107.453685 0.002812 NTT XIV Server LocalMachine TCP 227 55022 → 55390 [PSH, ACK] Seq=67314 Ack=1170 Win=33232 Len=173
39116 107.986452 0.155478 NTT XIV Server LocalMachine TCP 347 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=67808 Ack=1170 Win=33232 Len=293
39122 108.147687 0.000394 NTT XIV Server LocalMachine TCP 375 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=67487 Ack=1170 Win=33232 Len=321
39129 108.269934 0.088408 NTT XIV Server LocalMachine TCP 273 55022 → 55390 [PSH, ACK] Seq=68101 Ack=1170 Win=33232 Len=219
39139 108.447399 0.016012 NTT XIV Server LocalMachine TCP 207 55022 → 55390 [PSH, ACK] Seq=68320 Ack=1170 Win=33232 Len=153
39156 108.972841 0.043095 NTT XIV Server LocalMachine TCP 486 [TCP Previous segment not captured] 55022 → 55390 [PSH, ACK] Seq=68732 Ack=1170 Win=33232 Len=432
39162 109.133371 0.053097 NTT XIV Server LocalMachine TCP 313 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=68473 Ack=1170 Win=33232 Len=259
39169 109.253519 0.017840 NTT XIV Server LocalMachine TCP 503 55022 → 55390 [PSH, ACK] Seq=69164 Ack=1170 Win=33232 Len=449
39192 110.293386 0.044777 NTT XIV Server LocalMachine TCP 214 [TCP Retransmission] 55022 → 55390 [PSH, ACK] Seq=69613 Ack=1170 Win=33232 Len=160

[Kaitlen]

I'm based in Tokyo and have been on Hyperion for the duration of the game since 2.0.
I rarely have any issue playing unless there's some locally induced problem.
The only real benefit is that I'm within the NTT network the entire time (OCN is provider on NTT).
There was some packet loss going on once my connection hit the next hop after crossing the ocean (#9-#11 below), but it seems to be gone now.

(Tracing/Pinging a Primal DC IP) Taken at 11:45am JST 5/18/23.

1 <1 ms <1 ms <1 ms RT-AC88U-2710 [192.168.1.254]
2 2 ms 1 ms 2 ms 118.23.27.227
3 2 ms 2 ms 2 ms 118.23.27.21
4 4 ms 4 ms 4 ms 118.23.4.5
5 4 ms 2 ms 2 ms 180.8.126.49
6 3 ms 3 ms 4 ms 122.1.245.209
7 3 ms 3 ms 3 ms ae-6.r02.tokyjp05.jp.bb.gin.ntt.net [120.88.53.21]
8 5 ms 3 ms 3 ms ae-3.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.23]
9 112 ms 112 ms 116 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 * 112 ms * ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 128 ms 115 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 115 ms 114 ms 114 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * * * Request timed out.
14 115 ms 115 ms 115 ms 204.2.29.86

Ping Stats:
Ping statistics for 204.2.29.86:
Packets: Sent = 321, Received = 321, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 143ms, Average = 116ms

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Edit: Added 2nd Sample from 1:29pm JST - seems to have stabilized from early this morning.

Tracing route to 204.2.29.86 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC88U-2710 [192.168.1.254]
2 2 ms 2 ms 2 ms 118.23.27.227
3 3 ms 2 ms 3 ms 118.23.27.21
4 4 ms 3 ms 3 ms 118.23.4.5
5 6 ms 6 ms 4 ms 180.8.126.49
6 2 ms 3 ms 3 ms 122.1.245.209
7 3 ms 4 ms 4 ms ae-6.r02.tokyjp05.jp.bb.gin.ntt.net [120.88.53.21]
8 3 ms 2 ms 3 ms ae-3.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.23]
9 112 ms 110 ms 110 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 113 ms 119 ms 115 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 119 ms 137 ms 119 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 115 ms 115 ms 115 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * * * Request timed out.
14 115 ms 115 ms 117 ms 204.2.29.86

Ping statistics for 204.2.29.86:
Packets: Sent = 2517, Received = 2517, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 157ms, Average = 118ms

Replying with an update from my post yesterday. I took another sample as of 10:25am JST (6:25pm PST).
I have the unique view of being inside the NTT network for the entire path and it does reflect some consistent issues once my connection hits the US side. (hop #9)
Hops #2-#6 are also NTT hops, but just no RDNS entry.

Tracing route to 204.2.29.86 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms RT-AC88U-2710 [192.168.1.254]
2 2 ms 2 ms 2 ms 118.23.27.227
3 2 ms 2 ms 2 ms 118.23.27.21
4 7 ms 8 ms 5 ms 118.23.4.5
5 3 ms 3 ms 7 ms 180.8.126.49
6 29 ms 19 ms 18 ms 122.1.245.209
7 12 ms 13 ms 14 ms ae-6.r02.tokyjp05.jp.bb.gin.ntt.net [120.88.53.21]
8 19 ms 23 ms 27 ms ae-3.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.23]
9 * 122 ms 126 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 151 ms 157 ms 139 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 * 140 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 118 ms 116 ms 114 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * * * Request timed out.
14 115 ms 115 ms 117 ms 204.2.29.86

Despite the issues noted above, I'm not experiencing packet loss today and no issues in-game.
(I'm usually on during Japan daytime (tyvm wfh!) and partially in the evening hours)
Ping Sample from 10:25AM-10:35AM.

Ping statistics for 204.2.29.86:
Packets: Sent = 740, Received = 740, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 157ms, Average = 119ms

I typically get a "Good" connection most days.

[KSarv]

Commenting to keep this thread relevant and the fire going. Still experiencing major lag and packet loss today. One measly update with a link to a support ticket from over a year ago. Going to cancel my sub until this fixed. I'd encourage others to do the same.... money talks.

[CosmicDare]

Still lag/issues. Rubberbanding, startstops, freezing. I've been disconnected once from all this mess and BF in the same house as me has actually crashed over it.

I've sent in my tracert to SE via their form they eventually provided, and provided a tracert to ATT support along with a link to this thread because this is just an overwhelming amount of evidence for them, and I think everyone trying to solve this deserves major props!

My tracert shows timeouts right after the sacramento node, coinciding with everyone here. ATT Fiber user here of course.
8 12 ms 12 ms 12 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
9 28 ms 36 ms 30 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
10 27 ms 26 ms 27 ms ae-1.r20.dllstx14.us.bb.gin.ntt.net [129.250.3.54]
11 104 ms 103 ms 104 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
12 121 ms 135 ms 113 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 116 ms 113 ms 113 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 113 ms 114 ms 113 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 113 ms 112 ms * 204.2.29.122
17 113 ms * 113 ms 204.2.29.122

:< I.. really hope this is fixed by 6.4 but I am highly doubting it only b/c ti's been going on at least since saturday for me and they haven't even publicly acknowledged an issue until yesterday :/

[Aelius]

Writing to mention that I sent in my traceroute through their form. Also an AT&T customer... also still frustrated with SE's decision to move the servers from Montreal to Cali as someone living on the east coast and forever condemning me to use a vpn just to play this game as intended.