Bad lag again with NTT's NA server network

[TaleraRistain]

Here's that section on my friend, not sure if Dallas, but in Texas with Optimum. Not hitting that same node we're all showing issues with.

7 * * * Request timed out.
8 58 ms 52 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 54 ms 56 ms 56 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 61 ms 79 ms 54 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 54 ms 54 ms 54 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 59 ms * 204.2.29.241
13 55 ms 57 ms 53 ms 204.2.29.6

This is also mine last night around 3 or 4 am when things were smooth enough to play. But nowhere near that same jump they're trying to say is expected going from Texas to Sacramento for that same node at that time.

8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 68 ms 55 ms 57 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 59 ms 61 ms 59 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 60 ms 59 ms 59 ms 204.2.29.6

[Ath192]

Here's that section on my friend, not sure if Dallas, but in Texas with Optimum. Not hitting that same node we're all showing issues with.

7 * * * Request timed out.
8 58 ms 52 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
9 54 ms 56 ms 56 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
10 61 ms 79 ms 54 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
11 54 ms 54 ms 54 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * 59 ms * 204.2.29.241
13 55 ms 57 ms 53 ms 204.2.29.6

This is also mine last night around 3 or 4 am when things were smooth enough to play. But nowhere near that same jump they're trying to say is expected going from Texas to Sacramento for that same node at that time.

8 8 ms 8 ms 9 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
9 68 ms 55 ms 57 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 59 ms 61 ms 59 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 60 ms 60 ms 60 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 60 ms 59 ms 59 ms 204.2.29.6

Well actually I can't hit 128.241.2.18 without dropping packets so. To me what NTT said is true and it's on ATTs side. I also don't go through node 57.

Like, its very well true that the drops are probably happening when ATT hands off the traffic to NTT but the equipment that's doing the hand off must be the problem and not the NTT equipment receiving it. Otherwise like in the previous post the NTT tech would've had problems pinging their own equipment in sacramento, which he didn't. Further more, the Optimum connection listed here passes through NTT with no issue right, and it passes through the node I am dropping packets on.

To me this is ATT.

Here is mine, by all accounts its awfully similar to the Optimum in Texas with no issues.

4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 28 ms 31 ms 31 ms 32.130.25.67
8 26 ms 27 ms 27 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 * * * Request timed out.
10 108 ms 114 ms * ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 152 ms 117 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 117 ms 117 ms 116 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 118 ms 118 ms 118 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 118 ms 119 ms 204.2.29.241
15 117 ms 118 ms 117 ms 204.2.29.87

Trace complete.