Bad lag again with NTT's NA server network

[DivineP]

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!

[Jibs]

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







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/

[Rehayem]

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.

[Duelist_Neko]

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?! ><

[NaiaLalita]

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

  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

  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

  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!

[Maru_Schwarzlicht]

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.

[Sols]

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.

[yaii]

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

[Szylver]

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.

[Khryseis_Astra]

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!