Bad lag again with NTT's NA server network

[Wryneck]

Anyone still getting issues? Feel like I'm the only one still with the same issues since Tuesday, still tons of delay on stuff. Most of my friends issues have been resolved.

Just had my game crap the bed a few minutes ago, casts dropping left and right, several second long hang ups into the game just booting. Reclears have been impossible this week because of it. Been like this for about a week now.

[Sorjal]

Traceroute to NA Center as instructed and to Exodus server IP. From MA via Xfinity/Comcast. This is why I can't even think about trying savage content, as I already have too many instances of getting hit by mechanics that I've avoided on my PC screen. Around 9pm EST but this happens all the time, even 4-5 am EST on weekdays. It's reached a point where I have to watch to see if crafting actions complete when using keybinds, as I've messed up some when just going by rhythm.

2 13 ms 11 ms 18 ms 96.120.64.125
3 12 ms 13 ms 13 ms 24.124.210.93
4 20 ms 15 ms 13 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 20 ms 19 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 16 ms 16 ms 21 ms 75.149.231.250
7 37 ms 37 ms 37 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102] + 16-21 ms from Comcast to NTT
8 82 ms 83 ms 87 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] + 45-50 ms within NTT
9 87 ms 83 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 84 ms 89 ms 85 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 86 ms 90 ms 88 ms 204.2.29.122

2 16 ms 25 ms 13 ms 96.120.64.125
3 11 ms 11 ms 17 ms 24.124.210.93
4 15 ms 22 ms 15 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 21 ms 17 ms 19 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 20 ms 19 ms 19 ms 75.149.231.250
7 36 ms 40 ms 36 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102] + 16-20 ms from Comcast to NTT
8 90 ms 83 ms 89 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] + 43-54 ms within NTT
9 91 ms 93 ms * ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 89 ms 88 ms 92 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 86 ms 95 ms 87 ms 204.2.29.83

And snippet of Resource Monitor:



Traceroute, Sun 6-18-23 11:15p EST

2 14 ms 11 ms 11 ms 96.120.64.125
3 13 ms 11 ms 11 ms 24.124.210.93
4 18 ms 15 ms 17 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 18 ms 15 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 15 ms 15 ms 17 ms 75.149.231.250
7 36 ms 35 ms 63 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 82 ms 81 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 85 ms 83 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 86 ms 88 ms 87 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 84 ms 83 ms 83 ms 204.2.29.122

Traceroute, 6-19-23 4:46a EST (seriously, 4 AM)

2 11 ms 9 ms 12 ms 96.120.64.125
3 10 ms 9 ms 11 ms 24.124.210.93
4 14 ms 13 ms 14 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 14 ms 15 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 15 ms 17 ms 15 ms 75.149.231.250
7 35 ms 35 ms 45 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 90 ms 89 ms 79 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 87 ms 83 ms 83 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 86 ms 86 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * 84 ms 204.2.29.241
12 84 ms 83 ms 86 ms 204.2.29.122

6-19-23, 5:00-5:10am est

[Khryseis_Astra]

Going to submit another trace route to SE tonight, because I’m still seeing the same problem.

Sorjal: your trace looks a lot like mine once it gets to NTT. Both of us are seeing issues start at San Jose. Comcast was having trouble the other morning, unrelated to this since I’ve been dealing with this since last Sunday, but all my local numbers are still low. It’s that San Jose node where I see everything quadruple.

[ArcadiaP]

Definitely don't let up as the problem continues to be unresolved.

[Khryseis_Astra]

Still seeing the awful lag... looks like the San Jose node has been removed or rerouted and now the one in LA (?) is acting up? Now I'm starting to get numbers in the hundreds... had a couple hours last night where the lag was minimal, but it came back around midnight again.

8 20 ms 24 ms 18 ms be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
9 29 ms 27 ms 23 ms be-301-cr12.beaumeade.va.ibone.comcast.net [96.110.39.165]
10 31 ms 31 ms 25 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
11 27 ms 27 ms 31 ms be-3412-pe12.ashburn.va.ibone.comcast.net [96.110.34.126]
12 33 ms 33 ms 30 ms ae-18.a04.asbnva02.us.bb.gin.ntt.net [129.250.9.117]
13 35 ms 31 ms 26 ms ae-2.r25.asbnva02.us.bb.gin.ntt.net [129.250.2.124]
14 94 ms 93 ms 84 ms ae-2.r25.lsanca07.us.bb.gin.ntt.net [129.250.3.189]
15 98 ms 100 ms 85 ms ae-1.r24.lsanca07.us.bb.gin.ntt.net [129.250.3.218]
16 89 ms 92 ms 90 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
17 90 ms 145 ms 93 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
18 92 ms 97 ms 89 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 * 90 ms * 204.2.29.241
20 93 ms 98 ms 95 ms 204.2.29.122

[ArcadiaP]

Not sure what's going on, again, but latency has increased 5-8ms more than average. I haven't been playing as much as I usually do, but I did some reclears on Tuesday and had an amazing 58-59ms stable connection. Currently I'm in the 65-69ms range and well, why? This is really dumb.

[n_n]

Not sure what's going on, again, but latency has increased 5-8ms more than average. I haven't been playing as much as I usually do, but I did some reclears on Tuesday and had an amazing 58-59ms stable connection. Currently I'm in the 65-69ms range and well, why? This is really dumb.

Yeah I was getting this too when I was trying my normal connection a couple weeks ago. Going from 58 to 65+ at certain times of the day. I don't experience this on proxy connection, so I've just been playing on that from now on. Especially since I experienced really bad lag for 15 mins straight one time.

Also last night I saw a sizeable amount of people in duty and big city shout chat complaining about really bad lag, 300+ ping, etc. Seems to still be broken for some. I'm surprised this thread has really slowed down now despite that.

[Sorjal]

Square's customer support just told me...

"Hello there,

Thank you for contacting Square Enix Customer Support. Let me assist you with the connection error that you are receiving.

Broadly speaking, connection issues come from three places: your home network, the server, and the route connecting the two. Since everyone connects to the same server or group of servers and we do not have multiple reports of connection issues at this time, we can safely rule the server out. To troubleshoot your home network, we provided the suggestions in our previous response. Since none of those suggestions have resolved the issue, the problem likely does not stem from here. This leaves the route in between as the most likely culprit.

This most likely is caused by congestion or routing issues along the way to the server, causing latency, packet loss, and disconnections. This is sometimes caused by severe weather conditions or technical malfunctions anywhere between a PC/Console and the server, not necessarily around the devices' immediate area.

Unfortunately, we do not have any direct control over how the device is routed to the server so we are unable to resolve this. As such, we would suggest contacting your Internet Service Provider and making a report with them.

You can also submit a report on any connection issues via this link here:
http://sqex.to/vzc

Again, we apologize that we are unable to assist you with this issue further and hope that you can still continue to enjoy the game.
"
... completely ignoring that this thread even exists, or that NTT is Their provider...

[Jeeqbit]

There is a problem with NTT the last few days that I wasn't experiencing at all until now. My ping has increased by 100. All but one of the points on the way to NTT have this extra 100 ping.

Actually it's all over the place. It increases to 400 ping sometimes, then 200, then 300, with occasional packet loss across all the NTT points. Occasionally it's normal. But it is affecting my weaving a lot and very noticeable.

I have tested this on two separate internet connections on two separate ISPs because I actually have two. And both have the problem.

[Yaesrei]

Using Windows Command Prompt to ping Aether it's giving me 380+ms with a 25% drop rate usually. Never had any problems until today about 5 hours ago. Incredibly annoying and makes the game unplayable, hope this is resolved ASAP.