[BlackArcher101]

Here is what I get.

Tracing route to 64.37.64.51 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.10.1
2 4 ms 3 ms 3 ms core2-vlan661.rdr.wiband.net [64.56.134.1]
3 10 ms 9 ms 10 ms cgy-rdrix.cgy.wiband.net [72.13.161.1]
4 11 ms 10 ms 10 ms ge-02-edge1.cgy.wiband.net [72.13.190.25]
5 11 ms 10 ms 10 ms h64-42-254-90.gtcust.grouptelecom.net [64.42.254
.90]
6 11 ms 10 ms 12 ms GE0-2.WANA-CALGAB.IP.GROUPTELECOM.NET [66.59.190
.149]
7 27 ms 28 ms 26 ms POS9-0.WANB-VANCBC.IP.GROUPTELECOM.NET [66.59.19
0.198]
8 27 ms 26 ms 26 ms POS2-0.PEERA-STTLWA.IP.GROUPTELECOM.NET [66.59.1
90.98]
9 27 ms 26 ms 28 ms bpr4-so-5-0-0.SeattleSwitchDesign.savvis.net [20
8.173.50.73]
10 27 ms 27 ms 26 ms 208.173.49.2
11 27 ms 27 ms 27 ms sea-core-02.inet.qwest.net [205.171.26.85]
12 * * * Request timed out.
13 92 ms 91 ms 92 ms mo1-edge-03.inet.qwest.net [205.171.29.170]
14 92 ms 91 ms 92 ms qwestgige.cybercon.com [65.123.132.254]
15 91 ms 90 ms 91 ms 64.37.64.51

Trace complete.


Looks normal to me. They probably won't do anything for a 100ms ping. My ISP didn't start worrying until anything over 250ms. The packet loss you see is probably from a router that won't reply. There is a slow down at qwest, but nothing out of the ordinary really.