Bad lag again with NTT's NA server network

[LuminosSolis]

Same east coast player myself used to excellent connection all the time on att fiber now the game is unplayable tried different data centers same results

[TaleraRistain]

Here's that section on my friend, not sure if Dallas, but in Texas with Optimum. Not hitting that same node we're all showing issues with.

7 * * * Request timed out.
8 58 ms 52 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 54 ms 56 ms 56 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 61 ms 79 ms 54 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 54 ms 54 ms 54 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 59 ms * 204.2.29.241
13 55 ms 57 ms 53 ms 204.2.29.6

This is also mine last night around 3 or 4 am when things were smooth enough to play. But nowhere near that same jump they're trying to say is expected going from Texas to Sacramento for that same node at that time.

8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 68 ms 55 ms 57 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 59 ms 61 ms 59 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 60 ms 59 ms 59 ms 204.2.29.6

[Ath192]

Here's that section on my friend, not sure if Dallas, but in Texas with Optimum. Not hitting that same node we're all showing issues with.

7 * * * Request timed out.
8 58 ms 52 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 54 ms 56 ms 56 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 61 ms 79 ms 54 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 54 ms 54 ms 54 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 59 ms * 204.2.29.241
13 55 ms 57 ms 53 ms 204.2.29.6

This is also mine last night around 3 or 4 am when things were smooth enough to play. But nowhere near that same jump they're trying to say is expected going from Texas to Sacramento for that same node at that time.

8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 68 ms 55 ms 57 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 59 ms 61 ms 59 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 60 ms 59 ms 59 ms 204.2.29.6

Well actually I can't hit 128.241.2.18 without dropping packets so. To me what NTT said is true and it's on ATTs side. I also don't go through node 57.

Like, its very well true that the drops are probably happening when ATT hands off the traffic to NTT but the equipment that's doing the hand off must be the problem and not the NTT equipment receiving it. Otherwise like in the previous post the NTT tech would've had problems pinging their own equipment in sacramento, which he didn't. Further more, the Optimum connection listed here passes through NTT with no issue right, and it passes through the node I am dropping packets on.

To me this is ATT.

Here is mine, by all accounts its awfully similar to the Optimum in Texas with no issues.

4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 28 ms 31 ms 31 ms 32.130.25.67
8 26 ms 27 ms 27 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * * * Request timed out.
10 108 ms 114 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 152 ms 117 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 117 ms 117 ms 116 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 118 ms 118 ms 118 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 118 ms 119 ms 204.2.29.241
15 117 ms 118 ms 117 ms 204.2.29.87

Trace complete.

[texas_boy]

Hadn't had any issues until this evening. ATT in Central Texas being routed through Dallas.

Tried going through Proton VPN and found that I don't have the random and frequent disconnects - guess I'll use that until ATT can get their stuff figured out.

[LinaGiggles]

This is what I got when I did ticket and such. I don't know if I should even make new thread or just at least post here on this update.

Greetings,

Thank you for keeping in touch with the SQUARE ENIX Support Center.

We apologize for the confusion and inconvenience you are still having experience with. Unfortunately this is a known issue, at the moment is under investigation and procedure, we advise to please report this on the forum as a bug and to stay on the lookout for any update on the Lodestone. We can only ask for you patience for the time being.

We thank you for understating this matter. If you ever need further assistance, do not hesitate to contact us. Have a great day and please take care.

Thank you,
Veronica
SQUARE ENIX Customer Support
_____________
If you need any additional assistance with this concern, please reply to this email directly. If you need assistance with a new concern, please visit the SQUARE ENIX Support Center and submit a new support ticket at: https://support.na.square-enix.com. Additionally, we have a survey that you may fill out to provide your customer service feedback and suggestions once your ticket has been closed.

[Jonobang]

I am midwest NA,

Tracing route to 204.2.29.122 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 20 ms 22 ms 20 ms 76-255-24-1.lightspeed.mdsnwi.sbcglobal.net [76.255.24.1]
3 20 ms 21 ms 20 ms 76.229.12.62
4 * * * Request timed out.
5 26 ms 33 ms 28 ms 32.130.17.75
6 25 ms 30 ms 30 ms cgcil402igs.ip.att.net [12.122.133.161]
7 75 ms 76 ms 74 ms 192.205.32.194
8 75 ms 75 ms 79 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 91 ms 80 ms 78 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 * 132 ms 131 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 133 ms 132 ms 133 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 131 ms 132 ms 204.2.29.241
13 132 ms * 132 ms 204.2.29.122

Trace complete.


My traceroute results, hope they fix it soon

[Allison_Grimvault]

Lag is as bad as ever STILL and on the 3rd day. Game is unplayable.

[Janyd]

Thanks for sharing the ticket reply from SE, Lina.

Yes, you can use this forum thread to keep the reports and traceroutes coming.

The best we can do is keep doing what we're doing here, and if you want to use a VPN as a temporary workaround, I highly recommend you do so if you can spare the cash.

[LinaGiggles]

Thanks for sharing the ticket reply from SE, Lina.

Yes, you can use this forum thread to keep the reports and traceroutes coming.

The best we can do is keep doing what we're doing here, and if you want to use a VPN as a temporary workaround, I highly recommend you do so if you can spare the cash.

Yeah for now ..I got VPN.. I shouldn't have to or any of us shouldn't have to but its best way I can play for now. :S <3 Thanks for the suggestion.

[Janyd]

Yeah for now ..I got VPN.. I shouldn't have to or any of us shouldn't have to but its best way I can play for now. :S <3 Thanks for the suggestion.

I completely agree. It's not the ideal workaround, and none of us here should have to use it all the time, but it's at least a workaround. For now.

Ideally, things will get sorted ASAP.

As for those Spectrum and AT&T traceroutes... guess this means the node situation between Dallas and California is worse than we thought, if I'm reading this right.