My browser has been stuttering badly for the last few days and I believe it something to do with the following tracert results that I've been retrieving consistently - bad hop on #4 - I'm in MA.
Tracing route to www.seekingalpha.com [208.93.143.60]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 6 ms 8 ms L100.BSTNMA-VFTTP-72.verizon-gni.net [96.237.177.1]
3 8 ms 8 ms 6 ms G11-0-1-772.BSTNMA-LCR-07.verizon-gni.net [130.81.96.114]
4 * * * Request timed out.
5 18 ms 18 ms 16 ms so-9-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.70]
6 18 ms 16 ms 17 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
7 18 ms 17 ms 18 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
8 18 ms 17 ms 51 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
9 17 ms 18 ms 16 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
10 30 ms 17 ms 16 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
11 18 ms 24 ms 29 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
12 19 ms 16 ms 17 ms ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
13 18 ms 17 ms 18 ms 4.26.35.210
14 17 ms 18 ms 23 ms LB140.NYNY.COTENDO.net [208.93.143.60]
Trace complete.
Can anybody confirm/deny/help?
People missread tracert. Its really not meant to show quality of the line but to show the route your message is taking.
There are lots of reasons for having a hop timeout. It, by itself, is not important. Options on the tracert command (-w) can change the timeout value. Of course reported large delays along along the route mean a problem.
Start a new topic or ask questions in the open forum.
