Bad lag again with NTT's NA server network

[Lofu]

You weren't the only one to crash, though there's speculation we're being DDOS'd over and over again.

[MsMisato]

sorry someone tripped over the power cable

[iGyro]

they are looking into it-if you look in other threads you might find a link to submit information to SE consisting of: your ISP, country, times it occurs, frequency and traceroute to server.

I don't mean to sound rude towards you in any manner, but there's a lot of us who has probably submitted that information already.

This has been an on-going issue with NTT since May 2023 and the ISP has even tried to shift the blame onto other ISPs for their faulty server nodes. I've spoken with someone, who used to work in the ISP technical side, the other night in Novice Network and they told us first-hand experiences of how horrible NTT's technicians were to deal with over the phone from the corporate side. So, even if we did provide all of our information to Square Enix and help them finally catch up to speed with this thread, the only two solutions in this manner is either:
1. Put a boot up NTT's backside and actually get them to address their horrible network node(s) in the San Fransisco area. (San Jose / Sacremento nodes specifically)
2. Reconsider their contract with NTT and find a new server provider / location for the servers.

[StormyDays]

During today's DDOS on NA servers (and worldwide) I did a route test to my home server (Siren) and found nearly all of NTT's nodes on the route in this test had upwards of 95+% packet loss. As it appears it was a worldwide DDOS for FFXIV, I would look to NTT (FFXIV's service provider) with insufficient security overall. Although it is a small usage case scenario, any data helps I guess. First NTT host in my route was in Georgia and was not affected during the attack.

Unaffected NTT hosts (0-1% packet loss):

ntt.atl04.atlas.cogentco.com (assuming a transfer here from cogentco to NTT)
ae-5.r24.atlnga05.us.bb.gin.ntt.net
ae-1.a05.asbnva02.us.bb.gin.ntt.net

Problem NTT hosts (95+% packet loss):

ae-4.r25.asbnva02.us.bb.gin.ntt.net (DDOS likely started here or at a prior host in NA)
ae-0.r24.asbnva02.us.bb.gin.ntt.net
ae-2.r24.snjsca04.us.bb.gin.ntt.net
ae-4.a00.scrmca03.us.bb.gin.ntt.net
xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net

[DariRyusei]

As of right now, latency is coming in erratic, unpredictable moments. Sometimes it'll be fine, but then suddenly it'll be like a three to five second delay on actions. This will last for a few seconds and then it will go back to normal.

Not to mention that it actually took about five full MINUTES for the forums to load after I tried to log in. It usually takes a while because it auto-redirects to the Japanese forums (and I'm in the US, so that's a long way for data to have to travel), but this time I actually had to leave the page open and just check on it later.

[Greyhawk]

Still a problem - got dropped and now it's throwing the HTTPS errors, and now it cannot validate the certificate for the login client. This has been a horrible experience for me since at least this expansion, and only gets worse. Also an ATT fiber customer here, so yeah...

[ShizuForever]

when are you gunna fire those shitty NTT hosting more like ghosting?
im paying a sub and paying for a VPN (no VPN = 500 ping) and still im not able to play
its like i have zero expectations already and still im somehow let down
how is this even possible
i asked my ISP back in may what's wrong cuz i cant have these disconnects and deal with queue times every minute during DT launch and they said NTT said "we might fix the underwater cables by july"
and guess what? the same problems persist until now
i originally thought the previous few days were isolated incidents but im starting to see a pattern here
its awlays during peak hours when it dies


10 196 ms 159 ms 159 ms ntt-ic-323771.ip.twelve99-cust.net [62.115.12.53]
11 * * * Request timed out.
12 159 ms 159 ms 159 ms ae-1.a03.snjsca04.us.bb.gin.ntt.net [129.250.2.191]
13 * * * Request timed out.
14 160 ms * * ae-6.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.158]
15 166 ms 166 ms 165 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 161 ms 159 ms 159 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 166 ms * * 204.2.29.241
18 163 ms 162 ms 162 ms 204.2.29.7

[mayanyamano]

I've been having the same latency issues as described by others for multiple weeks now, with a break last night, and it beginning again in full force earlier this evening. I've run tracerts on my PC (with wi-fi) and my wife's PC (with ethernet) and both computers have issues with particular nodes in California. I've submitted information to the support website linked to by Okieeomi but am beginning to feel rather bummed about the situation. Especially after all the steps I've taken in the last couple weeks to ensure the best possible connection I can get.

1 9 ms 17 ms 32 ms [redacted]
2 16 ms 19 ms 13 ms [redacted]
3 24 ms 138 ms 48 ms [redacted]
4 20 ms 18 ms 18 ms [redacted]
5 21 ms 21 ms 20 ms [redacted]
6 55 ms 32 ms 422 ms [redacted]
7 18 ms 44 ms 24 ms [redacted]
8 15 ms 14 ms 15 ms ae-9.a02.sttlwa01.us.bb.gin.ntt.net [129.250.66.105] <- beginning of NTT nodes
9 16 ms * * ae-2.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.94]
10 * 36 ms * ae-3.r25.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 * * * Request timed out.
12 38 ms 47 ms 94 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 59 ms 38 ms 38 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 37 ms * * 204.2.29.241
15 35 ms 35 ms 37 ms 204.2.29.8


I had the opportunity to do a video interview with an SE representative at PAX West. I wish I would have thought to bring this up during that interview, too.... the glowing review of the game I gave doesn't quite describe how it feels to play right now.

[Anida]

Greetings,

We are aware that some players have been experiencing network-related issues (such as a few seconds of network loss, lag, or disconnects) over the past few days when playing on the North American data centers.

<snip>

Additionally, as mentioned in the announcement, even if we are unable to request investigations from some of the ISPs from our end, the situation may be improved if players can contact their internet service provider and share their details and issues directly with them.

We appreciate your cooperation as we continue striving to address network-related issues that players may be experiencing.

Have you ever tried to talk to AT&T support?
It's like trying to pull your own teeth... with a pair of tweezers.

[Zahbi]

Bumping this because I've suddenly started having problems with this yesterday afternoon. According to tracert, everything seems normal until NTT's Sacramento 03 data center.

1 <1 ms <1 ms <1 ms RT-AX82U-EE18 [192.168.50.1]
2 6 ms 4 ms 3 ms 50-104-64-1.prtg.in.frontiernet.net [50.104.64.1]
3 2 ms 4 ms 4 ms 184.19.246.62
4 5 ms 6 ms 8 ms ae8---0.scr03.chcg.il.frontiernet.net [74.41.143.152]
5 6 ms 6 ms 6 ms ae0---0.cbr05.chcg.il.frontiernet.net [45.52.201.105]
6 7 ms 6 ms 6 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
7 6 ms 6 ms 13 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
8 8 ms 8 ms 8 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
9 8 ms * 19 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 * * * Request timed out.
11 118 ms 116 ms 116 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 66 ms 64 ms 64 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 63 ms 62 ms * 204.2.29.241
14 64 ms 64 ms 64 ms 204.2.29.9


My ping is normally around 65ms, but this issue has doubled my ping. I've already submitted a report, but I'm just frustrated.

ETA: There were some issues with their San Jose data center as well. I forget which one exactly, as now it doesn't even respond in tracert and just goes straight to Sacramento 03.