Bad lag again with NTT's NA server network

Quote:

---

Originally Posted by Zhexos

Greetings,

We are aware that some players may be experiencing network-related issues such as frequent stuttering or significant latencies, which may be caused by packet loss.

If you feel you may be experiencing packet loss while playing FFXIV, we kindly ask that you submit a report through the "Providing information on packet loss and lag" section at the bottom of our support form. Instructions on how to obtain your traceroute information can be found in this Lodestone announcement.

We will be referencing these reports on a regular basis as we continue our investigations and contact telecommunication carriers as necessary.

We appreciate your cooperation as we continue striving to address network-related issues that players may be experiencing.

---

With all due respect, this has been going on for nearly a year for me personally, and from what I've seen, I'm one of the lucky ones, as it's been going on for years for some people. At what point does this become unacceptable and something is actually *done* about it?

Quote:

---

Originally Posted by Luranis

With all due respect, this has been going on for nearly a year for me personally, and from what I've seen, I'm one of the lucky ones, as it's been going on for years for some people. At what point does this become unacceptable and something is actually *done* about it?

---

I'd like to echo this. I've been experiencing this issue since before Endwalker came out, and at this point I'd expect some information beyond the standard "we're looking into it". I can only hope the cloud server test is a success and SE allows free transfers to it once they're live.

Edit: It's dying every 3 minutes on the dot, starting at 5:04 PM EST today, 2023-11-25. If you need live data, please try right now.

Several months later, I still have to play this game through a proxy to get normal ping. Regular connection still sits at 100+ on some nights (it should be 50), with occasional drop outs. Pretty crazy how this still hasn't been solved.

I was aware this happened roughly 6-7 months ago and it has been happening again for the past 3-4 weeks where people in game stop for like a second then goes back to normal and happens every 10-15s.

I was hoping it would have been resolved by now but clearly it looks like it is here to stay.

It's completely out of my control which is the frustrating part.

Quote:

---

Originally Posted by KisalaSaizuki

I was hoping it would have been resolved by now but clearly it looks like it is here to stay.

---

Yup, it seems that way. I really feel bad for the console players because doing a proxy connection through your router doesn't seem very easy... or even possible on some models?

Just chiming in, network connection for me has been mostly stable since the major debacle back in.... whenever that was, sometime in the Summer I think. Around a month or two ago, I started having bad connections only when I joined high-end content and during peak hours of that content; I think Square/XIV just doesn't have enough good routing capacity for high-end instances being made, since all other content, normal raids included, my connection would be fine.

The current problem now is that ever since yesterday, on fun ol' happy Christmas, my connection has been bouncing between 110-120ms and spiking into the 150's for no reason at all. Thanks NTT, for being utter garbage trash and thanks Square, for using my subscription money on trash games that don't pertain to making XIV better.

As it stands, I'm once again forced to use a VPN for a better connection and I'm kind of tired having to play the wondering game when I come online and hoping I don't need a VPN to just enjoy a quality connection.

Please fix your trash, this is absurd. My standard connection to a server from N.E Ohio -> California is around 50ms, with XIV I'm used to 60ms. Do better.

I had to just go the extreme fix this myself.

I already had a VPN that I pay for that allows up to 5 concurrent connections. I setup my OPNsense router/firewall with an OpenVPN setup and any outbound traffic from my home network going to an IP within 204.2.28.0/22 gets sent out though my VPN. This would be the only way that I know of for console players to get around these ping problems. They would need a router that supports a VPN that has nodes to get around these bad pings. It took me some testing using the PC VPN client to find the best nodes for my VPN provider.

This is the ping stats for 1 hour (2023-12-26 @ 7 to 8:22pm EST) both normal and though VPN to the FF14 servers. Red & Green are pings though normal Internet. Purple & Green are though the VPN. You can see how the VPN is far more stable.

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

I have sent in many reports though their website with the data they want but it results in nothing ever changing. I forever need to use a VPN to play this game in the evenings.

P.S. the high and erratic pings only start once you're inside the NTT network within the last 4 hops. I have never had problems on any other game like this ever.

It's both good to see you, and at the same time, unfortunate that you had to appear.

I'm a European player, but still playing on Sargatanas as I was migrated there from 1.0 and have all my friends / LS stuff there, but since a few months I do experience the same issues.
Especially in dungeons/raids the stuttering is very clear. Mobs/characters not moving for 0.5-1s every few seconds, my Red mage acting up (instead of the slow/fast/slow/fast spells it often goes slow/slow/slow) or using swift cast -> raise still starts to cast slowly after using the swift cast.

I never really had these kind of issues until like 2-3 months ago?

I've tried using my alt character on a EU server, but I see the same issues there.

Quote:

---

Originally Posted by KisalaSaizuki

I was aware this happened roughly 6-7 months ago and it has been happening again for the past 3-4 weeks where people in game stop for like a second then goes back to normal and happens every 10-15s.

I was hoping it would have been resolved by now but clearly it looks like it is here to stay.

It's completely out of my control which is the frustrating part.

---

I indeed notice exactly the same thing, while I'm playing from a Belgian (European) network. So it's not only in NA where the issue pops up it seems.

Quote:

---

Originally Posted by Finalfreak

I indeed notice exactly the same thing, while I'm playing from a Belgian (European) network. So it's not only in NA where the issue pops up it seems.

---

As a player who has been playing XIV since 2015 this is really frustrating, it happened 6-7 months ago and lasted 2-ish weeks, atm it has been going on for 4-ish weeks now. As an EU player this is also frustrating as i just want to play.

If this persists past the next main patch and no long term solution is found i may consider removing my sub. I enjoy the game, content, friends etc but feel this should not be an issue regardless where you connect from or what platform you're on. SE have a responsibilty to their playerbase and should set a fire under AT&T/NTT for such persistant issues because god forbid this becomes a more serious and widespread issue and causes them a massive headache.

Quote:

---

Originally Posted by KisalaSaizuki

As a player who has been playing XIV since 2015 this is really frustrating, it happened 6-7 months ago and lasted 2-ish weeks, atm it has been going on for 4-ish weeks now. As an EU player this is also frustrating as i just want to play.

If this persists past the next main patch and no long term solution is found i may consider removing my sub. I enjoy the game, content, friends etc but feel this should not be an issue regardless where you connect from or what platform you're on. SE have a responsibilty to their playerbase and should set a fire under AT&T/NTT for such persistant issues because god forbid this becomes a more serious and widespread issue and causes them a massive headache.

---

I’m having the same issues with the same timeline. I'm in central USA using AT&T fiber playing on Primal and FFXIV is literally my only internet issue. My issues begin at ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]/ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7].

Without a VPN, the game is like a slideshow with 5-10+ second delay spikes. I used to be able to reduce the delay to 1-2 seconds using a VPN, but I’m now getting 2-4+ seconds of delay at best, often with dropped input.

Having the same issue as the above two...AT&T fiber, eastern USA. This happened the same time last year and lasted a month or so. Sorry but this is ridiculous, paying for an unplayable game, so tired of this. I think I'm just going to let FFXIV give up the ghost.


9 61 ms 66 ms 66 ms ae-8.a02.atlnga05.us.bb.gin.ntt.net [129.250.8.197]
10 61 ms 61 ms 64 ms ae-8.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.66]
11 30 ms 29 ms 30 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
12 29 ms 28 ms 28 ms ae-0.r22.dllstx14.us.bb.gin.ntt.net [129.250.2.59]
13 * * * Request timed out.
14 91 ms 75 ms 126 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
15 70 ms 81 ms 69 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
16 70 ms 69 ms 70 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 * * 69 ms 204.2.29.241
18 69 ms 69 ms 69 ms 204.2.29.122

It's been a while for me, but tonight both me and my partner got hit with latency issues in TOP. Partner was around 7:30pm CST and I got hit with a wave at 9:00pm CST. Only FF14 was affected, as per the usual (cause it's NTT sacramento causing issues). Outside of instance seems to be stable for now, but it's just annoying that this node is causing hardships for everyone.

i speak for myself was with at&t for many years when i moved to central florida and picked up spectrum my service got way better.

I am on Comcast and having the same issue :-)

It was fine for upwards of two weeks, but tonight I can't connect longer than a minute or two before being kicked. It started at exactly 7 PM EST. I don't know how many more accounts of issues that SE needs, but here's another one. Check your network right this second and you'll see the issue...

Once again me and my Wife are experiencing the same packet loss issues that we all experienced back in May/August of 2023. Issue to us is a little better since but sometimes during peak player hours the lag just hits off and on and constantly get 3 to 5 sec lag jumps every probably 20 secs. Below is the results from my tracert route cmd. Currently 10:37pm EST on Saturday, been like this to my knowledge for the past 2 hours.

1 1 ms 1 ms 1 ms
2 21 ms 30 ms 13 ms
3 51 ms 25 ms 21 ms
4 * * * Request timed out.
5 * * * Request timed out.
6 32 ms 36 ms * 32.130.89.25
7 49 ms 67 ms 62 ms 192.205.32.210
8 49 ms 76 ms 47 ms ae-10.r23.chcgil09.us.bb.gin.ntt.net [129.250.3.37]
9 118 ms 119 ms 126 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 132 ms 164 ms 129 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 118 ms 117 ms 169 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 98 ms 169 ms 99 ms 204.2.29.122

I want to note, when we had this issue back in May 2023 we were on a different provider and switched. Issues are still happening with the new provider. Went from AT&T to a private internet provider provided were we live. Our connection is PERFECTLY fine with every other game we play. Its NOT our ISPs, there is something clearly wrong with how these NTT servers are routing packets and its NOT handling the server load at all.

I have tried opening ports provided by the moderator in the forum post like below. Didn't make a difference for me. May make a difference for others.
https://forum.square-enix.com/ffxiv/...077-NA-bad-lag.

I subbed to NordVPN back in May for abit before my wife and I took a break due to these issues. We aren't going to do that again. Cloudflare maybe the free option but when I tried it seems unreliable if to maybe others are using it too. THIS IS NOT A FIX.
Hoping maybe those East Coast cloud servers coming will make a huge difference...

Square needs to double down on NTT and figure out where the issue is.

Original OP person here chiming in once again.....

Yes this is still going on for my connection. Like I said here in an early reply, I've had to start using a VPN if I wish to play this game in the evening times from 8pm till midnight give or take an hour.

This is the bad lag from tonight Jan 13th, 2024.
Left graph: The high peeks with red are ping times from my connection to the server. The purple line is though my VPN. It's 100% stable.
Right graph: This is the packet loss without VPN. While higher pings is one thing, packet loss is what makes the game unplayable.
https://i.imgur.com/AlCTQdE.jpg

I still have AT&T fiber. Sorry but I won't be going back to Spectrum cable. It's extremely slow and over priced. This problem is 100% NTT's network. Again, they NEED to resolve this.

I genuinely cannot believe this issue continues to persist this long. Spectrum from the East Coast (Florida). Relevant section of the traceroute:

10 42 ms 41 ms 40 ms ae-4.r22.dllstx14.us.bb.gin.ntt.net [129.250.2.219]
11 * * * Request timed out.
12 111 ms 107 ms 107 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
13 163 ms 171 ms 162 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
14 169 ms 167 ms 172 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]

Kind of insane that I have to pay for a third party tool -- a VPN -- to reroute my connection to your servers in order to play the game.

Once more... I'm so tired of this garbage. How many more years of complaining from your NA customers will you take before finally looking at NTT?

6 58 ms 55 ms 56 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
7 53 ms 51 ms 53 ms ae-6.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.118]
8 * 128 ms 53 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 95 ms 83 ms 80 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 86 ms 90 ms 89 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 101 ms 99 ms 91 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 65 ms * * 204.2.29.241
13 94 ms 93 ms 92 ms 204.2.29.6

I haven't really had issues in the past few months, as far as NTT goes, until 6.55 dropped. I don't get routed through Virginia anymore (which is great), but occasionally my new route through Atlanta doesn't look so hot.

Periodically I'll get run ins with something like this - https://cdn.discordapp.com/attachmen...ebc70d7bea3a1&

(As a side note Hop 2 is the local CMTS that ignores all pings & what not and Hop 5 is always ignoring most traces & what not so its packet loss is not a factor as it does this with other routes).

While my latency from the East Coast is rather solid all things considered, getting spikes of even 1-2% packet loss in spurts is really bad, especially when you're trying to not wipe your raid in Unreal or Savage.

It is getting worse and worse right now. Easily 480ms with 50%+ packetloss =.=

1 1 ms 1 ms 1 ms 192.168.50.1
2 5 ms 5 ms 4 ms 183.90.49.1
3 5 ms 4 ms 4 ms 182.19.151.117
4 9 ms 4 ms 4 ms 183.90.44.45
5 4 ms 4 ms 4 ms 203.118.7.85
6 5 ms 4 ms 4 ms 203.118.7.94
7 5 ms 6 ms 6 ms unknown.telstraglobal.net [210.176.138.173]
8 8 ms 6 ms 8 ms i-93.sgcn-core01.telstraglobal.net [202.84.219.178]
9 184 ms 185 ms 184 ms unknown.telstraglobal.net [202.84.143.122]
10 179 ms 177 ms 177 ms i-92.eqnx03.telstraglobal.net [202.84.247.17]
11 175 ms 175 ms 174 ms sjo-b23-link.ip.twelve99.net [213.248.75.146]
12 475 ms * 499 ms ntt-ic-323771.ip.twelve99-cust.net [62.115.12.53]
13 * * * Request timed out.
14 485 ms 485 ms 523 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
15 481 ms 480 ms 485 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
16 524 ms 517 ms 520 ms 204.2.29.241
17 485 ms 489 ms 497 ms 204.2.29.122

Getting really high latency again, started around last week. I connect to Crystal from Singapore and usually have around 170ms but have been at around 500ms with high amounts of packet loss and rubberbanding.

Code:

---

1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2    4 ms    4 ms    4 ms  183.90.54.1
  3    4 ms    4 ms    4 ms  183.90.44.213
  4    50 ms    75 ms    19 ms  183.90.44.173
  5    4 ms    3 ms    3 ms  203.118.7.73
  6    3 ms    4 ms    4 ms  203.118.3.69
  7    4 ms    4 ms    4 ms  unknown.telstraglobal.net [210.176.138.173]
  8    4 ms    6 ms    6 ms  i-93.sgcn-core01.telstraglobal.net [202.84.219.178]
  9  179 ms  177 ms  180 ms  unknown.telstraglobal.net [202.84.143.122]
 10  181 ms  182 ms  181 ms  i-92.eqnx03.telstraglobal.net [202.84.247.17]
 11  173 ms  173 ms  173 ms  sjo-b23-link.ip.twelve99.net [213.248.75.146]
 12  515 ms  499 ms  503 ms  ntt-ic-323771.ip.twelve99-cust.net [62.115.12.53]
 13    *      497 ms  507 ms  ae-10.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
 14  499 ms  497 ms  470 ms  ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
 15  512 ms  530 ms  526 ms  xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
 16  494 ms    *        *    204.2.29.241
 17  526 ms  526 ms  518 ms  204.2.29.122

---

Happening to me again at random. Normally sitting around 60ms connecting to Primal from the midwest US, however very often (even during the middle of the day on a weekday) I will get up to 120ms with huge, very noticeable packet loss. When will SE actually do something about this? It's just as much on them now as it is any provider. The Cloud Test worked great, so they *can* do something if they wanted to. This is the only game I have any issues with, it's insane.

Getting kicked constantly this morning. It's been so good but damn. Unplayable today.

i am playing from EU on NA (aether dc) and i got the 2002 error. i can connect to EU DC's just fine, but can't seem to connect to NA. i tried restarting the router and flushing the dns.

Ah shiz here we go again

I'd say I missed watching everyone in Radz-at-Han rubber banding around as this node choked on itself YET AGAIN but I'd be lying

Just noticed it's back to being what it was in May 2023. Steady rise in ping times and levels off with really bad unplayable packet loss.

2024-02-07 @ 9:25pm EST
Purple/Green = VPN pings that uses an alternate route into NTT's network.
Red/Green = no VPN pings
https://i.imgur.com/6KEZD47.jpg

2024-02-07 @ 9:25pm EST
Yellow = VPN average packet loss
Blue = no VPN average packet loss
https://i.imgur.com/yviQtRF.jpg

MTR without using VPN.

Code:

---

# mtr -w 204.2.29.90
Start: 2024-02-07T21:57:57-0500
HOST: Locutus                                      Loss%  Snt  Last  Avg  Best  Wrst StDev
  1.|-- 192.168.1.1                                  0.0%    10    0.3  0.2  0.1  0.3  0.1
  2.|-- 192.168.1.254                                0.0%    10    0.8  0.7  0.5  1.0  0.2
  3.|-- ???-???-??-?.lightspeed.??????.sbcglobal.net  0.0%    10    4.2  3.4  1.2  4.9  1.2
  4.|-- 71.152.134.90                                0.0%    10    3.4  3.7  2.4  5.4  1.2
  5.|-- ???                                          100.0    10    0.0  0.0  0.0  0.0  0.0
  6.|-- 32.130.89.25                                90.0%    10    7.9  7.9  7.9  7.9  0.0
  7.|-- 192.205.32.210                                0.0%    10  16.9  17.0  8.7  23.4  4.7
  8.|-- ae-10.r23.chcgil09.us.bb.gin.ntt.net          0.0%    10  10.1  16.7  10.1  27.0  5.0
  9.|-- ae-1.r24.snjsca04.us.bb.gin.ntt.net          20.0%    10  111.9 110.6 106.2 117.1  3.2
 10.|-- ae-4.a00.scrmca03.us.bb.gin.ntt.net          10.0%    10  112.9 116.0 110.2 140.3  9.6
 11.|-- xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net    0.0%    10  111.9 113.5 111.2 117.3  1.9
 12.|-- 204.2.29.241                                80.0%    10  111.4 108.6 105.8 111.4  4.0
 13.|-- 204.2.29.90                                  0.0%    10  112.0 109.2 100.8 113.8  4.2

---

MTR WITH VPN. Packet loss in hops 7 and 10 are normal. It's the others in NTT's network causing this problem.

Code:

---

# mtr -w 204.2.29.90
Start: 2024-02-07T22:02:18-0500
HOST: Locutus                                            Loss%  Snt  Last  Avg  Best  Wrst StDev
  1.|-- 192.168.1.1                                        0.0%    10    0.3  0.3  0.2  0.4  0.1
  2.|-- 10.24.112.1                                        0.0%    10  56.8  55.5  54.4  57.0  1.0
  3.|-- te0-3-1-4.rcr51.b023785-1.sjc01.atlas.cogentco.com  0.0%    10  55.0  56.3  55.0  57.7  1.0
  4.|-- be2360.ccr22.sjc01.atlas.cogentco.com              0.0%    10  56.9  56.7  55.1  58.2  1.2
  5.|-- be3144.ccr41.sjc03.atlas.cogentco.com              0.0%    10  58.6  56.7  55.3  58.6  1.1
  6.|-- ae-26.a03.snjsca04.us.bb.gin.ntt.net                0.0%    10  56.0  60.7  55.3  78.8  7.9
  7.|-- ???                                                100.0    10    0.0  0.0  0.0  0.0  0.0
  8.|-- ae-4.a00.scrmca03.us.bb.gin.ntt.net                0.0%    10  61.1  60.4  58.4  62.0  1.2
  9.|-- xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net          0.0%    10  61.9  60.9  59.5  62.1  0.9
 10.|-- 204.2.29.241                                      60.0%    10  59.4  60.6  59.4  61.4  0.8
 11.|-- 204.2.29.90                                        0.0%    10  58.8  59.7  58.3  61.8  1.2

---

Throwing on my traceroute here, starting at the NTT nodes.


8 46 ms 41 ms 44 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 42 ms 44 ms 43 ms ae-6.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.118]
10 54 ms 53 ms 55 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 117 ms 115 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 118 ms 118 ms 117 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 118 ms 119 ms 115 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 114 ms 114 ms * 204.2.29.241
15 116 ms 110 ms 116 ms 204.2.29.122


Looks like the California NTT nodes are at fault again, especially Sacramento's nodes.

Though I was unable to get a traceroute in with it, I do have T-Mobile 5G Home Internet now as a backup option, and I saw in ping tests that it hovered around 70-75ms most of the time.

Suffice it to say that this continues to be a routing issue with some ISPs such as AT&T that others may not have. For now.

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

miserable, it does seem to have been a relatively brief excursion at least

It has likely been mentioned before, but in case it hasn't or if this helps even one person, I highly recommend Mudfish. I'm on the east coast and I've been having the packet loss issues in the evening. I decided to try Mudfish because I was at the end of my rope. I'm so glad I did because it has completely fixed the packet loss issue for me. There is the very occaisional ping spike but the only reason I know it happened is because Mudfish's console has a ping graph.

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

Getting a recent spike in latency and packet loss at NTT again.

Quote:

---

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 1 ms 192.168.0.1
3 6 ms 5 ms 4 ms tukw-dsl-gw70.tukw.qwest.net [63.231.10.70]
4 8 ms 9 ms 15 ms tukw-agw1.inet.qwest.net [63.226.198.41]
5 * * * Request timed out.
6 6 ms 7 ms 6 ms 4.69.219.206
7 5 ms 6 ms 9 ms ae-10.a03.sttlwa01.us.bb.gin.ntt.net [129.250.9.180]
8 7 ms 6 ms 8 ms ae-3.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.206]
9 31 ms 28 ms * ae-3.r25.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
10 60 ms 58 ms 57 ms ae-8.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.155]
11 76 ms 76 ms 81 ms ae-4.r25.atlnga05.us.bb.gin.ntt.net [129.250.4.117]
12 * * * Request timed out.
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.

Trace complete.

---

here's mine today. so fun. myself and most of my alliance in thaleia today had such bad lag im shocked we made it through.

NA player here
The game has been virtually unplayable for about two weeks at this point
I've never seen a 90001 error before now, all content except for alliance raids has been constantly 90king and 2002ing
Idk how I can run 23 other players and it's seamless but I crash in a guildhest or msq roulette or (the worst of the lot so far) a guild room trying to access my glam dresser, but that's been how it's been and I'm so tired
Game will randomly lag spike even just walking around a city, or it freezes for a few seconds in a raid then it's fine again, up and down up and down with Sending and Receiving pings
I just want to be able to play the game again
Tried everything that mod messages have said to try, no dice
Last resort is a reinstall but I'd really hope not to have to do that

some more data for OP

I am having the same types of problems with latency.

I connect to Aether - Sargetanas from Australia so I don't expect the best ping but lately (the last few weeks) my ping has doubled and is making the game unplayable on my main toon.

My Tracert

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

I’m seeing the San Jose and Sacramento nodes acting up again… it was good for a few months, but now it’s back. Been laggy all week… :( Seems to clear up a little bit after midnight, but that’s not really a convenient time for me to play anytime other than a Saturday night!

Same thing happening to me. AGAIN. I hate that this keeps re-occurring! It's really hurting my static's progress in raids. SE please give NTT a call and get this fixed!

Issues with the Sacramento Node, yet again. Getting over 150 ping when I usually get 80/90.

Yep, looks like the Sacramento node is starting to go back into its bad habits again.

The spikes are around 100ms. Brief but noticeable.

EDIT: Pasting my most recent traceroute, starting at the first NTT node.

8 29 ms 28 ms 29 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 * * * Request timed out.
10 56 ms 55 ms 55 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 98 ms 98 ms 114 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 101 ms 103 ms 105 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 99 ms 101 ms 99 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * * Request timed out.
15 102 ms 102 ms 106 ms 204.2.29.122