Bad lag again with NTT's NA server network

[Ath192]

If I were to put money on it, the issue is between ae-5.a00.dllstx14.us.bb.gin.ntt.net and ae-2.r20.dllstx14.us.bb.gin.ntt.net. I have two internet connections coming in, and on my spectrum line, I do not hit ae-5.a00.dllstx14.us.bb.gin.ntt.net and have not had issues in ~3 weeks. AT&T routing looks like:

Hop 4: 32.130.25.65
Hop 5: ae-5.a00.dllstx14.us.bb.gin.ntt.net
Hop 6: ae-2.r20.dllstx14.us.bb.gin.ntt.net

While spectrum looks like:

Hop 9: as2914.cr11-dal3.ip4.gtt.net
Hop 10: ae-2.r20.dllstx14.us.bb.gin.ntt.net
Hop 11: ae-2.r24.lsanca07.us.bb.gin.ntt.net

Here is the first post showing none of those though:

It's happening again. NTT having bad packet loss and lag all within their network. Please get this fixed once and for all.

Current packet loss.


Past 12 hours graphs. Can see when it start about 10:30am EST


Past 2.5 months.

(NTT made a change in early April that caused the average pings to increase by 5-10ms)

Still the only thing I can find in common so far is that people who are having problems are going through a 129.250.4.9 or a 129.250.4.239 address. If anyone can prove this is wrong lmk. You will also see that the known working optimum tracert does not include either of these.


*Update, first packet drop of the day recorded 10:45 AM -11 AM CST*

Reply from 204.2.29.86: bytes=32 time=120ms TTL=50
Reply from 204.2.29.86: bytes=32 time=110ms TTL=50
Reply from 204.2.29.86: bytes=32 time=121ms TTL=50
Reply from 204.2.29.86: bytes=32 time=107ms TTL=50
Reply from 204.2.29.86: bytes=32 time=114ms TTL=50
Reply from 204.2.29.86: bytes=32 time=109ms TTL=50
Reply from 204.2.29.86: bytes=32 time=115ms TTL=50
Reply from 204.2.29.86: bytes=32 time=118ms TTL=50
Reply from 204.2.29.86: bytes=32 time=122ms TTL=50
Reply from 204.2.29.86: bytes=32 time=117ms TTL=50
Reply from 204.2.29.86: bytes=32 time=117ms TTL=50
Reply from 204.2.29.86: bytes=32 time=120ms TTL=50
Reply from 204.2.29.86: bytes=32 time=111ms TTL=50
Request timed out.
Reply from 204.2.29.86: bytes=32 time=113ms TTL=50
Reply from 204.2.29.86: bytes=32 time=121ms TTL=50
Reply from 204.2.29.86: bytes=32 time=117ms TTL=50
Reply from 204.2.29.86: bytes=32 time=104ms TTL=50
Reply from 204.2.29.86: bytes=32 time=112ms TTL=50
Reply from 204.2.29.86: bytes=32 time=113ms TTL=50
Reply from 204.2.29.86: bytes=32 time=115ms TTL=50
Reply from 204.2.29.86: bytes=32 time=115ms TTL=50
Reply from 204.2.29.86: bytes=32 time=121ms TTL=50
Reply from 204.2.29.86: bytes=32 time=119ms TTL=50
Reply from 204.2.29.86: bytes=32 time=113ms TTL=50
Reply from 204.2.29.86: bytes=32 time=108ms TTL=50