The route that is give the problem is mostly inbound from what I can see as the trace route from the server back shows it stayed in the att network on the way back and didn't go to ntt. You need to contact NTT with your trace routes to show the problem is in their network. I will send the ticket on to the network folks to see if there is any contracts they have that can help get it cleared up.
Quote from: theplanetThe route that is give the problem is mostly inbound from what I can see as the trace route from the server back shows it stayed in the att network on the way back and didn't go to ntt. You need to contact NTT with your trace routes to show the problem is in their network. I will send the ticket on to the network folks to see if there is any contracts they have that can help get it cleared up.
The connect has increased by 90+ @ DM , Mutant and Railz.
2 27ms 0/ 100 = 0% 0/ 100 = 0% 154.11.89.129 3 --- 100/ 100 =100% 100/ 100 =100% toroonnlbr00.bb.telus.com [154.11.11.66] 4 135ms 5/ 100 = 5% 5/ 100 = 5% so-4-3-2.cr1.ord2.us.above.net [216.200.254.30]
http://img246.imageshack.us/my.php?image=netgraphei8.jpg