Tracing route to (yoursite.com) [206.188.192.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 19 ms gig4-0.rochnymth-rtr03.nyroc.rr.com [24.93.0.157]
4 10 ms 11 ms 10 ms xe-9-1-0-0.rochnyei-rtr000.nyroc.rr.com [24.92.224.14]
5 26 ms 26 ms 25 ms 107.14.19.28
6 27 ms 27 ms 24 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
7 26 ms 27 ms 26 ms if-4-0-0.core1.CT8-Chicago.as6453.net [66.110.14.21]
8 80 ms 79 ms 99 ms 208.173.180.145
9 62 ms 62 ms 27 ms ber1-ge-8-2.chicagoequinix.savvis.net [204.70.194.238]
10 28 ms 28 ms 26 ms cr1-tengig-0-5-0-0.chicago.savvis.net [204.70.196.21]
11 91 ms 92 ms 155 ms cr1-bundle-pos2.Washington.savvis.net [204.70.200.90]
12 94 ms 95 ms 92 ms hr1-tengig-2-0-0.sterling2dc2.savvis.net [204.70.197.74]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * 64.58.94.114 reports: Destination net unreachable.
Trace complete.
Pinging 206.188.192.206 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.188.192.206:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Yet your load time in my browser (FF 4.0) was just over 4 secs.