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.