Bad lag again with NTT's NA server network

[DarthKamen]

Sorry if this has been said before, but this is a large thread, and searching it shows nothing. I have T-Mobile internet, not AT&T. Since yesterday morning I have had horrible lag followed by disconnection, rendering it unplayable (I am on console). Traceroute shows NTT as being the issue, as many seem to point out. So it is affecting more than just AT&T users.

I just wanted to put this out there somewhere official.

[Integro]

Sorry if this has been said before, but this is a large thread, and searching it shows nothing. I have T-Mobile internet, not AT&T. Since yesterday morning I have had horrible lag followed by disconnection, rendering it unplayable (I am on console). Traceroute shows NTT as being the issue, as many seem to point out. So it is affecting more than just AT&T users.

I just wanted to put this out there somewhere official.

T-Mobile at some point likely hops into ATT fiber. I have Dish, they utilize ATT fiber network, my tracer routes show ATT in the hop chain. My ping and packet loss begin on the 8th hop to the NTT Sacramento node.

[DarthKamen]

T-Mobile at some point likely hops into ATT fiber. I have Dish, they utilize ATT fiber network, my tracer routes show ATT in the hop chain. My ping and packet loss begin on the 8th hop to the NTT Sacramento node.

Ah that makes sense, thank you. I'm not very versed in how this stuff works.

[Gymoz]

Replying here for extra traction.

I have ATT Fiber with ExitLag set to San Jose(1). Early morning, ping is 70s. Noon to Evening, ping is 115-125.

SE please get in contact with NTT so we can actually play the game, thanks.

Here is the contact form for NTT.

[synthrian]

Getting this issue on Mediacom as well. I can mostly stay connected during the day but I noticed the past couple nights around 8pm Central it's literally unplayable and I can barely stay connected for 5 mins. Too bad that's when my static plays Have tried various nodes on Mudfish, Nord and Exitlag, as well as CF. Going to give PIA a shot tonight but I'm not optimistic.

[Monochii]

Hey still having the same issues as everyone else. No difference with connection with nearly 100% packet loss on the NTT servers end. Having no issues outside of FFXIV....

This maybe the hopium speaking but I feel positive about the latest update from Square yesterday.

"the teams did find that connection quality was degrading at certain points on the Internet, depending on the connection used to reach the servers."

"we are working with the network carriers that are directly connected to our servers to resolve the issue,".

From what I'm understanding this means they at least see what we've all been seeing with the issues on NTT servers end and are speaking to them to resolve it. It is always a good idea to double check with your ISP to make sure that your connection to the internet is as solid as possible, even though that is clearly not what is wrong here.

Really all we can do at this point is keep submitting the Tracert reports and honestly keep pressure Square on this forum and any other social media platform to keep them aware that this is still a major problem that needs to be fixed.

If you really have to play you can use a VPN as a workaround. Don't stop keeping the pressure on Square though. This is NOT a fix from Square and we shouldn't have to ourselves find ways to fix the issue. We as the consumer should only have to consume the product we pay for.

[Janyd]

Hey still having the same issues as everyone else. No difference with connection with nearly 100% packet loss on the NTT servers end. Having no issues outside of FFXIV....

This maybe the hopium speaking but I feel positive about the latest update from Square yesterday.

"the teams did find that connection quality was degrading at certain points on the Internet, depending on the connection used to reach the servers."

"we are working with the network carriers that are directly connected to our servers to resolve the issue,".

From what I'm understanding this means they at least see what we've all been seeing with the issues on NTT servers end and are speaking to them to resolve it. It is always a good idea to double check with your ISP to make sure that your connection to the internet is as solid as possible, even though that is clearly not what is wrong here.

Really all we can do at this point is keep submitting the Tracert reports and honestly keep pressure Square on this forum and any other social media platform to keep them aware that this is still a major problem that needs to be fixed.

If you really have to play you can use a VPN as a workaround. Don't stop keeping the pressure on Square though. This is NOT a fix from Square and we shouldn't have to ourselves find ways to fix the issue. We as the consumer should only have to consume the product we pay for.

Exactly this. Also, nothing wrong with "Hopium" in my book. It beats hopeless cynicism and the "we are nothing" bull going around.
Despair is for cowards, and that is not my style.

Use a VPN as a workaround if you must, or 1.1.1.1 (Cloudflare Warp) if you can get it to work, but keep the pressure on 'em.

Lest we forget, keep sending your Traceroutes and Pings to this form: https://secure.square-enix.com/enqt3...NETWORK_N/html

[Rekts]

I don't mean to jinx it, but for whatever reason my connection seems fine atm?

[ArcadiaP]

Doing a trace route through my router as I'm currently on with Mudfish, yes, the ping is 60ms which is what I expect from my connection and distance to California. Looks like a solid 58-60ms Ping to XIV currently.

Hrothgar, where art thou to share your neat graphs with us.

[brnslpy]

Traceroute at 19:14 EDT:

 6  32.130.17.77 (32.130.17.77)  7.822 ms  7.141 ms  8.617 ms
 7  cgcil402igs.ip.att.net (12.122.132.197)  9.774 ms  15.007 ms  7.826 ms
 8  192.205.32.194 (192.205.32.194)  9.523 ms  7.111 ms  7.090 ms
 9  ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239)  9.029 ms  9.135 ms  7.508 ms
10  ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17)  54.301 ms  54.236 ms  54.171 ms
11  * * *
12  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18)  57.854 ms  57.579 ms  57.414 ms
13  * 204.2.29.241 (204.2.29.241)  57.276 ms *
14  204.2.29.96 (204.2.29.96)  57.456 ms  56.810 ms  56.713 ms

MTR at 19:17 EDT:

 6. 32.130.17.77                                      0.0%     9   10.1  10.5   7.8  13.6   2.2
 7. cgcil402igs.ip.att.net                            0.0%     9    7.7  11.0   7.7  14.2   2.2
 8. 192.205.32.194                                    0.0%     9   12.6  12.3   7.8  23.4   4.7
 9. ae-4.r23.chcgil09.us.bb.gin.ntt.net               0.0%     9    8.1  13.9   7.7  59.3  17.1
10. ae-1.r24.snjsca04.us.bb.gin.ntt.net              77.8%     9   54.4  54.3  54.2  54.4   0.1
11. ae-4.a00.scrmca03.us.bb.gin.ntt.net              11.1%     9   57.0  63.6  57.0  93.4  13.3
12. xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net         0.0%     9   57.5  57.5  57.3  57.7   0.1
13. 204.2.29.241                                     87.5%     8   57.1  57.1  57.1  57.1   0.0
14. 204.2.29.96                                       0.0%     8   57.0  56.9  56.6  57.2   0.2

EDIT: Added an MTR coming from same physical location but going through a VPN and same routes as above:

 6. be2124.ccr41.ord01.atlas.cogentco.com             0.0%    15    7.9   7.3   7.0   7.9   0.3
 7. be2765.ccr41.ord03.atlas.cogentco.com             0.0%    15    7.5   7.8   7.2  13.1   1.5
 8. ae-11.a06.chcgil09.us.bb.gin.ntt.net              0.0%    15    8.9  10.2   6.9  16.4   2.8
 9. ae-10.r23.chcgil09.us.bb.gin.ntt.net              0.0%    15   16.8   9.0   6.7  16.8   3.0
10. ae-1.r24.snjsca04.us.bb.gin.ntt.net              50.0%    14   54.3  57.3  53.8  69.5   6.0
11. ae-4.a00.scrmca03.us.bb.gin.ntt.net              30.8%    14   57.2  58.5  57.2  63.0   1.9
12. xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net         0.0%    14   57.7  57.9  57.5  58.2   0.2
13. 204.2.29.241                                     92.3%    14   57.3  57.3  57.3  57.3   0.0
14. 204.2.29.96                                       0.0%    14   57.2  58.1  56.8  67.3   2.9

Yeah these numbers are a lot different than what we've been seeing. Fingers crossed maybe they fixed it before they go away for holiday weekend.