Bad lag again with NTT's NA server network

[brnslpy]

Been watching the nodes all morning from Midwest ATT. Right on schedule, around 11:30AM EDT, ping doubled from 60ms to 100-120ms with intermittent packet loss. Decided to spend my lunch break wading through ATT customer support. After they were done mucking around with my router, and allowing me to share trace routes, they watched my pings to 204.2.29.122 (FFXIV gateway server from SQEX's network issue report page) and confirmed the same thing I was seeing. Supposedly, their network engineers are aware of the peer-to-peer node with NTT and said their current timeline is 7-8 hours -- take that as you will though. 3 days for one bad node... I don't understand how two ISPs would take that long to fix that.

Partial Traceroute for the curious:

7 cgcil402igs.ip.att.net (12.122.132.197) 9.470 ms 17.816 ms 15.938 ms
8 192.205.32.194 (192.205.32.194) 9.816 ms 10.712 ms 12.681 ms
9 ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239) 15.468 ms 12.202 ms 10.787 ms
10 ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 61.391 ms * 56.979 ms
11 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 104.897 ms 118.354 ms 108.629 ms
12 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 99.586 ms 90.496 ms 103.030 ms
13 204.2.29.241 (204.2.29.241) 108.414 ms * *

You can see its always the node 129.250.7.57 that's locking everything up.

[MoonmoonMoonmoon]

You can see its always the node 129.250.7.57 that's locking everything up.

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:

[brnslpy]

Yeah, I've gone down the list of the one from their support page and ones from is.xivup.com -- I concur that some might get different stuck routes but at least in my tests from two different sources, 129.250.7.57 is the one I'm locking up on.

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

[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