said by hamburglar:I always see it starting on the second hop (10.160.64.1), so I'm not even leaving the local RR network and getting latency. During the day, it's almost solid less than 50ms.
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.50.2
2 592 ms 83 ms 69 ms 10.160.64.1
3 98 ms 80 ms 21 ms ae1-1112.cr02.clmcohib.midohio.rr.com [65.25.145.73]
4 319 ms * 353 ms be21.clevohek-ccr01.mwrtn.rr.com [65.189.141.106]
5 339 ms 485 ms 342 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
6 50 ms 45 ms 294 ms 107.14.19.135
7 292 ms 268 ms 204 ms 66.109.9.66
8 124 ms 123 ms 60 ms 209.85.252.46
9 74 ms 261 ms 158 ms 72.14.236.148
10 48 ms 60 ms 141 ms 72.14.238.70
11 147 ms 50 ms 69 ms 216.239.49.149
12 72 ms 36 ms 92 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
If you show that trace to a TW employee, they'll tell you there is nothing wrong with it since the destination is @92ms, ask hob. They will tell you to ignore the other hops and just look at the last hop. Of course, your problem is congested gateway(second hop) and you will need patience and time to convince TW that you have a congested node. Good luck!