Bad lag again with NTT's NA server network

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.

Also getting some lag and 90002/1'd with Verizon at midnight EST.

It's happening again, 700 people queue on leviathan after the mass disconnects

https://i.gyazo.com/f6776a93476a64cd...6b781a5f4a.png

Surprise, surprise. It looks like another night of bad connections.

Canada here...yup Crystal just got stomped...(though my tracert was via a diff route
)

Server go SPLAT

https://i.imgur.com/q2Pjo0B.png

Same on Primal 7:25pm PST- MASS DC of everyone and now que is 700+ (Server: Hyperion) Was doing M4 and everyone died during first DDoS we waited as some folks came back and then six people got DC icon and BOOM kicked to lobby to wait.

Really wish SE would get a fix on these DDoS - making it very painful on weekends to have fun when most time is getting kicked out of the game.

EDIT: And after waiting for a few minutes kicked out of the game 2002 - thanks. ;(

https://i.imgur.com/rKboDsBh.png

OH WHAT A DAY! WHAT A LOVELY DAY!

Adding to the pile. COMCAST east coast.

Cox east cost, was on Ultros, downstream seemed ok just judging by the numbers in the game UI, but upload kept crashing. Not doing any tracert because I've already done a ton.

Judging by the queue now from trying to log on (+1k in queue) seems the entire server crashed and it wasn't just me.

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

sorry someone tripped over the power cable

Quote:

---

Originally Posted by wizisi2k

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.

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

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.

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...

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

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.

Quote:

---

Originally Posted by Okieeomi

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.

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.

Quote:

---

Originally Posted by 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.

---

I seem to be having same issues with Frontier internet as well.

1 <1 ms <1 ms <1 ms GT-AX11000-7C20 [192.168.8.50]
2 1 ms 2 ms 3 ms 74-32-184-1.dr01.aled.il.frontiernet.net [74.32.184.1]
3 4 ms 3 ms 3 ms ae11---100.car01.lkvl.mn.frontiernet.net [74.36.197.101]
4 15 ms 15 ms 15 ms ae3---0.cor01.lkvl.mn.frontiernet.net [74.40.2.209]
5 15 ms 11 ms 13 ms 74.40.5.50
6 13 ms 14 ms 15 ms ae1---0.cbr05.chcg.il.frontiernet.net [45.52.201.107]
7 12 ms 11 ms 15 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
8 15 ms 13 ms 15 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
9 16 ms 15 ms 19 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
10 15 ms 19 ms 15 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
11 * 117 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 120 ms 124 ms 122 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 136 ms 130 ms 122 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 70 ms * 204.2.29.241
15 121 ms 123 ms 123 ms 204.2.29.9

I also have been having issues with Frontier for the last several days now

1 <1 ms <1 ms <1 ms 192.168.4.1
2 6 ms 7 ms 7 ms 50-104-116-1.prtg.in.frontiernet.net [50.104.116.1]
3 2 ms 4 ms 4 ms ae16---43.car02.ftwy.in.frontiernet.net [184.19.246.60]
4 4 ms 1 ms 4 ms ae1---0.ber01.ftwy.in.frontiernet.net [74.40.3.201]
5 * * 5 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
6 14 ms 8 ms 12 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
7 9 ms 9 ms 8 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
8 12 ms * 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 * 80 ms 73 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 114 ms 115 ms 113 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 115 ms 115 ms 115 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * 114 ms 204.2.29.241
13 114 ms 115 ms 117 ms 204.2.29.122

Another frontier user here. While I don't have a trace for you, I do want to say that I am also getting lag as of a week ago. People running, stopping, running, stopping. People jumping and freezing midair for a second.

Another Frontier user and I've also been subject to horrendous lag making the game basically unplayable.

Same issue here (frontier customer near LA, occurred late on Friday).

[redacted, no issues]
3 6 ms 5 ms 5 ms ae13--400.ber01.snmn.ca.frontiernet.net [184.19.246.106]
4 4 ms 7 ms 7 ms ae9---0.scr03.lsan.ca.frontiernet.net [45.52.201.248]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 62 ms * ae-28.a03.lsanca07.us.bb.gin.ntt.net [129.250.9.93]
8 * * * Request timed out.
9 20 ms 19 ms 19 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 69 ms 68 ms 69 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 17 ms 19 ms 19 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 68 ms 66 ms 67 ms 204.2.29.122

(Update: I did another trace, now both Los Angeles & Sacramento ntt nodes are having issues)
(Update 2: Contacted frontier just in case, and CS said there's nothing wrong but they will make a note of it so that others making the same request regarding the traceroute would know)

Also frontier here


Tracing route to 204.2.29.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 2 ms 4 ms 50-54-32-1.adr01.nrwl.oh.frontiernet.net [50.54.32.1]
3 3 ms 5 ms 2 ms ae3---0.car01.nrwl.oh.frontiernet.net [74.42.150.33]
4 12 ms 12 ms 11 ms ae10---0.scr01.chcg.il.frontiernet.net [74.40.4.169]
5 21 ms 23 ms 16 ms ae0---0.cbr05.chcg.il.frontiernet.net [45.52.201.105]
6 13 ms 11 ms 12 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
7 23 ms 13 ms 13 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
8 14 ms 18 ms 15 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
9 13 ms 14 ms 14 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 116 ms * * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 69 ms 70 ms 69 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 * 122 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * 120 ms 119 ms 204.2.29.241
14 120 ms 121 ms 120 ms 204.2.29.8

Edit: Tried again today and its even worse.

Frontier here Started yesterday

C:\Users\nvick>tracert neolobby08.ffxiv.com

Tracing route to neolobby08.ffxiv.com [204.2.29.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 9 ms 184-14-96-1.dsl1.chtn.wv.frontiernet.net [184.14.96.1]
3 2 ms 2 ms 1 ms 74.40.71.9
4 15 ms 14 ms 14 ms ae9---0.scr04.chcg.il.frontiernet.net [74.40.10.233]
5 18 ms 74 ms 25 ms ae1---0.cbr05.chcg.il.frontiernet.net [45.52.201.107]
6 * 15 ms 15 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
7 16 ms 16 ms 16 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
8 18 ms 19 ms 25 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
9 * * 17 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 * * * Request timed out.
11 73 ms 71 ms 72 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 126 ms 126 ms 126 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 72 ms * * 204.2.29.241
14 71 ms 72 ms 71 ms 204.2.29.8

Trace complete.

My connection to the NA servers seems to be back to normal now. Just giving a heads up if others want to check.

Quote:

---

Originally Posted by Zahbi

My connection to the NA servers seems to be back to normal now. Just giving a heads up if others want to check.

---

Mine is definitely not. :(

+1 to this tread. I am an AT&T Fiber customer based in Texas, USA, and have been experiencing network performance issues since September 2023, and are consistent since the launch of Dawntrail.

I'm getting 3-5+ second delays and dropped inputs, with particularly poor performance in dungeons and PvP instances. VPNs have stopped helping me recently, and I’ve noticed a change in my traceroute from Dallas > California to Dallas > Miami > California, resulting in the worst performance I’ve experienced so far.

I’m attaching my traceroute below and am looking out for an acknowledgment of the issue or an announcement/timeline for the Cloud Data Center. Otherwise, I'll end up cancelling soon. FFXIV is the only service/game I have with these issues so I’m not considering switching ISPs.

Target Name: 204.2.29.82
IP: 204.2.29.82
Date/Time: 9/14/2024 10:46:22 AM - 9/14/2024 10:56:22 AM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 2 0 1.00 1.00 1.00 [redacted]
2 2 0 1.50 1.50 1.50 [redacted]
3 2 0 1.90 1.90 1.90 [redacted]
4 2 100 0 0 0 [-]
5 2 100 0 0 0 [-]
6 2 0 9.91 9.91 9.91 ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
7 2 0 8.49 8.49 8.49 ae-20.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.114]
8 2 100 0 0 0 [-]
9 2 0 36.77 36.77 36.77 ae-0.a02.miamfl02.us.bb.gin.ntt.net [129.250.2.4]
10 2 100 0 0 0 [-]
11 2 100 0 0 0 [-]
12 2 100 0 0 0 [-]
13 2 100 0 0 0 [-]
14 2 0 98.44 98.44 98.44 ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
15 2 0 76.43 76.43 76.43 ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
16 2 0 77.56 77.56 77.56 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 2 0 76.60 76.60 76.60 204.2.29.241 [204.2.29.241]
18 2 0 75.23 75.23 75.23 204.2.29.82 [204.2.29.82]

It's still bad, and continues to be bad daily.

1 <1 ms <1 ms <1 ms <localhost>
2 12 ms 10 ms 12 ms <local>
3 11 ms 10 ms 10 ms <comcast> [68.87.160.205]
4 16 ms 11 ms 10 ms <comcast> [69.139.160.245]
5 13 ms 11 ms 11 ms <comcast> [24.124.128.249]
6 11 ms 11 ms 11 ms <comcast> [68.86.93.9]
7 11 ms 11 ms 11 ms <comcast> [96.110.44.90]
8 19 ms 15 ms 12 ms ae-9.a02.sttlwa01.us.bb.gin.ntt.net [129.250.66.105]
9 20 ms 12 ms 13 ms ae-2.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.94]
10 * * * Request timed out.
11 29 ms 36 ms 29 ms ae-1.a03.snjsca04.us.bb.gin.ntt.net [129.250.2.191]
12 * * * Request timed out.
13 * 30 ms 31 ms ae-6.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.158]
14 32 ms 35 ms 34 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
15 39 ms 32 ms 33 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
16 * * 33 ms 204.2.29.241
17 32 ms 39 ms 32 ms 204.2.29.89

Daily issues. Major rubberbanding every 10 or so mins. Negatively affecting endgame content progression.

1 1 ms 1 ms 1 ms
2 10 ms 11 ms 13 ms
3 13 ms 11 ms 27 ms <comcast> [68.86.137.201]
4 29 ms 13 ms 16 ms <comcast> [68.85.171.5]
5 23 ms 14 ms 12 ms <comcast> [68.85.171.14]
6 20 ms 11 ms 15 ms <comcast> [96.110.97.41]
7 21 ms 21 ms 19 ms <comcast> [162.151.94.93]
8 26 ms 25 ms 26 ms <comcast> [96.110.43.85]
9 26 ms 24 ms 27 ms <comcast> [96.110.33.182]
10 24 ms 27 ms 32 ms 71.25.197.82
11 40 ms 35 ms 35 ms ae-5.r24.atlnga05.us.bb.gin.ntt.net [129.250.4.192]
12 * * * Request timed out.
13 60 ms 44 ms 38 ms ae-1.a05.asbnva02.us.bb.gin.ntt.net [129.250.3.244]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 93 ms 89 ms 108 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
18 89 ms 91 ms 90 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 89 ms 85 ms 89 ms 204.2.29.241
20 88 ms 90 ms 86 ms 204.2.29.122

Is it me or this issue been more worse. ever since Dawntrail started? it always feels where always under a ddos like every month now. kind of annyoing that NTT won't fix their nodes at all :(

Quote:

---

Originally Posted by RyuezaneWithersoul

Is it me or this issue been more worse. ever since Dawntrail started? it always feels where always under a ddos like every month now. kind of annyoing that NTT won't fix their nodes at all :(

---

Yeah my group's been getting shit on tonight trying to do M2S and my BLM and PLD keep DCing due to the DDoS. When is XIV going to do something about this? Because it's kinda ridiculous that they're being disrupted almost on the daily now since normally they would've already dealt with it.

Another Comcast user here. Still bad. So frustrating.

Re-posting due to having issues with connectivity to this game once again, since yesterday. My ISP is also Comcast. I've run a couple tracert's throughout the night and it seems to be the 10th and 12th node consistently that have issues for me. I have not tried combat, but I have been disconnected at least once per hour while trying to quick synth or relax at my house.

I will share this information via the support portal as well.

Tracing route to 204.2.29.94 over a maximum of 30 hops

1 3 ms * * 10.0.0.1
2 29 ms 40 ms 39 ms [redacted]
3 23 ms 23 ms 23 ms [redacted]
4 31 ms 19 ms 17 ms [redacted]
5 18 ms 21 ms 21 ms [redacted]
6 19 ms 21 ms 21 ms [redacted]
7 19 ms 21 ms 23 ms [redacted, beginning of NTT nodes]
8 34 ms 24 ms 23 ms ae-9.a02.sttlwa01.us.bb.gin.ntt.net [129.250.66.105]
9 33 ms 30 ms 22 ms ae-2.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.94]
10 * * 42 ms ae-3.r25.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 37 ms 35 ms 62 ms ae-1.a03.snjsca04.us.bb.gin.ntt.net [129.250.2.191]
12 * * * Request timed out.
13 54 ms 62 ms 54 ms ae-6.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.158]
14 55 ms 48 ms 41 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
15 45 ms 48 ms 43 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
16 44 ms 55 ms 39 ms 204.2.29.241
17 40 ms 43 ms 68 ms 204.2.29.94

My VPN no longer reliably fixes this node/routing issue since a week ago. The game becomes unplayable around ~10PM and/or 1AM+ EST every night. It's the same crap I experienced since June 2023.
I'm really enjoying endgame stuff and I really want to learn another ultimate, but my playtime is usually around these hours so I can't do any of that.
Very frustrating. I'm tired of messing with VPNs just to play this game that I'm already paying a subscription for.

Suddenly getting very bad lag again out of no where. 8pm EST

1 <1 ms <1 ms <1 ms [redacted]
2 10 ms 12 ms 10 ms [redacted]
3 24 ms 15 ms 31 ms [redacted]
4 13 ms 14 ms 12 ms [redacted]
5 16 ms 16 ms 18 ms [redacted]
6 25 ms * * lag-415.asbnva1611w-bcr00.netops.charter.com [107.14.18.106]
7 28 ms 48 ms 26 ms lag-0.pr2.dca10.netops.charter.com [66.109.5.117]
8 22 ms 26 ms 27 ms ash-b2-link.ip.twelve99.net [62.115.188.210]
9 21 ms 21 ms 23 ms ae-40.a08.asbnva02.us.bb.gin.ntt.net [129.250.8.18]
10 * * * Request timed out.
11 21 ms 24 ms 27 ms ae-1.a05.asbnva02.us.bb.gin.ntt.net [129.250.3.244]
12 * * * Request timed out.
13 * 26 ms * ae-0.r24.asbnva02.us.bb.gin.ntt.net [129.250.3.243]
14 * 263 ms * ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 836 ms 832 ms 783 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 658 ms 693 ms 655 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * 695 ms 684 ms 204.2.29.241
18 93 ms 83 ms 87 ms 204.2.29.8

Trace complete.

Target Name: 204.2.29.82 IP: 204.2.29.82 Date/Time: 9/29/2024 8:53:23 PM - 9/29/2024 9:03:23 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 28 0 0.31 3.39 0.60 redacted [redacted]
2 28 0 0.46 5.61 1.15 redacted [redacted]
3 28 0 1.29 2.45 1.69 redacted [redacted]
4 28 0 1.43 2.78 2.17 redacted [redacted]
5 27 100 0 0 0 [-]
6 15 80 7.14 8.29 7.68 32.130.24.47 [32.130.24.47]
7 28 0 9.59 21.00 10.34 ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
8 28 0 8.07 11.36 8.77 ae-20.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.114]
9 22 64 37.40 175.77 95.42 ae-2.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.218]
10 28 50 36.86 77.33 41.45 ae-0.a02.miamfl02.us.bb.gin.ntt.net [129.250.2.4]
11 27 100 0 0 0 [-]
12 19 89 37.60 37.95 37.78 ae-0.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.5]
13 27 100 0 0 0 [-]
14 23 70 66.89 70.38 68.16 ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
15 28 0 76.69 89.50 78.51 ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
16 28 0 76.51 95.02 78.28 ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
17 28 0 76.97 78.15 77.40 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
18 28 71 76.50 80.06 77.48 204.2.29.241 [204.2.29.241]
19 28 0 76.27 78.09 76.85 204.2.29.82 [204.2.29.82]