Bad lag again with NTT's NA server network

[UtterEast]

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

[Ayedin]

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.

[Jehiren]

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

[gothxbrooks]

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.

[ThatVarkYouKnow]

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

[Morne]

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

[Khryseis_Astra]

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!

[djhollowpoint]

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!

[Aexnidaral]

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

[Janyd]

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