Bad lag again with NTT's NA server network

[Lahtori]

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

[Suimetsu]

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 -

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

[QS_W]

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

[gimmeoliver]

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.

 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

[Tadeusz]

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.

[jazix]

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

[Zebeedoo]

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.

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