Bad lag again with NTT's NA server network

[TaleraRistain]

Did you try running it with the actual datacenter IP? If you do that, you'll find that it's a different node acting up.

Partial `tracert` results:

4 4 ms 2 ms 4 ms 71.154.103.72
5 * * * Request timed out.
6 14 ms 15 ms 15 ms 32.130.25.65
7 18 ms 14 ms 20 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 * * * Request timed out.
9 * * * Request timed out.
10 108 ms 102 ms 101 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 102 ms 102 ms 103 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 103 ms 102 ms 104 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 * 95 ms * 204.2.29.241
14 103 ms 95 ms 92 ms 204.2.29.6

Screenshot:

How do you find that? The most I've been able to find is a neolobby02 reference on an reddit thread for Aether DC and I'm also constantly seeing that 129.250.7.57 node. I also tried with the IP Windows Resource Monitor was giving me when I was in game the past two nights and it's always been that node.

[MoonmoonMoonmoon]

How do you find that? The most I've been able to find is a neolobby02 reference on an reddit thread for Aether DC and I'm also constantly seeing that 129.250.7.57 node. I also tried with the IP Windows Resource Monitor was giving me when I was in game the past two nights and it's always been that node.

Just ping

neolobby02.ffxiv.com

to get the IP address of the Aether DC. It's possible that you're hitting a different node, which would indicate that several nodes withing the NTT network are bad and they're not doing anything to fix it. Shame on them and shame on anyone defending them right now.

[TaleraRistain]

Just ping

neolobby02.ffxiv.com

to get the IP address of the Aether DC. It's possible that you're hitting a different node, which would indicate that several nodes withing the NTT network are bad and they're not doing anything to fix it. Shame on them and shame on anyone defending them right now.

Yep that's what I'm using for ping and the traceroute and it's bringing up the 57 node as an issue.

[Ath192]

Yep that's what I'm using for ping and the traceroute and it's bringing up the 57 node as an issue.

It doesn't seem like mine goes through the 57 though and I'm still having the problem. When I ping my routes I'm just fine until I get to the following IP: 128.241.2.18. As soon as I try to ping that it starts dropping packets.

[SonicRose]

My experience with this game for years has mostly been fine. Of course I have experienced lag before (who hasn't?) But it's not usually persistent like this. Recently upgraded to fiber optics with my Internet Provider and it was working absolutely fine as before until a couple days ago. It's okay while I'm doing casual content, but I want to run current high end and I don't even want to try another deep dive in palace or HoH until this is resolved. It's kind of funny out of combat to see a group of people lurch forward only to stop a few paces and then resume, but it's also worrisome.

[Dawn_Naur]

AT&T customer in South Carolina.. i have the same issues as everyone else.. other than a few solo quests and just hanging out.. or an old dungeon or island sanctuary.. its largely unplayable.

please fix before 6.4

(begging on knees)

[TaleraRistain]

It doesn't seem like mine goes through the 57 though and I'm still having the problem. When I ping my routes I'm just fine until I get to the following IP: 128.241.2.18. As soon as I try to ping that it starts dropping packets.

Yeah it could be 2 nodes

9 55 ms 55 ms 55 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 * 110 ms 110 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 111 ms 110 ms 110 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 * 111 ms 109 ms 204.2.29.6

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