Bad lag again with NTT's NA server network

Getting the same thing here. I was in a raid, and it seemed like everyone was running and stopping, running and stopping, and I couldn't click on any commands.

What a damn joke
https://cdn.discordapp.com/attachmen...1220/image.png

Same thing here, people rubber-banding around, interactions take several seconds to process, etc

having the same problem, game was acting normally when I was on earlier.

I dont know why Square Enix wont acknowledge or talk about this. Its really frustrating to not know if this is a permanent thing or if its being worked on.

Im just going to let my sub expire in December because i cant take this anymore. This is ridiculous :(

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

https://i.imgur.com/8pcaC90.png

Just today started noticing unplayable lag at times, found this topic. Trace routes show lag at the same place as others complaining here.

It's the worst knowing I can't fix this myself.

Edit: Just lagged so bad the game full disconnected. Cool.

Same just started today and for most of my FC. Ironaically they are all spectrum users...

https://onedrive.live.com/embed?resi...HULKoh7XSLdy_4

Quote:

Originally Posted by Janyd

I thought the issues had returned for my ISP, but turns out a Windows Update caused the "service host network service" to have high network usage via "delivery optimization" in Windows 10.

Went to check my retainers and noticed my ping was above 110ms, so I did a traceroute and it showed much higher ms on nodes well before NTT, so that told me something else was afoot. Then I opened Task Manager, and saw the culprit was indeed a Windows program called "service host network service" was gobbling up way more bandwidth than necessary.

So, after some YouTube searches, I used the command prompt "sfc /scannow" and that cleared up some files that must've been corrupted during the recent Windows Patch Tuesday. Took a few minutes to run, so some patience was required.

One restart later, and my latency's back to normal for FFXIV (around 59 to 64 ms).

Not sure if that'll help anyone else here, but it never hurts to check your PC to see if any Windows Updates of late messed with something. Chances are, knowing Microsoft, that's always a possibility.

Thank you for sharing this, I'm going to give it a try to help my own case!

~*~ • ~*~

Quote:

Originally Posted by Nekoyurei

Getting the same thing here. I was in a raid, and it seemed like everyone was running and stopping, running and stopping, and I couldn't click on any commands.

Quote:

Originally Posted by StouterTaru

Same thing here, people rubber-banding around, interactions take several seconds to process, etc

Quote:

Originally Posted by Kalania

having the same problem, game was acting normally when I was on earlier.

Exact same for me today. I was working on 2 characters, just to do a couple roulettes each and set up Island Sanctuary for the week.

Character 1: I ran an Expert and set up Island Sanctuary workshops without issue. Queued into an Alliance Roulette (Syrcus Tower) and was put into Slideshow Disconnect mode. (I saw Glasys' enrage for the first time ever! I was not suffering alone) I could still TRY to use my own actions and spells, but none of it was hitting the servers. No damage dealt, no healing put out, no MP spent. But user-end displays, like cooldown counters and personal animations, were still playing just fine.
I think I ended up disconnecting 5 times total during that Syrcus Tower run, and I count my blessing that I got the roulette completion rewards despite it all. Not that I'm happy I had to get carried through an ARR Alliance Raid, but I would have been miserable to have kept trying that much, to work around something outside my control, and gotten nothing for it. You know?
I visited retainers, and my FC chest to deposit some items, and even donig that alone in a personal house was 3+ seconds per input/confirmation.

Character 2: After the grief I went through on Character 1, I didn't bother even trying any combat content. I just wanted to make sure my Island Sanctuary was set for the week. The lag persisted and it took me over 30 minutes to get my schedules set up, waiting for selections to update, presets to save, and menus and confirmations to respond. I still need to work on my PvP Series, so possibly missing my daily Frontlines Roulette is stressing me out right now.

Yep, same here. The issue is on the serverside. European player on NA DC, just completely unplayable. Nothing we can do as players other than beg Square Enix to please at least acknowledge the issue, at best tell us what they're doing to fix the issue. Maybe even butter us up with some free days (totallynotjustbecauseineedafewmoredaystogrindsomething)

Crossing my fingers, it seems back to normal to me. (I am on cox internet btw)

Nope: I spoke too soon. It acted normal for 10 minutes than lagged and kicked me from the game.

I'll post again in a bit with some tracert results, but for now:

I tried Janyd's recommendation, and it feels like it helped a little but I'm also very much still experiencing XIV-specific lag that's making the game unplayable.
Shout out to the Frontlines team that had to deal with me while I learned the Win10 repair wasn't my solution. (We came in 2nd, and my end score was an unprecedented 0-4-0; I've literally never failed to rack up even a single Assist, this lag robbed me of multiple aoe hit credits lol)

I don't think I've ever posted here, but just wanted to lend my voice to the lag situation right now. Just started happening to me tonight and I'm on Cox internet. Not sure if it's normal to get no returns from some hops from tracert when doing the NA datacenter or whether that's a result of even higher lag on those hops. Gets bad starting at 10 and 11.

https://i.imgur.com/Yh0Qev8.jpg

I have approximately 50% packet loss pinging Crystal.

I should mention that I'm on Windows 11. (so the above fix mentioned won't actually run for me; Windows won't let me do it)

Okay, so far the problems affecting Spectrum, Cox, and Comcast users that I've seen here and on r/FFXIV don't seem to be affecting me.

I'm on AT&T, for full transparency, and May/June was a bad time for me and so many AT&T users, so my heart goes out to all of y'all affected.

Here's my recent traceroute, starting with the NTT nodes for privacy's sake:

8 25 ms 25 ms 26 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 * 26 ms 25 ms ae-3.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.23]
10 63 ms 56 ms 52 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 70 ms 76 ms 63 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 63 ms 76 ms 62 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 64 ms 63 ms 63 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * * Request timed out.
15 63 ms 62 ms 62 ms 204.2.29.122

The ping was so horrendous that not even VPN/ping reducer could fix it, I had 100% packet loss regardless. 11/10 server quality.

Getting hi ping off the .ntt hops :(

Present tracert Results

Got around to running some tracert tests.
For those unfamiliar, you can do so as well. On Windows:

Quote:

Command Prompt (Admin) > tracert full.ip.address

I checked against 3 different IPs for Aether (204.2.29.6, 204.2.229.9, 204.2.29.122)

I like to run the tests multiple times, in the event of outlier hiccups.
First bounces removed for privacy.
Code boxes to help mitigate this post's unruly length.

It's become difficult to find the correct, updated information, both on official and unofficial sites.

I started with 204.2.29.6, which may be outdated. It was listed for Aether a few places. (ARR Status, June of this year in this very thread)

Code:

TEST 1 of 5 6 10 ms 11 ms 11 ms 64.15.5.82 7 11 ms 11 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 22 ms 13 ms 12 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 12 ms 12 ms 134 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 36 ms 36 ms 34 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 33 ms 36 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 202 ms * 250 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 84 ms 87 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 82 ms 84 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * * * Request timed out. 16 80 ms 91 ms 87 ms 204.2.29.6 TEST 2 of 5 6 13 ms 13 ms 11 ms 64.15.5.82 7 16 ms 11 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 14 ms 18 ms 12 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 13 ms 27 ms 11 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 41 ms 34 ms 36 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 * * 36 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 * * * Request timed out. 13 82 ms 82 ms 81 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 85 ms 82 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 81 ms * * 204.2.29.241 16 82 ms 81 ms 83 ms 204.2.29.6 TEST 3 of 5 6 11 ms 10 ms 12 ms 64.15.5.82 7 12 ms 26 ms 27 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 14 ms 30 ms 26 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 15 ms 13 ms 14 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 33 ms 33 ms 34 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 36 ms 43 ms 47 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 * * * Request timed out. 13 81 ms 82 ms 83 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 83 ms 85 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 83 ms * 88 ms 204.2.29.241 16 83 ms 83 ms 81 ms 204.2.29.6 TEST 4 of 5 6 11 ms 12 ms 11 ms 64.15.5.82 7 12 ms 11 ms 13 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 13 ms 12 ms 14 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 28 ms 28 ms 18 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 35 ms 35 ms 32 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 35 ms 32 ms 39 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 * 201 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 82 ms 83 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 87 ms 82 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * * * Request timed out. 16 81 ms 85 ms 80 ms 204.2.29.6 TEST 5 of 5 6 12 ms 12 ms 14 ms 64.15.5.82 7 11 ms 12 ms 11 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 20 ms 12 ms 11 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 13 ms 13 ms 13 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 35 ms 35 ms 33 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 36 ms 32 ms 42 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 219 ms 198 ms 186 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 84 ms 81 ms 81 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 83 ms 82 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * * 81 ms 204.2.29.241 16 83 ms 81 ms 80 ms 204.2.29.6

Second batch of tests, run to 204.2.229.9. This may also be incorrect (lobby server, not data center server) but it cropped up often in search results.

Code:

TEST 1 of 5 6 11 ms 11 ms 11 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 12 ms 9 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 15 ms 24 ms 22 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 12 ms 13 ms 13 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 92 ms 96 ms 89 ms ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 * * * Request timed out. 12 98 ms 98 ms 99 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. TEST 2 of 5 6 11 ms 12 ms 12 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 16 ms 26 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 18 ms 11 ms 12 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 13 ms 19 ms 12 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 95 ms 93 ms 85 ms ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 94 ms 89 ms 84 ms ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183] 12 99 ms 100 ms 98 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. TEST 3 of 5 6 16 ms 16 ms 11 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 12 ms 12 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 18 ms 11 ms 11 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 14 ms 13 ms 13 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 87 ms 85 ms 89 ms ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 92 ms 94 ms 88 ms ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183] 12 110 ms 101 ms 99 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. TEST 4 of 5 6 13 ms 13 ms 13 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 15 ms 15 ms 11 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 12 ms 17 ms 13 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 22 ms 15 ms 12 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 90 ms 86 ms * ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 86 ms 90 ms 89 ms ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183] 12 108 ms 103 ms 112 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. TEST 5 of 5 6 130 ms 104 ms 40 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 108 ms 80 ms 58 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 131 ms 122 ms 190 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 15 ms 14 ms 14 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 89 ms 85 ms 85 ms ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 85 ms * 84 ms ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183] 12 100 ms 99 ms 101 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.

Third and final batch of tests, run to 204.2.29.122 (per the IP addresses listed in this 2022 official News-Topic post)

Quote:

IP addresses for each of the physical data centers are as follows:
Japan: 124.150.157.15 (traceroute 124.150.157.15)
North America: 204.2.29.122 (traceroute 204.2.29.122)
Europe: 80.239.145.101 (traceroute 80.239.145.101)
Oceania: 153.254.80.65 (traceroute 153.254.80.65)

Code:

TEST 1 of 5 6 12 ms 11 ms 12 ms 64.15.1.88 7 11 ms 10 ms 24 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 12 ms 19 ms 11 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 15 ms 13 ms 14 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 34 ms 32 ms 40 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 34 ms 36 ms 33 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 253 ms * 246 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 80 ms 82 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 86 ms 82 ms 86 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 84 ms * * 204.2.29.241 16 81 ms 81 ms 89 ms 204.2.29.122 TEST 2 of 5 6 13 ms 11 ms 13 ms 64.15.1.88 7 29 ms 17 ms 25 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 11 ms 11 ms 14 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 15 ms 12 ms 15 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 * 33 ms 33 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 34 ms 34 ms 40 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 191 ms 173 ms 170 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 86 ms 81 ms 80 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 81 ms 82 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * 82 ms * 204.2.29.241 16 83 ms 81 ms 81 ms 204.2.29.122 TEST 3 of 5 6 12 ms 13 ms 13 ms 64.15.1.88 7 13 ms 13 ms 14 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 13 ms 14 ms 13 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 14 ms 13 ms 12 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 40 ms 36 ms 34 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 33 ms 33 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 242 ms 220 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 81 ms 80 ms 80 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 81 ms 79 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 81 ms * * 204.2.29.241 16 80 ms 87 ms 80 ms 204.2.29.122 TEST 4 of 5 6 11 ms 14 ms 10 ms 64.15.1.88 7 17 ms 18 ms 15 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 29 ms 26 ms 24 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 13 ms 14 ms 13 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 36 ms 32 ms 45 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 34 ms 34 ms 33 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 * * * Request timed out. 13 80 ms 85 ms 81 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 81 ms 81 ms 87 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 79 ms * * 204.2.29.241 16 80 ms 80 ms 80 ms 204.2.29.122 TEST 5 of 5 6 12 ms 12 ms 12 ms 64.15.1.88 7 13 ms 13 ms 11 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 19 ms 13 ms 12 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 16 ms 16 ms 23 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 35 ms 34 ms 34 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 33 ms 33 ms 34 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 157 ms 157 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 80 ms 81 ms 81 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 81 ms 81 ms 81 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * * * Request timed out. 16 83 ms 82 ms 81 ms 204.2.29.122

OTHER INFO
Physical Location: NE USA
ISP: Optimum
Connection: Wired
Router: Yes (Updated, Restarted, Working Properly for ALL Internet in Household)
OS: Windows 10 (Updated, Restarted, Repair Check Run & Executed, Restarted)

My connection speeds are around
70-80 Mbps Download
30-40 Mbps Upload
(These have been consistent for years on the same service)

For FFXIV, I primarily play on Aether (Midgardsormr).

So my issues seems to have resolved themselves. Maybe it was an issue with cox in my area.

Seems so for me as well? Wishful thinking it was a fluke incident and got resolved silently but I'll take any boon I can get.

I'm getting about a half second of lag, on the US East Coast. Haven't had lag this bad in a long while. I'm hoping it's not a new routing problem....

https://i.imgur.com/1qBhpfh.png

I've been following this thread since it's conception to see if it gets resolved without the use of VPN. (I don't have the issue, UK here)

I just wanted to say that I hope it gets resolved for you all having to pay for a VPN to play 14!

SE please fix this with NTT

Heres my submission as well. Same issue terrible lag all day.

https://i.postimg.cc/GmyvSLHJ/Screen...-14-021755.png

Would be nice if SE did something about this and got it fixed. This is an interesting read as well. Perhaps emailing NTT as well since SE wont probably ever get to it. We pay for a sub but I guess them handling network issues isnt covered...

https://www.reddit.com/r/ffxiv/comme...lity_to_north/

Before I went to sleep, ping seemed to be stable again. It's 10:30 AM BST and it's back to 400 ms, slowly stabilizing itself. What gives? NTT servers, that's what. This is unacceptable.

https://media.discordapp.net/attachm...7007/image.png

https://media.discordapp.net/attachm...1834/image.png

5am EST struck and I spent the entirety of a Euphrosyne run in limbo. I got to watch the entirrrre raid, but from the seat of 17min behind everrrrryone else. I was able to talk to people in active time but that's all... I can't post any fancy feedback because I'm an PS5 user but this crap stole 7hr from me yesterday too. It's getting so bad that I can't even look forward to Dawntrail. Instead I'm contemplating quitting and giving up my most prized possession in the process, my lavender beds mansion... Why should I waste my limited funds and time if I can't even play?! ><

Follow-up tracert Results

Popping in today with an update.
My game connection appears to be stable and functional tonight!

I did run a tracert to each of the 3 IPs I did before, just for comparison:

204.2.29.6

Code:

6 12 ms 12 ms 12 ms 64.15.5.82 7 11 ms 13 ms 20 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 13 ms 20 ms 17 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 14 ms 12 ms 14 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 34 ms 40 ms 35 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 41 ms 40 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 78 ms 82 ms 80 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 92 ms 88 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 86 ms 85 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * 81 ms * 204.2.29.241 16 83 ms 84 ms 83 ms 204.2.29.6

This result is consistent with the results I was getting yesterday. Same locations, same general communication times - except for the 12th hop, at 129.250.5.17. My results yesterday for that hop were consistently 200+, or timing out.

204.2.229.9

Code:

6 12 ms 18 ms 17 ms rtr3-tg10-1.wan.whplny.cv.net [64.15.0.42] 7 17 ms 29 ms 11 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 15 ms 16 ms 13 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 14 ms 16 ms 13 ms ae-2.r20.nwrknj03.us.bb.gin.ntt.net [129.250.3.50] 10 88 ms 85 ms 87 ms ae-9.r20.londen12.uk.bb.gin.ntt.net [129.250.6.146] 11 86 ms 86 ms 87 ms ae-1.r21.londen12.uk.bb.gin.ntt.net [129.250.2.183] 12 102 ms 100 ms 99 ms ae-16.r20.frnkge13.de.bb.gin.ntt.net [129.250.3.13] 13 * * * Request timed out. 14 * * * Request timed out. 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. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.

This result is also consistent with my tests run yesterday.

204.2.29.122

Code:

6 13 ms 19 ms 13 ms 64.15.1.88 7 13 ms 16 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89] 8 13 ms 15 ms 12 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78] 9 16 ms 12 ms 12 ms ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.3.129] 10 39 ms 34 ms 33 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166] 11 43 ms 36 ms 34 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27] 12 77 ms 99 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 13 82 ms 83 ms 84 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57] 14 86 ms 81 ms 80 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18] 15 * * * Request timed out. 16 81 ms 81 ms 91 ms 204.2.29.122

These results are mostly consistent with yesterdays - except, again, the 12th hop at 129.250.5.17, which was often at 200+ or timing out yesterday.

To me, it looks like that particular node was having some sort of issue, which has now been resolved!

What is the point of this forum? clearly nobody at square enix is looking at this. more than 1 month ever since this problem has plagued my gameplay and they literally did nothing. I'm guessing they dont need to fix anything or bother since Square enix is suffering from success with all these failed games! So why even bother fixing this one, too?

Edit: i never had such lag, packet loss and disconnects since heavensward. crazy to me that they dropped the ball this hard and now they wont even bother.

Just gonna add onto this post since this is an issue I've had back in June, and it's happening again. Where the ping is just permanently locked at 100+ (average is 115 but reached as high as 150). I noticed I was lagging again so i did what I did last time: a bunch of cmd tests over a period of 2 hours. Thank goodness the servers decided to act up during a lull in content this time unlike last time. Regardless, this is still pretty annoying to deal with. I've paid for this game very single month since 2021, I shouldn't just be barred from playing in the free time I do have because of something out of both me and my ISP's control (Cox). Like a user mentioned above, this thread having 131 posts and counting is just a failure on SE's part to actually fix the issue.

This is back for me since today, everything freezes every like 5 seconds and then quickly catches up

Quote:

Originally Posted by yaii

This is back for me since today, everything freezes every like 5 seconds and then quickly catches up

Yes. for the last 3 days the lag and packet loss are making the game unplayable.

Are you playing in the US? That’s really weird! I see UK and DE (can’t remember which country that is) in there too! I’ve been noticing the lag ramp up again lately, I’ll have to run another trace when I get home. Usually my problems are in Sacramento and San Jose within NTT’s network, but your route is going from VA and then in the total wrong direction!

Atleast they announced that they want to put their servers on cloud servers and not their own physical ones. thanks god. maybe this issue will resolve in couple of months when they implement their cloud servers because i'm sure they are not competent at all to manage any physical servers as you can see.

I am experiencing severe lags all the time, and it got much worse with todays patch, every few moments in a dungeon i get a lag up to 5 seconds and can't use any skills. Everything is standing still and then plays in a time lapse to catch up.
Its bee like this for months, please do SOMETHING, the game becomes unplayable.
Even Triple Triad is lagging right now

Today has been nearly unplayable. The server managed to stay mostly stable for the new alliance raid, but since 6:45 PM EST I've had huge lag spikes every nine minutes, almost on the dot. I guess I'll go play something else and come back tomorrow and try again... This is getting silly..

Edit: was fine for early Wednesday (2023-10-04), but was dying every 2-4 minutes for me since 8:51 PM EST. Unplayable for the rest of the evening.

Edit #2: same deal tonight (2023-10-05), but it started at 3:43 PM EST, and the lag spikes are almost exactly three minutes apart.

Guess we're back at it again. San Jose node is messed up again

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

Yeah issues for me are popping up too, was even having difficulty connecting to the server from the launcher itself.

Quote:

Originally Posted by Rehayem

Guess we're back at it again. San Jose node is messed up again

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

Can confirm, mine is dying at either 204.2.29.7 or 204.2.29.241, both NTT San Jose IPs.

Even a VPN isn't helping anymore. JFC.

Question, would this also cause minor stuttering issues?

Quote:

Originally Posted by Omegaher0

Question, would this also cause minor stuttering issues?

For me, it can range from a 2-3 second stutter all the way to a 60-90 second stutter that results in a 90006 or 90002 disconnect.

Quote:

Originally Posted by jazix

For me, it can range from a 2-3 second stutter all the way to a 60-90 second stutter that results in a 90006 or 90002 disconnect.

Ever since patch 6.4, I have been having fps stuttering issues, mainly a 4-5 fps drop for a second then back to normal for a while. Could this be caused by the server issues?