This isn't an Optimum issue, but Optimum can work around the issue by providing an alternate route out of their network to avoid the bad nodes.

The bad node seems to be somewhere between ntt.net (these people) and the NA Datacenter.

My traceroute from once it leaves Optimum's network:

Code:
 7  nyk-b7-link.ip.twelve99.net (62.115.153.104)  6.726 ms  6.711 ms  6.898 ms
 8  nyk-bb2-link.ip.twelve99.net (62.115.143.12)  8.379 ms  7.429 ms nyk-bb1-link.ip.twelve99.net (62.115.143.10)  8.059 ms
 9  nyk-b1-link.ip.twelve99.net (62.115.135.133)  8.132 ms  39.199 ms  8.014 ms
10  * ae-17.a02.nycmny17.us.bb.gin.ntt.net (129.250.8.229)  7.635 ms *
11  * * *
12  * * *
And it fails from then on, always after getting to a ntt.net node. From the looks of one thread last month (here), it was ntt.net then, too.