Bad lag again with NTT's NA server network

Quote:

---

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

---

This is what I can share from a friend without the issue. Canada.

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

AT&T same issues and they claim its SE side and I put ticket in for support they just gave run around that I already did all said things. It been going on for last few days for me. I'm in WI.

My ping has gone down from 120ms to about 83ms. I haven't tried battle content yet but its marginally better. Still about 15ms or so more than normal but I haven't been seeing rubberbanding in the cities at least. Running a trace for the data center does seem to still result in packet loss though.

Still terrible lag for me. Cannot pvp well at all. It is making getting the last few series levels before the new series quite painful. It's been 3+ days now :(

Quote:

---

Originally Posted by MoonmoonMoonmoon

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.

ATT fiber customer in IL. Terrible lag during their peak times. I have to use a vpn and it's back to being decent. Really hope this is resolved soon.

Quote:

---

Originally Posted by TaleraRistain

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.


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

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.

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

Quote:

---

Originally Posted by Ath192

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.


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

---

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

Quote:

---

Originally Posted by Ath192

This is what I can share from a friend without the issue. Canada.

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

---

This unfortunately has not offered up any results for me so far. It's like there are pre-defined routes that I cannot bypass in the internet. It doesn't matter how much I try to hit the 129.250.8.61 node at ntt.net, I cannot get my internet to cooperate.

I'm using a Linksys WRT3200ACM router if anyone has any ideas.

I'm in Central US and I'm experiencing severe lag as well. I mostly play on PS5 too.

Hello everyone,

We're aware that some users playing on the North American data center have been experiencing network delays and/or packet loss while playing. We understand the frustrations and concerns regarding the situation, especially with Patch 6.4 and new Savage raids on the horizon.

The Community team has been relaying your reports to the Development team as they continue their ongoing investigation. If your network connection seems to be slower or stuttering more than usual, we would appreciate it if you could take a moment to follow the instructions detailed in this Lodestone announcement and share your information with us through this form.


Thank you,

Thanks for the reply, Okieeomi!

Hopefully, the development team and all parties involved can get to the bottom of this soon.

I have been dealing with lag issues for the past 3 days. Frontline is unplayable. On every NA Data Center, it shows a POOR connection, and it never improves. This issues is NOT with my ISP. I have reset my gateway, rebooted the computer and restarted FFXIV dozens of times, with no improvement. Speed tests have shown my connection to be good.

I have tried three different browsers and this is all I get when I follow the form link :confused:

https://images-wixmp-ed30a86b8c4ca88...1OWg_3yqUt3gZU

(AH I see the post further up as well)

SE finally posted SOMETHING...

https://twitter.com/FF_XIV_EN/status...63004749402114

Quote:

---

Originally Posted by klutzz

I have tried three different browsers and this is all I get when I follow the form link :confused:

https://images-wixmp-ed30a86b8c4ca88...1OWg_3yqUt3gZU

---

Same thing. Google translates it into "An unexpected error has occurred".

*facepalm*

Quote:

---

Originally Posted by Krojack

Same thing. Google translates it into "An unexpected error has occurred".

*facepalm*

---

Yeah, I tried a few times before I found the actual link in the Lodestone article that was posted. That one seems to work?

I was able to connect to a vpn that pops me out in los angeles. I no longer suffer high ping and dropped packets. Thank you Proton VPN

Quote:

---

Originally Posted by Okieeomi

Hello everyone,

We're aware that some users playing on the North American data center have been experiencing network delays and/or packet loss while playing. We understand the frustrations and concerns regarding the situation, especially with Patch 6.4 and new Savage raids on the horizon.

The Community team has been relaying your reports to the Development team as they continue their ongoing investigation. If your network connection seems to be slower or stuttering more than usual, we would appreciate it if you could take a moment to follow the instructions detailed in this Lodestone announcement and share your information with us through this form.

Thank you,

---

Thank you for the reply! I know the SE side is limited since it's not in their direct control, but we appreciate any pressure that the SE side can put on those involved to get this fixed for your customers.

link worked for me lol maybe turn off your vpn

I managed to contact NTT, the guy was very nice and told me that this is on ATT, there's nothing wrong with their equipment. As a courtesy he performed some tests.

Good day,

Per our conversation, I have investigated your traceroute result. I want to add a caveat that this as a courtesy email response, because technically, if ATT is your upstream provider, you will need to work with ATT on this potential packet loss issue.
With that said, I do not see any issue within the NTT network that would cause your packet loss issue. I would suggest to work with ATT if they are your upstream provider.
Per your traceroute result:
7 25 ms 31 ms 31 ms 32.130.25.67 <<< This is the ATT node that is handing off traffic to NTT in Dallas, Tx
8 40 ms 36 ms 30 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237] <<< This is the ATT node where the traffic is picked up by NTT
9 * * * Request timed out. <<< This is a node that is not responding to ICMP, does not indicate packet loss or latency
10 * * * Request timed out. <<< This is a node that is not responding to ICMP, does not indicate packet loss or latency
11 116 ms 117 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7] <<< The ms increase between Hop 8 and 11 is expected as the traffic traverses the NTT network between Dallas, TX to Sacramento, CA
12 118 ms 117 ms 116 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76] <<< The ms stayed consistent
13 117 ms 119 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] <<< The ms stayed constsent

Hopes 14 and 15 is where NTT hands off to a peer where the trace reaches its destination.

I performed a ping from our Dallas, TX node to the destination IP 204.2.29.87. And I did not receive any packet loss.

dllstx1> ping 204.2.29.87 count 100
May 17 23:03:36
PING 204.2.29.87 (204.2.29.87): 56 data bytes
64 bytes from 204.2.29.87: icmp_seq=0 ttl=57 time=40.044 ms
64 bytes from 204.2.29.87: icmp_seq=1 ttl=57 time=39.382 ms
64 bytes from 204.2.29.87: icmp_seq=2 ttl=57 time=39.889 ms
64 bytes from 204.2.29.87: icmp_seq=3 ttl=57 time=39.235 ms
64 bytes from 204.2.29.87: icmp_seq=4 ttl=57 time=39.100 ms
64 bytes from 204.2.29.87: icmp_seq=5 ttl=57 time=39.304 ms
64 bytes from 204.2.29.87: icmp_seq=6 ttl=57 time=39.403 ms
64 bytes from 204.2.29.87: icmp_seq=7 ttl=57 time=40.766 ms
64 bytes from 204.2.29.87: icmp_seq=8 ttl=57 time=40.019 ms
64 bytes from 204.2.29.87: icmp_seq=9 ttl=57 time=39.395 ms
64 bytes from 204.2.29.87: icmp_seq=10 ttl=57 time=40.190 ms
64 bytes from 204.2.29.87: icmp_seq=11 ttl=57 time=39.404 ms
64 bytes from 204.2.29.87: icmp_seq=12 ttl=57 time=41.263 ms
// Truncated //
64 bytes from 204.2.29.87: icmp_seq=84 ttl=57 time=39.327 ms
64 bytes from 204.2.29.87: icmp_seq=85 ttl=57 time=39.744 ms
64 bytes from 204.2.29.87: icmp_seq=86 ttl=57 time=39.615 ms
64 bytes from 204.2.29.87: icmp_seq=87 ttl=57 time=40.364 ms
64 bytes from 204.2.29.87: icmp_seq=88 ttl=57 time=41.482 ms
64 bytes from 204.2.29.87: icmp_seq=89 ttl=57 time=39.367 ms
64 bytes from 204.2.29.87: icmp_seq=90 ttl=57 time=39.399 ms
64 bytes from 204.2.29.87: icmp_seq=91 ttl=57 time=39.247 ms
64 bytes from 204.2.29.87: icmp_seq=92 ttl=57 time=39.258 ms
64 bytes from 204.2.29.87: icmp_seq=93 ttl=57 time=39.146 ms
64 bytes from 204.2.29.87: icmp_seq=94 ttl=57 time=39.738 ms
64 bytes from 204.2.29.87: icmp_seq=95 ttl=57 time=40.225 ms
64 bytes from 204.2.29.87: icmp_seq=96 ttl=57 time=39.203 ms
64 bytes from 204.2.29.87: icmp_seq=97 ttl=57 time=39.681 ms
64 bytes from 204.2.29.87: icmp_seq=98 ttl=57 time=39.681 ms
64 bytes from 204.2.29.87: icmp_seq=99 ttl=57 time=39.263 ms
--- 204.2.29.87 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/stddev = 39.096/39.843/56.776/1.873 ms



---
Victor Nadalalicea
Network Analyst, Global IP NOC

I dunno about that. It seems that AT&T and NTT need to come together to fix it.

I don't have a vpn, but thanks for the suggestion :/

Quote:

---

Originally Posted by Janyd

I dunno about that. It seems that AT&T and NTT need to come together to fix it.

---

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.

Quote:

---

Originally Posted by Ath192

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.

---

Either way, at least all parties involved have been alerted to this. I seem to recall someone else mentioning speaking to an AT&T rep earlier this week and they also were made aware of it.

Quote:

---

Originally Posted by Janyd

Either way, at least all parties involved have been alerted to this. I seem to recall someone else mentioning speaking to an AT&T rep earlier this week and they also were made aware of it.

---

Yep, believe me, I want this fixed as bad as anyone else. Just relaying what I heard when I tried.

The only other major ISP that I'm aware of that's both in the Dallas area and a direct competitor of AT&T would be Charter/Spectrum.

Unfortunately, I don't know of anyone that's seen this thread yet that could provide their traceroute. That said, that's an excellent idea, Ath192.

If anyone from DFW/North Texas on a not-AT&T ISP can provide a traceroute, let's see it.

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

Quote:

---

Originally Posted by Titor

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.

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

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

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.

Quote:

---

Originally Posted by Ath192

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.

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

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

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.

Quote:

---

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

---

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.

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