Bad lag again with NTT's NA server network

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

[n_n]

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

[radhaz]

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

[Illyrian94]

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.

[Rekts]

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.

[Elizara]

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)

[RyuezaneWithersoul]

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

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

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

[Kaitlen]

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)

[Brywynn]

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!