Bad lag again with NTT's NA server network

Okay, was just checking..

Couple nasty spikes right now on Pingplotter but generally okay. Hopefully they're still working on it.

Another day, another infestation of trash. Unusable connection.

Yeah the lag has started up again earlier than yesterday. Let's hope tho. I don't like playing around like this. ^^

Yeah the lag has started again. Of course another day of unplayable latency.

I don't know if I remember how to play without lag at this point.

With me, I just don't when it's lagging. Neko's still doing Zelda..Please, let's hope this gets fixed.

For a joke, I asked on the CurseTheYagudo discord for everyone who isn't lagging to throw sharp pointy objects at AT&T and NTT (they knew I was half joking) until this fixes itself. ^^ We all gotta put the pressure on you know?

I've been using Cloudflare Warp for the last couple of days. It has made my experience almost lag-free.
It's free, easy to configure and uninstalls easily.

Day 14 of latency and packet loss. I never expected this issue to resolve quickly, but I expected it to be solved within a week. Now it's been 2. Shame on all parties. No additional news from SE for a few days too.

From a new thread on Reddit, NTT replied to someone:

"Reviewing the information provided the source of the packet loss is likely due to an AT&T and NTT congested peering point. While there were no issues present in the traceroute provided, I can see that the return path for your traffic would likely be traversing a known congestion point in LA where throughout most of the day you would be experiencing packet loss for this source/destination combination. Unfortunately the issue you are experiencing is not technical in nature but instead more political. Both AT&T and NTT are aware of the situation however due to NDA's we are unable to discuss specifics as to when an increase in peering capacity would be initiated. This issue has already been escalated to the highest technical levels within NTT to helpalleviate the congestion as much as possible however we're unable overcome the root of the issue which is a lack of capacity.Due to NDA, we can't disclose any specifics. However, we have been taking and will continue to take technical steps to remedy the situation to the extent possible at our side."

I guess we really gotta put pressure on AT&T then, make sure you call this a PEERING ISSUE. Otherwise you're liable to get the runaround. I'm still chicken about calling them due to the brother that works from home; EVERY TIME I've done that they've tried resetting our router or other nastiness that'd get me pounded in short order so I've been using the strat of waiting this out.

If I'm going to call their tech support, it'd better be about more than one game. :)

Also Lahorti; That's also working for me again BUT that doesn't help my brother, so I'm keeping a eye on this thread to find out when we DON'T have to use VPNs and things like Cloudflare Warp. As I said earlier in the thread; Most console players are up a creek without a paddle with this if you are just using AT&T's supplied gateway! (WHICH. WE. ARE. That is one of the hazards of Uverse.)

One solution would be to move my pc out of my bedroom so he could use that to play but..we don't have any other place to put it at this time, and that kinda defeats the purpose of having two DIFFERENT accounts. And we're kinda on the poor side right now due to convention season and the fact that DON BLUTH was at Momocon. (Autographs are not cheap!) So building him a pc is not in the offing for months, and mine needs a rebuild as it is.

I’ve been lurking this thread for two weeks. I’ve been playing XIV since the launch of ARR with a DSL connection and up until a few years ago an AT&T fiber connection. This rubberbanding and latency is objectively WORSE than playing on a DSL line. CC is unplayable, normal raids are unplayable, my crafting macros are unusable and for the first time since coil I had to have one of my raid mates craft my gear for me this tier. My house and static are the only reasons I continue to stay subscribed. The lack of transparency is ridiculous too. No, SE, this won’t blow over, and we will keep this thread bumped and on the front page until this issue is fully addressed.

I don't know how much I trust reddit randos though. Reddit has consistently, magically been talking to NTT since this started and have consistently claimed AT&T is the issue despite us being able to tell from traceroutes that the problem doesn't occur at the handoff, it happens inside NTT's network. NTT says ATT, ATT says NTT. Keeping the pressure on all fronts is the only thing that's going to solve anything. I don't trust that anything has been escalated "to the highest level" anywhere yet, or this problem would be solved.

Quote:

---

Originally Posted by Brywynn

I don't know how much I trust reddit randos though. Reddit has consistently, magically been talking to NTT since this started and have consistently claimed AT&T is the issue despite us being able to tell from traceroutes that the problem doesn't occur at the handoff, it happens inside NTT's network. NTT says ATT, ATT says NTT. Keeping the pressure on all fronts is the only thing that's going to solve anything. I don't trust that anything has been escalated "to the highest level" anywhere yet, or this problem would be solved.

---

While I completely agree Redditors will post absolutely anything-- even fabricated nonsense to get those upvotes and rewards that they deem so important, those email responses are genuine... albeit copypasted. People in this thread have gotten an email response from NTT and it's the same crap about it being "escalated to the highest level" and "muh NDA."

Results today, before and after of my NA and JP ping plots using Warp.

https://live.staticflickr.com/65535/...67a241a2_c.jpg

https://live.staticflickr.com/65535/...63699fdd_c.jpg

Same story for me the past few days. I've been playing the fighting games the past couple of days but have been keeping an eye on pingplotter like usual.
I've also contacted AT&T support again and will see just how long I can manage to keep my support ticket open before they decide to just randomly close it or send someone to replace my router *again* even though I've proved that isn't the issue.

It's definitely wishful thinking, but hopefully tomorrow we'll see some improvements. I believe it was Friday night we saw a full night with no packet loss, and then the holiday weekend it all returned. Maybe we'll get lucky tomorrow after the holiday and get some people actually working on it.

I feel like at this point I'm just digging up reasons to stay positive.

Rekts; it's a good thing to stay positive. Maybe after this mess is fixed, we can get together and do some stuff? (Gotta love data center/world visits)

I agree there was no lag on Friday then it came back. i hope by tomorrow it's fixed. i just hope we don't go till June with this issue..

Just keeping the bad dream thread alive; I've not posted in days but have been lurking. I've got the Trifecta going as well, sound cuts out, game becomes unresponsive will not close without windowed access to task manager, and of course this. I've not run any of the new content; want to hear the music. (Yes, I know sound has been addressed, two week processing time...ugh) I've been working my island in the morning since sound is not really critical. Mornings things are playable, afternoon...no shot. Wild to think that just last month I was consistently enjoying an "excellent" connection, perfect audio and could close the game via the menu options. What the heck happened?!? Side note on anything Reddit, not buying it.

6:00 am

2 9 ms 9 ms 7 ms 10.40.159.1
3 11 ms 11 ms 9 ms 12.244.143.181
4 14 ms 15 ms 15 ms 12.123.6.38
5 12 ms 15 ms 15 ms fldfl401igs.ip.att.net [12.122.155.169]
6 23 ms 18 ms 19 ms 192.205.35.118
7 17 ms 19 ms 19 ms ae-0.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.5]
8 39 ms 41 ms 41 ms ae-8.r20.dllstx14.us.bb.gin.ntt.net [129.250.2.219]
9 * * * Request timed out.
10 76 ms 75 ms 76 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 77 ms 76 ms 88 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 74 ms 76 ms 74 ms xe-1-0-4-2.a00.scrmca03.us.ce.gin.ntt.net [192.80.16.2]
13 77 ms 76 ms 76 ms 204.2.229.230

8:00 pm

2 19 ms 13 ms 10 ms 10.40.159.1
3 8 ms 10 ms 10 ms 12.244.143.181
4 16 ms 14 ms 15 ms 12.123.6.38
5 15 ms 15 ms 15 ms fldfl401igs.ip.att.net [12.122.155.169]
6 39 ms 43 ms 40 ms 192.205.35.118
7 * * * Request timed out.
8 48 ms 48 ms 44 ms ae-8.r20.dllstx14.us.bb.gin.ntt.net [129.250.2.219]
9 115 ms 126 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
10 126 ms 127 ms 126 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
11 * 127 ms 144 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
12 125 ms 126 ms 128 ms xe-1-0-4-2.a00.scrmca03.us.ce.gin.ntt.net [192.80.16.2]
13 125 ms 126 ms 126 ms 204.2.229.230

Just posting a follow-up from my earlier posts, the current weather inside NTT's network at May 30th 9:45AM JST/5:45 PM PST/8:45 PM EST

I'm accustomed to playing with a ping from 110-150, average is more like ~118 day-to-day.
(hops 1-8 = central Tokyo, 9-13 California)

1 <1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 1 ms 118.23.27.227
3 2 ms 2 ms 2 ms 118.23.27.17
4 3 ms 3 ms 3 ms 118.23.4.1
5 3 ms 2 ms 3 ms 180.8.126.41
6 3 ms 3 ms 3 ms 122.1.245.209
7 3 ms 3 ms 3 ms ae-6.r03.tokyjp05.jp.bb.gin.ntt.net [120.88.53.29]
8 5 ms 3 ms 3 ms ae-4.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.34]
9 110 ms 110 ms 110 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 125 ms 120 ms 119 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 121 ms 129 ms 121 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 123 ms 123 ms 124 ms xe-1-0-4-2.a00.scrmca03.us.ce.gin.ntt.net [192.80.16.2]
13 124 ms 126 ms 124 ms 204.2.229.230

Ping Sample: (same time as route above)
Ping statistics for 204.2.229.230:
Packets: Sent = 610, Received = 610, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 122ms, Maximum = 155ms, Average = 124ms

Just sharing this so people can compare choke points around the same time period but from different routes into NTT.

Sample #2 - May 30th 4:32 PM JST/12:32 AM PST/3:32 AM EST:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 3 ms 3 ms 118.23.27.227
3 2 ms 2 ms 3 ms 118.23.27.17
4 6 ms 3 ms 4 ms 118.23.4.1
5 6 ms 3 ms 3 ms 180.8.126.41
6 3 ms 3 ms 7 ms 122.1.245.209
7 11 ms 9 ms 6 ms ae-6.r03.tokyjp05.jp.bb.gin.ntt.net [120.88.53.29]
8 16 ms 9 ms 14 ms ae-4.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.3.34]
9 112 ms 111 ms 114 ms ae-4.r25.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
10 119 ms 119 ms 118 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 121 ms 129 ms 121 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 123 ms 123 ms 127 ms xe-1-0-4-2.a00.scrmca03.us.ce.gin.ntt.net [192.80.16.2]
13 123 ms 123 ms 123 ms 204.2.229.230

(no change in ping test)

Quote:

---

Originally Posted by Integro

Just keeping the bad dream thread alive; I've not posted in days but have been lurking. I've got the Trifecta going as well, sound cuts out, game becomes unresponsive will not close without windowed access to task manager, and of course this. I've not run any of the new content; want to hear the music. (Yes, I know sound has been addressed, two week processing time...ugh) I've been working my island in the morning since sound is not really critical. Mornings things are playable, afternoon...no shot. Wild to think that just last month I was consistently enjoying an "excellent" connection, perfect audio and could close the game via the menu options. What the heck happened?!? Side note on anything Reddit, not buying it.

---

Oh hey! I did not know that the sound randomly cutting out and the game becoming unresponsive and unable to be closed was also a thing other people were dealing with!! Like, my sound works, but if I alt-tab too long I come back to dead quiet and have to exit out from taskbar because it will hang up if I try to close from in-game.

NEAT!

And sometimes reddit is info, but I just don't buy that NTT is talking to random FFXIV players like that. We aren't their customer. Square is. I completely buy people's responses they've posted from AT&T saying "it ain't us it ain't in our network" because that's what all the numbers have shown in this thread. Which is barreling on towards 90 pages now...

FUN!

I still see rubber banding / lag spikes game is almost not playable sigh.

I'm not on ATT but am also now having issues, goes away when I try a diff network, so they clearly did something during maintenance, I am worried they broke it more than they fixed it atm.

Quote:

---

Originally Posted by DES_VII

I still see rubber banding / lag spikes game is almost not playable sigh.

---

my connection reads as "excellent" for the first time in a month after installing this... and i dont see rubber banding yet!

Quote:

---

Originally Posted by Brywynn

Oh hey! I did not know that the sound randomly cutting out and the game becoming unresponsive and unable to be closed was also a thing other people were dealing with!! Like, my sound works, but if I alt-tab too long I come back to dead quiet and have to exit out from taskbar because it will hang up if I try to close from in-game.

NEAT!

FUN!

---

Yep!

https://forum.square-enix.com/ffxiv/...S5-Audio-Issue

https://forum.square-enix.com/ffxiv/...onding-on-exit

Holy heckin moly. Today's the worst the lag has been. I normally have just experienced gnarly rubberbanding, but I've been having several bursts of 10+ seconds of freezing with my first 90006 error of this whole ordeal. Absolutely bonkers.
I hate hate hate the fact that I'm still subbed just to keep my gd house.

1 <1 ms <1 ms <1 ms 192.168.1.254
2 1 ms 2 ms 1 ms 118.23.27.227
3 2 ms 2 ms 2 ms 118.23.27.17
4 12 ms 15 ms 15 ms 118.23.4.1
5 * * * Request timed out.
6 * * * Request timed out.
7 15 ms 14 ms 15 ms 32.130.25.65
8 12 ms 12 ms 18 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 12 ms 12 ms 12 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 * 96 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 99 ms * 98 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 99 ms 150 ms 99 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 99 ms 99 ms 99 ms xe-1-0-4-2.a00.scrmca03.us.ce.gin.ntt.net [192.80.16.2]
14 * 98 ms 99 ms 204.2.229.230
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.

Quote:

---

Originally Posted by CirenInus

my connection reads as "excellent" for the first time in a month after installing this... and i dont see rubber banding yet!

---

I'm happy you don't have super rubber banding lag spikes. A lot still do. Heck ppl have unsubbed till its fixed.

The lag was really horrible tonight. It has been pretty bad since this thread's creation, but tonight was just exceptionally horrific. Combat had reached the point of being unplayable, and it's really frustrating.

Hope it's better tonight. Anyway this morning it's back to being okay without having to use things like a VPN or Cloudflare Warp. Let's see if it holds guys. I hope it's fixed by the time 'Neko is not as distracted by Zelda so we can play together again. I realize I go to bed earlier than some of you but it may be due to time zones as well.

I have been continuing to use my Verizon hotspot with no issues (other than the mild lag it's always had and inability to use Discord voice chat). Just watching this thread in hopes of seeing the issue resolved so I can actually use the fiber internet I'm paying for to play. I can't believe it's gone on this long. ☹️

I can't really do much since I can't justify a new router for one game that I already pay for monthly to play on a console. I've tried different DNS settings, but haven't had luck. Ridiculous we're still here with no end in sight two weeks since the issue started. 3 big companies involved doing the spiderman meme.

Quote:

---

3 3 ms 3 ms 3 ms 71.155.29.140
4 * * * Request timed out.
5 12 ms 7 ms 7 ms 32.130.25.65
6 6 ms 7 ms 7 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
7 * * * Request timed out.
8 * 82 ms 75 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 79 ms 82 ms 99 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 80 ms 82 ms 90 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 87 ms 90 ms * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 89 ms 91 ms 85 ms 204.2.29.6

---

11:40am CST, already started.

Quote:

---

Originally Posted by kristicles

I can't really do much since I can't justify a new router for one game that I already pay for monthly to play on a console. I've tried different DNS settings, but haven't had luck. Ridiculous we're still here with no end in sight two weeks since the issue started. 3 big companies involved doing the spiderman meme.

---

If you have a laptop or pc nearby, it is possible to run a vpn to your console. You run a Ethernet from your modem to your PC, and a USB-Ethernet adapter to the console. Run a vpn on your pc and allow the adapter to share the connection. This has worked like a dream these past couple of days.

Went to log in an hour ago and saw "poor" connection with a LAN cable getting over 900 mbps(I'm also on console). Didn't bode well so I didn't log in.

I really do hope we see improvement soon.

Quote:

---

Originally Posted by Aranthon

If you have a laptop or pc nearby, it is possible to run a vpn to your console. You run a Ethernet from your modem to your PC, and a USB-Ethernet adapter to the console. Run a vpn on your pc and allow the adapter to share the connection. This has worked like a dream these past couple of days.

---

I will try this out! thank you! I will try and find a free vpn because I'm at the point that I refuse to pay any extra for this :(

Several additional people have been posting on the ATT forums over the last couple of days, and still the only real input are from "experts" and not actual ATT employees. The fact that we can't get any communication from either of these companies is appalling.

I thought I’d try and log in early to see if CC would be possible at all if I could beat prime time congestion…and no. I spent my matches slamming skills that wouldn’t go off and running in over and over to teleporting opposing teams, at 11am CST. I was hoping I’d be able to get to crystal this season after giving up at diamond last season, but it looks like I’ll be lucky to even make it past gold being a literal boat anchor to my team. If this doesn’t get fixed soon, I might not even be able to upgrade my hellhound weapons like I wanted to. Even getting the fomo rewards this season will be terrible in casual CC as the teleporting and rubberbanding is extremely disorienting and an exercise in frustration. Tonight will also be our groups first time going in to savage. I can only imagine how bad that will be.

It's still bad. Is there actually nothing being done about this? During the mornings or during the night I can play but during the day it's impossible with everyone slide casting around.

Sadly whatever is going on between ATT and NTT "It's under an NDA" so it can take awhile for this situation to get fixed I remember Comcast customers having this problem 4 years ago so who knows how long this situation can last? I'm waiting for it cloudflare is a hit-and-miss for me most of the time anyways. for the 2 years of me playing final fantasy 14 I never had this problem it personally sucks that we have to find a VPN to just play this game.

Quote:

---

Originally Posted by RyuezaneWithersoul

Sadly whatever is going on between ATT and NTT "It's under an NDA" so it can take awhile for this situation to get fixed I remember Comcast customers having this problem 4 years ago so who knows how long this situation can last? I'm waiting for it cloudflare is a hit-and-miss for me most of the time anyways. for the 2 years of me playing final fantasy 14 I never had this problem it personally sucks that we have to find a VPN to just play this game.

---

People shouldn't tolerate this. If nothing will be done, then people should just drop the game. If everyone affected leaves then SE will have to push for something to be done. At the end of the day SE is in the middle of it all. NTT/ATT/Whoever might be a part of the problem, but SE is where all of these problems seem to come together.

It makes me genuinely sad to see so many people using VPNs to play. Maybe you have one for other reasons, maybe you don't, but either way this isn't your problem to solve. You're spending extra money to solve an issue for you caused by massive corporations. That's absolutely not right.

An ATT employee replied on their forums earlier today "ATT doesn't manage the IP for NTT". Thank you for that amazing insight on what you're planning to do for your customers caught in the middle....

I think the only thing we can do is keep pressuring all 3 companies involved. NTT for refusing to address or resolve the situation, ATT for being the one most affected for both customers and non-customers, and SE for contracting with NTT.

Call them, utilize social media, keep putting in support tickets. NTT on Twitter is @GlobalNTT.