We’re trying to figure out wether this is an isolated or wider incident, looking like one of our customer’s flows is fragging between NTT and Comcast.
5 ae-0.a02.snjsca04.us.bb.gin.ntt.net (129.250.2.3) 5.571 ms 13.026 ms 9.514 ms
6 ae-0.comcast.snjsca04.us.bb.gin.ntt.net (129.250.66.34) 119.688 ms 117.368 ms 111.902 ms
7 be-12578-cr01.9greatoaks.ca.ibone.comcast.net (68.86.88.17) 118.845 ms 117.035 ms 114.762 ms
8 * be-7922-ar01.hayward.ca.sfba.comcast.net (68.86.94.154) 120.025 ms 114.310 ms
9 * be-397-rar01.fairfield.ca.sfba.comcast.net (96.108.99.10) 119.178 ms *
10 162.151.79.66 (162.151.79.66) 123.215 ms 121.184 ms 124.125 ms
If anyone from either entity would like to contact me off list for troubleshooting please feel free.
Hi all,
We are following up off-list!
This may be a good moment to mention that the excellent people at the NTT NOC are always available at noc@ntt.net, or the phone numbers listed in PeeringDB. 
Kind regards,
Job
This may be a good moment to mention that the excellent people at the
NTT NOC are always available at noc@ntt.net, or the phone numbers
listed in PeeringDB. 
just to say that they are awesome
so, uh, you don't recommend them to your competitors then?
Nick
just to say that they are awesome
so, uh, you don't recommend them to your competitors then?
no way. my competitors should buy from comcast, he, ...
I’ll Just pop in here to echo Randy’s comments - we have great experiences with NTT across the board and they did reach out and resolve the issue.
-Ben