said by mario44222 
:This is my tracert:
Tracing route to 82.165.228.91 over a maximum of 30 hops
1 5 ms 6 ms 5 ms 10.52.64.1
2 11 ms 8 ms 6 ms 24-168-128-30.nj.rr.com [24.168.128.30]
3 7 ms 6 ms 7 ms 24-168-128-57.nj.rr.com [24.168.128.57]
4 6 ms 7 ms 8 ms pos3-0-nycmnyc-rtr1.nyc.rr.com [24.29.101.245]
5 6 ms 7 ms 9 ms pos0-0-nycmnyrdc-rtr1.nyc.rr.com [24.29.97.17]
6 71 ms 69 ms 71 ms pos6-0-nycmnyrdc-rtr1.nyc.rr.com [24.29.97.1]
7 15 ms 12 ms 10 ms so-7-1.car1.Weehawken1.Level3.net [4.79.152.9]
8 18 ms 17 ms 19 ms ge-5-0-0.mp1.Weehawken1.Level3.net [4.68.125.129
]
9 18 ms 18 ms 16 ms ae-0-0.bbr2.NewYork1.Level3.net [64.159.1.42]
10 18 ms 7 ms 9 ms ge-7-0.ipcolo1.NewYork1.Level3.net [4.68.97.13]
11 8 ms 7 ms 7 ms 4.78.164.2
12 11 ms 10 ms 13 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.7
2]
13 13 ms 13 ms 13 ms 82.165.228.91
Trace complete.
Your trace looks to be the worst here, and yet you only have 1 router with a hop of 70ms. That is starting to get bothersome, and i'm sure if you were to send your local Tier 3 this tracert they could get with either the NOC or RDC guys and have them take a look. No reason for that high of a trace time for a in-network ping.
·
