Bad lag again with NTT's NA server network

[Janyd]

The report form says "an unexpected error has occurred" in japanese to me.

I refreshed the page a couple times, and went back to resubmit the form, and it went through fine.

Try filling out the form in another browser if possible, and make sure if you're using a VPN to deactivate it for a minute or two, just in case that's causing any conflicts.

[TomsYoungerBro]

Glad SE saw this finally . Maybe they can get this handled before 6.4

[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

[Zab]

Did SE change actual data centers during the NA upgrade earlier this month.

There is definitely congestion at the interconnect between AT&T and NTT. It could be hardware on either side. Since I had almost no packet loss this morning (PDT) and a 40ms ping time, but by lunch time that ping had doubled and the packet loss was at 15%. It's very possible that the number of accounts returning to the game have pushed the networking hardware over its functional limit.

Speculating, the problems may be business issues rather than technical. They know where the weak hardware is and need to upgrade it. Well, does the contract allow higher traffic to be passed? If not, what does it take to amend the contract.

And if new hardware is needed, do they (AT&T or NTT) have it available? Do they have to order it before they can install it? Who's budget is it coming out of? And so on. It may take awhile to fix.

And I just saw the twitter post admitting to the problem and asking for more information. I suspect they are just trying to appear to be doing something here.

I use sonic.net as my ISP. Unfortunately, they use AT&T for their service around here (since they haven't brought in their own fiber yet). So I see the issues with the AT&T/NTT interconnect. However, Sonic offers free VPN which routes over AT&T to their servers and uses a clean connection to NTT. VPN does add some overhead, but I'm seeing 32ms pings with no packet loss when using it, so I'm set for now.

[TaleraRistain]

Well it seems like ATT is going to have to take the initiative because as far as I know, he told me there WERE issues with ATT, and this is known to them, but that they were fine on their end.

I guess we need someone from Dallas TX that doesn't use ATT to post a trace rt and see if it goes through NTT and see if they are dropping packets. I mean, it would rule them out.

Seeing if a friend of mine who is in Texas and isn't having issues can help us out. She's with Optimum.

[Symon14]

Another way to get to the form, which worked for me, is:

https://support.na.square-enix.com/c...382&la=1&fty=2

Then scroll to the bottom under "Providing information on packet loss" and click Submit Report (after running the tracert instructions).

[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

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

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

[Kestaa]

Im in a pretty unique position for the next few weeks. I have two different internet companies atm (both wireless), Spectrum and Fiber ATT. If interested I can post both of mine if requested.

Edit : here are the results in Central Texas, same computer just switching wireless connections from ATT to Spectrum

ATT Wireless:
Tracing route to 204.2.29.122 over a maximum of 30 hops


5 * * * Request timed out.
6 13 ms 16 ms 23 ms
7 30 ms 12 ms 14 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 11 ms 10 ms 14 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
9 90 ms 90 ms 89 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 99 ms 101 ms 102 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 99 ms 97 ms 102 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 105 ms 105 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * 98 ms 97 ms 204.2.29.241
14 100 ms * 101 ms 204.2.29.122

Trace complete.



Spectrum Wireless:

Tracing route to 204.2.29.122 over a maximum of 30 hops



6 18 ms * * lag-416.hstqtx0209w-bcr00.netops.charter.com
7 19 ms * 87 ms lag-800.pr0.hou50.netops.charter.com
8 * * * Request timed out.
9 * 140 ms * dls-b24-link.ip.twelve99.net
10 * * * Request timed out.
11 30 ms 24 ms 25 ms dls-b23-link.ip.twelve99.net [62.115.138.65]
12 25 ms 24 ms 31 ms ntt-ic-325660.ip.twelve99-cust.net [62.115.156.249]
13 29 ms 27 ms 30 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
14 * 115 ms 64 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
15 67 ms 74 ms 68 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
16 65 ms 64 ms 60 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
17 73 ms 73 ms 79 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
18 67 ms * * 204.2.29.241
19 68 ms 70 ms 71 ms 204.2.29.122