Bad lag again with NTT's NA server network

[owlcall]

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

[Krojack]

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


2024-02-07 @ 9:25pm EST
Yellow = VPN average packet loss
Blue = no VPN average packet loss


MTR without using VPN.

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

# 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

[Janyd]

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.

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

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