Bad lag again with NTT's NA server network

[ArcadiaP]

I don't know what the eff is going on with Square and NTT and this routing, but it's unbearable, and I say that as someone who is nearly 100% of the time Mudfish VPN'd into the game. I decided not to and was greeted with the absolute worst 110ms ping behavior I've ever seen. Why is this still an issue for literally anyone?

Mudfish Statistics
1 <1 ms <1 ms <1 ms [Redacted]
2 57 ms 58 ms 59 ms [Redacted]
3 60 ms 59 ms 60 ms [Redacted]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 57 ms 59 ms 60 ms lo0-0.gw3.scz1.us.linode.com [173.230.159.133]
8 60 ms 59 ms 59 ms ae56.r11.sjc01.ien.netarch.akamai.com [23.203.158.50]
9 61 ms 61 ms 58 ms ae-11.a03.snjsca04.us.bb.gin.ntt.net [140.174.28.105]
10 * * * Request timed out.
11 62 ms 69 ms 61 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 62 ms 63 ms 63 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 63 ms * 63 ms 204.2.29.241
14 64 ms 63 ms 63 ms 204.2.29.94

And Native Networking Statistics
1 <1 ms <1 ms <1 ms [Redacted]
2 <1 ms <1 ms <1 ms [Redacted]
3 5 ms 3 ms 3 ms [Redacted]
4 4 ms 3 ms 4 ms [Redacted]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 12 ms 11 ms 11 ms [Redacted]
9 13 ms 14 ms 11 ms ae-10.r23.chcgil09.us.bb.gin.ntt.net [129.250.3.37]
10 110 ms 124 ms 111 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 114 ms 115 ms 115 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 115 ms 114 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 113 ms * * 204.2.29.241
14 114 ms 115 ms 115 ms 204.2.29.94

What is this nonsense? I haven't kept up with this thread because it's depressing, but I have played without Mudfish before, it has been in the low 60's, but this is beyond unacceptable, once again. Not only does this game have DDOS issues on the weekly, or worse, it can't even manage to have decent routing. Eff off Square.

For those who haven't tried it, honestly Mudfish has been my saving grace. It's cheap, no subscription and I've only paid 10 dollars for what is essentially a whole years worth of VPN'ing. I specifically use this node and it may help you if you're in the East Coast/Midwest (that's more East, like Ohio region). Basic Mode, No Fast Connect, no Full VPN mode, and no WFP item mode. Mudfish Node US West (Fremont, CA -Linode 3). I also read that Cloudflares 1.1.1.1 may also help from a reddit post that's a year old. Mudfish won't help consoles, I feel for you guys, you have to do some black magic routing to fix that stuff.

[Janyd]

Might as well throw in my traceroute as well.

Looks like it's the LA and especially the Sacramento nodes again.

1 <1 ms <1 ms <1 ms REDACTED
2 20 ms 18 ms 18 ms REDACTED
3 19 ms 19 ms 19 ms REDACTED
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 28 ms 27 ms 28 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 29 ms 29 ms 29 ms ae-20.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.114]
10 * 80 ms 55 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 127 ms 116 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 116 ms 116 ms 116 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 116 ms 116 ms 116 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * 115 ms 204.2.29.241
15 115 ms 115 ms 115 ms 204.2.29.122

[Brigh]

I have not had this issue in ages, not since it first got bad at the beginning of this thread lol.
I am actually on AT&T, so the issue is more than just one player ISP. It looks like what its always been, just bad hops from east coast lol.
It only started for me about 3-4 days ago, but has gotten more frequent and more persistent. The packet loss has made PVP almost unplayable since everything rubber bands around.

here is my trace route info. also sent in a support ticket with this bc wowie its bad

Tracing route to 204.2.29.122 over a maximum of 30 hops

1 5 ms 2 ms 5 ms [redacted]
2 6 ms 5 ms 3 ms [redacted]
3 6 ms 4 ms 4 ms [redacted]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms * * 32.130.89.15
8 65 ms 66 ms 69 ms ae-8.a02.atlnga05.us.bb.gin.ntt.net [129.250.8.197]
9 63 ms 64 ms 63 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
10 38 ms 36 ms 33 ms ae-6.r23.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
11 34 ms 35 ms 33 ms ae-18.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.20]
12 * * * Request timed out.
13 129 ms 123 ms 130 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
14 131 ms * 127 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
15 131 ms 124 ms 126 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
16 128 ms * 125 ms 204.2.29.241
17 129 ms 125 ms 123 ms 204.2.29.122


guess I might try going back to vpn playing for the time being

[Janyd]

I might just put down 5 or 10 bucks into Mudfish and see how that compares. Wouldn't hurt to try since it's cheap, and try that Fremont, CA node that was mentioned in another post.

EDIT 2 Hours Later...

So I used Mudfish for a while to see if the lag improved... lo and behold:

1 <1 ms <1 ms <1 ms REDACTED
2 53 ms 54 ms 53 ms REDACTED
3 54 ms 54 ms 54 ms REDACTED
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 55 ms 54 ms 54 ms lo0-0.gw4.scz1.us.linode.com [173.230.159.134]
8 55 ms 54 ms 55 ms ae50.r12.sjc01.ien.netarch.akamai.com [23.203.158.52]
9 54 ms 54 ms 54 ms ae0.r11.sjc01.ien.netarch.akamai.com [23.207.232.32]
10 54 ms 55 ms 55 ms ae-11.a03.snjsca04.us.bb.gin.ntt.net [140.174.28.105]
11 * 57 ms 55 ms ae-6.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.158]
12 79 ms 58 ms 58 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 59 ms 59 ms 59 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * * Request timed out.
15 58 ms 58 ms 58 ms 204.2.29.122

[ArcadiaP]

I honestly hope it keeps helping you. That specific node (and node 2) seem to work the best for me and has been stable since way back when this started, but if things get really bad, it can even affect Mudfish, though if it's that bad, everyone is affected as well. I'm happy it worked though, others tried and did not see improvement.

[Servebotfrank]

I literally made a forum account today to complain about this. The lag has been CONSTANT and makes this game almost unplayable when it happens. I do connection tests every time, My ping is totally fine (11ms, I'm on Fiber), but my connection to Aether is 150ms with packet loss. I can barely play half the time.

[RyuezaneWithersoul]

i joined the fourm when this stuff was starting way back last year. sad that square enix and yoshi p don't wanna do anything about this problem asking us too send our reports and we never hear an update. always super tone death with them

[Caj]

01 <1 ms <1 ms <1 ms <redacted>
02 <1 ms <1 ms <1 ms <redacted>
03 1 ms 1 ms 1 ms <redacted>
04 1 ms 1 ms 1 ms <redacted>
05 * * * Request timed out.
06 * * * Request timed out.
07 9 ms 10 ms 9 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
08 8 ms * 8 ms ae-20.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.114]
09 38 ms * * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 91 ms 89 ms 90 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 98 ms 91 ms 89 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 91 ms 96 ms 99 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * 96 ms 98 ms 204.2.29.241
14 96 ms 95 ms 98 ms 204.2.29.82

[ashekheiron]

Just popping in to say that this is still happening to me at peak hours PST, and the packet loss is absolutely unbearable. This occurs generally starting at 5:30 PM PT and starts to clear up (if I'm lucky) by 7:30 PM or 8 PM PT. It's like playing on a powerpoint at times. I had this issue back in May and I would wager to bet it's worse now.

I don't have an accurate traceroute (will update when this inexplicably happens again), but this is what NORMAL ping looks like:

1 <1 ms <1 ms <1 ms <redacted>
2 3 ms 3 ms 2 ms <redacted>
3 2 ms 2 ms 2 ms <redacted>
4 * * * Request timed out.
5 * * * Request timed out.
6 6 ms 5 ms 6 ms ae-13.a04.snjsca04.us.bb.gin.ntt.net [129.250.9.184]
7 7 ms 17 ms 14 ms ae-0.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.122]
8 9 ms 9 ms 9 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
9 10 ms 10 ms 9 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
10 10 ms 9 ms 9 ms 204.2.29.241
11 8 ms 8 ms 9 ms 204.2.29.122

This is what occurs when during the above times:

1 <1 ms <1 ms <1 ms <redacted>
2 3 ms 3 ms 3 ms <redacted>
3 3 ms 2 ms 3 ms <redacted>
4 * * * Request timed out.
5 * * * Request timed out.
6 56 ms 56 ms 64 ms ae-13.a04.snjsca04.us.bb.gin.ntt.net [129.250.9.184]
7 68 ms 58 ms 73 ms ae-0.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.122]
8 61 ms 60 ms 65 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
9 61 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
10 60 ms 60 ms 60 ms 204.2.29.241
11 60 ms 60 ms 59 ms 204.2.29.122
video evidence: https://streamable.com/sprx8u

I swapped from Xfinity to AT&T because of this very reason. I am anticipating the upcoming ultimate, Futures Rewritten, with my static at 5 PM PT on the weekdays, but as it stands, I'll be griefing prog. It's unacceptable.

Does anyone know if Xfinity has been consistently better

[Krojack]

Yes it's broken.... again. I just happened to look at my ping graphs.

Ping times. My VPN route doesn't go though the AT&T connection at NTT.
Red & Green = straight connection
Purple & Green = VPN connection.


Packet loss