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.

[Ath192]

Finally, acknowledgment from Square Enix. I'm guessing a Lodestone post will come later today or tomorrow, at this rate. Fingers crossed!

Where?

Also ping test ran for hours shows around 6% packet loss today. I bet it'll get really bad at night again.

Packets: Sent = 5039, Received = 4732, Lost = 307 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 103ms, Maximum = 125ms, Average = 120ms

[Symon14]

Just posting to say I have noticed severe lag the last couple of days, and I am on AT&T Fiber. Healing a party is rough.

[Janyd]

Where?

Also ping test ran for hours shows around 6% packet loss today. I bet it'll get really bad at night again.

Packets: Sent = 5039, Received = 4732, Lost = 307 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 103ms, Maximum = 125ms, Average = 120ms

Oh, that was based on a previous thread comment someone else made about reaching out to a Square Enix customer service representative.
It's just wishful guessing that they'll get to make a post about it, since they're aware of the situation.

[Ath192]

Oh, that was based on a previous thread comment someone else made about reaching out to a Square Enix customer service representative.
It's just wishful guessing that they'll get to make a post about it, since they're aware of the situation.

Ah. Yeah this is so bad. I don't want to spend $40 on a VPN on top of what I'm paying ATT and SE already.

[Janyd]

A thought came to me.
Would using my gateway's firewall to filter out the faulty node would be of any help in this situation?
Or would the routes it would take be too far off the beaten path to make a difference?

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

[MoonmoonMoonmoon]

A thought came to me.
Would using my gateway's firewall to filter out the faulty node would be of any help in this situation?
Or would the routes it would take be too far off the beaten path to make a difference?

The only problem I can think of with this is that you'd just run into another faulty node. From what I can tell, there are at least two faulty nodes at play here that are causing these issues. If you can figure it out and provide a list of the faulty nodes I'd appreciate it for sure. I have raid again tonight and it looks like I'm going to be benched again because of this issue.

[Janyd]

The only problem I can think of with this is that you'd just run into another faulty node. From what I can tell, there are at least two faulty nodes at play here that are causing these issues. If you can figure it out and provide a list of the faulty nodes I'd appreciate it for sure. I have raid again tonight and it looks like I'm going to be benched again because of this issue.

I think your recent traceroute can yield answers.
If you can try to filter out hops 10, 11, and 12 by entering the IP Addresses at the end of each line, see where that takes you.
But please make sure it doesn't aversely affect any other Internet sites/services you use.

[MoonmoonMoonmoon]

Does anyone have a good connection with no lag right now so I can try entering some NTT.net nodes into my router to see if I can get a more stable connection?