Bad lag again with NTT's NA server network

AT&T Fiber in TX and same issue, unplayable lag for the last 2 days, multiple computers experiencing the same level of lag

Just chiming in, my two good friends both live in Dallas and are on AT&T and have had these same issues the past two days.

Just like last night around this time (~2AM eastern USA), the lag is starting to get better. It's very playable now, but I don't know how long until it'll break again, so take advantage of this if you need your daily roulettes still.

Quote:

---

Originally Posted by n_n

wow, I picked an awful time to resub =/

---

I'm with you on this one. Just bought the game for PC, and re-subbed after being away for seven years only to have this lag, disconnect, and poor connection even though I have AT&T Fiber Optics. I really want to play, and get back into the game but can't because of this lag issue making it unplayable.

Quote:

---

Originally Posted by n_n

Just like last night around this time (~2AM eastern USA), the lag is starting to get better. It's very playable now, but I don't know how long until it'll break again, so take advantage of this if you need your daily roulettes still.

---

Yep almost 4am eastern now and it's down to 60ms.

Chiming in to say I too am having severe rubberbanding/packetloss issues during the vast majority of my playtime yesterday and today. I am a AT&T fiber customer on the East Coast. Using a VPN has helped but I still experience some rubberbanding/packetloss with it enabled.

Cannot even imagine doing harder content with this sort of network performance.

Just going to add another to the list since it still seems like SE isnt acknowledging it yet.

Continued to rubber band yesterday in Frontlines. At some point, I think the server just doesn't register damage to me or I was really luck with how bad it was.

Source: Georgia. AT&T Fiber

Southern Ohio ATT Fiber reporting in for the same issue across multiple computers.

Tossing mine onto the pile as well, here. Indiana, ATT Fiber. High ping at the NTT nodes, packet loss, rubber banding, teleporting, crashing, etc. Game is full-on unplayable.

Boy did I pick a bad time to resub after a couple months off!

North Carolina, ATT fiber and suffering the same terrible lag in FFXIV for the past few days. No other games I've tried seem to be affected.

Very bad on AT&T fiber in Atlanta, GA.

I'm almost positive the issue won't be resolved today. But I highly recommend those with twitter to tweet at ATT and tag FFXIV in the message describing the issue with the NTT node. They'll give you the automated zip code / there's no outage in your area scripted messages, but ideally with more of us pushing the actual problem, maybe it'll get them to fix it. It's clear no side is taking any steps as there's been no communication at all, so let's add some fire!

Right on time at 10:40am EST the lag has started. Funny how it stopped at almost exactly the same time last night as well about 2:15am. I'm going out on a limb and guessing this won't be fixed anytime soon.

I'm also pretty upset that not a single SE support personnel has responded to this or acknowledged this problem. They have been pulling the, "if we ignore it long enough it will go away" stunt.

https://imgur.com/DJgT7dg.jpg

From may 15th 8am EST though 17th 11am EST
https://i.imgur.com/QP0pjun.jpg

Pretty much because unless you say the magic phrase, they kind of tend to not give it any piece of mind.
But yeah, decided to hop on what I would assume is a low traffic moment and I'm still noticing it.
Definitely going to cancel my sub if this continues. Not paying for a game I can't play.

For what it's worth, I figured I'd at least put in an SE support ticket. Filled out all the relevant info for the Connection/Network Issues form.
I'll share any updates I happen to get, although I'm assuming I likely won't get anything too relevant as I'm likely not the only one with a support ticket in for this issue right now.

Definitely frustrating that I renewed my sub only to not be able to play the game. The lack of any form of response after multiple days of an obvious issue is probably the biggest disappointment.

Edit: Received a very boilerplate-y response going through the usual stuff. "Turn off background processes on your computer, this might be caused by Microsoft Edge (lolwut), forward ports on your router, otherwise this is an issue with your ISP so take it up with them" sort of a deal. Replied with some traceroute screenshots showing ping issues at the NTT nodes and emphasized that this issue is not within my control or necessarily fully within AT&T's control. Sooooo we'll see what I get back.

I made it to the ATT tech team. I'll let you know what I find out and if they provide any assistance or ETA on this issue. I'll be submitting a SE support ticket next.

AT&T Fiber customer here, been having these lag spikes making the game unplayable all week on various character.
Connection and rig are otherwise fine and it's very clearly connection issues.

I'm located in the southern end of Alabama.

Definitely affects all gameplay. Dungeons, questing, crafting, marketboards.. etc.

Okay, here is the word from the tech: "I can see from my end that the root of the issue is beyond a simple configuration problem and is at the engineering level between the two ISPs. I also find that both parties are already aware of the issue, and they are already looking for a solution. The best I can do in this case is to take all your feedback related to the ongoing issue into a faster solution. I just want to remind you, that since the conflict is involving 2 different parties, it also depends on the efforts from the other provider."

So the good news is that those who are saying ATT and NTT are aware of the problem are speaking true (unless ATT is lying, but I like to think people are honest!). Bad news is there is no estimated time for a resolution. I still recommend sending ATT your feedback/screenshots/tracerts ect., as it might help solve or maybe at least escalate the priority level of the issue?

Yep not sure when it happened but as of 1pm eastern it's back on the BS. I'm working atm so not able to check game performance but I'm pretty sure it will be rubber-banding on me tonight.

I got a similar response from ATT as well so glad they are aware. Considering it's less than 20ms on my trace until it hits anything related to NTT, I suspect the issue is more on NTT's side and some here on these tech forums have mentioned exactly that before.

AT&T Fiber here. If this hasn't been fixed by tomorrow, I'm going to be cancelling my upcoming resub. Game has practically become unplayable due to lag.

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.

Quote:

---

Originally Posted by Stilico

AT&T Fiber here. If this hasn't been fixed by tomorrow, I'm going to be cancelling my upcoming resub. Game has practically become unplayable due to lag.

---

I don't want to go this route, especially since my static is relying on me to hit the ground running once 6.4 drops, but if I'm lagging, I won't be able to play.

Quote:

---

Originally Posted by brnslpy

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:

https://i.imgur.com/AUcZT86.png

I had to renew my VPN subscription as a result of this unplayable latency. Suffice it to say, rerouting does work if you're able to use or afford a VPN.

It's definitely not the best workaround, as I would prefer not having to use it, but it's at least viable until AT&T, SE, and/or NTT actually come forward with a "mea culpa" message.

Three days of this, and no official word, aside from what Techs have already stated. While it beats no word at all, official acknowledgment of this thread would be ideal.

If only there was a way to summon a CM in here to take a glance...

Quote:

---

For what it's worth, I figured I'd at least put in an SE support ticket. Filled out all the relevant info for the Connection/Network Issues form.
I'll share any updates I happen to get, although I'm assuming I likely won't get anything too relevant as I'm likely not the only one with a support ticket in for this issue right now.

Definitely frustrating that I renewed my sub only to not be able to play the game. The lack of any form of response after multiple days of an obvious issue is probably the biggest disappointment.

Edit: Received a very boilerplate-y response going through the usual stuff. "Turn off background processes on your computer, this might be caused by Microsoft Edge (lolwut), forward ports on your router, otherwise this is an issue with your ISP so take it up with them" sort of a deal. Replied with some traceroute screenshots showing ping issues at the NTT nodes and emphasized that this issue is not within my control or necessarily fully within AT&T's control. Sooooo we'll see what I get back.

---

After a bit more back and forth on my support ticket, Square Enix customer support responded and informed me that they are aware of the issue and are currently investigating and working on solving the issue. No timeline or anything given but... acknowledgement is a positive, I guess?

They also said to keep an eye on Lodestone for any updates.

Quote:

---

Originally Posted by Janyd

If only there was a way to summon a CM in here to take a glance...

---

Given that not even a moderator has popped in to say anything I don't think they want to touch this...

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.

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

Updated my post with more working PIA (Private Internet Access) VPN nodes. It seems most nodes around Chicago and including Chicago get around this. Also Silicon Valley for western people and Honolulu if you're a lucky person that lives there.

https://forum.square-enix.com/ffxiv/...=1#post6251695

Because this is a VPN, some of these IPs are dirty thus making Google.com make you complete a CAPTCHA in order to use their search. Last night I was using the Michigan node and found imgur.com has it banned.

Quote:

---

Originally Posted by Krojack

Updated my post with more working PIA (Private Internet Access) VPN nodes. It seems most nodes around Chicago and including Chicago get around this. Also Silicon Valley for western people and Honolulu if you're a lucky person that lives there.

https://forum.square-enix.com/ffxiv/...=1#post6251695

Because this is a VPN, some of these IPs are dirty thus making Google.com make you complete a CAPTCHA in order to use their search. Last night I was using the Michigan node and found imgur.com has it banned.

---

Much appreciated, Krojack.

Quote:

---

Originally Posted by MoonmoonMoonmoon

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:

https://i.imgur.com/AUcZT86.png

---

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.

Quote:

---

Originally Posted by Janyd

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

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. :(

Quote:

---

Originally Posted by Ath192

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.

Quote:

---

Originally Posted by Janyd

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.

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?

Quote:

---

Originally Posted by TaleraRistain

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.

Quote:

---

Originally Posted by 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?

---

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.

Quote:

---

Originally Posted by MoonmoonMoonmoon

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.

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?