Bad lag again with NTT's NA server network

[brnslpy]

Pretty terrible latency for a network that has no player traffic going to it:

traceroute to 204.2.29.122 (204.2.29.122), 64 hops max, 72 byte packets
1 [redacted] ([redacted]) 12.537 ms 3.684 ms 3.203 ms
2 [redacted] ([redacted]) 3.866 ms 3.319 ms 4.276 ms
3 [redacted] ([redacted]) 4.879 ms 4.076 ms 5.119 ms
4 71.152.134.114 (71.152.134.114) 7.250 ms 5.119 ms 5.173 ms
5 * * *
6 32.130.17.77 (32.130.17.77) 20.292 ms 14.417 ms 15.852 ms
7 cgcil402igs.ip.att.net (12.122.132.197) 12.039 ms 15.287 ms 15.897 ms
8 192.205.32.194 (192.205.32.194) 60.628 ms 60.842 ms *
9 ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239) 63.882 ms 60.697 ms *
10 ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 59.614 ms 59.905 ms 54.193 ms
11 ae-4.a00.scrmca03.us.bb.gin.ntt.net (129.250.7.57) 114.971 ms 114.726 ms 121.466 ms
12 * xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 122.276 ms 115.269 ms
13 204.2.29.241 (204.2.29.241) 114.816 ms 114.444 ms 114.083 ms
14 204.2.29.122 (204.2.29.122) 114.830 ms 114.199 ms 113.991 ms

If you pop in the host names from Line 6 and Lines 9 to Line 11 into web search, there are ATT forum posts from the last few years complaining about these same nodes.