Code:
Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  RT-AC68U-5570 [192.168.1.1]
  2     9 ms     8 ms     8 ms  96.120.28.53
  3     9 ms     8 ms     9 ms  te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
  4     8 ms     9 ms     9 ms  68.85.183.142
  5    14 ms    11 ms    10 ms  be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
  6    20 ms    12 ms    12 ms  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
  7    12 ms    13 ms    14 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  8    10 ms     9 ms    11 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  9   186 ms   186 ms   186 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 10    12 ms    20 ms    10 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 11   186 ms     *      178 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 12   189 ms   188 ms   189 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 13   188 ms   186 ms   188 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 14   190 ms   187 ms   186 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 15   180 ms   184 ms   180 ms  204.2.229.234
 16   174 ms   187 ms   187 ms  204.2.229.97

Trace complete.
So we keep posting this stuff, and it all looks roughly the same. You've been "investigating" this problem for literal months at this point. Is there an end in sight? Will NTT do anything to alleviate the problem? Because it's NTT. You understand that right? Months of investigation must have yielded the same (if not superior) results as a couple dozen forum posters posting their connection data for you. It's prime time, every night, without fail. Ping times in the 200-400 range and spiking as high as 900. I'm not across an ocean or on the damn moon or something. I'm in a major metropolitan area with modern infrastructure and my connection is going to another place that would be described with the same terms. I don't encounter a connection problem until I reach NTT's infrastructure which is, quite obviously, not up to the task of handling SE's traffic.