|
FYI, real slow tonight about 6:30 pm pacific.
I don't know if this is any help, but...
Tracing route to [67.205.70.12]
1 2 ms <1 ms <1 ms [192.168.1.1]
2 9 ms 8 ms 8 ms 76-10-191-1.dsl.teksavvy.com [76.10.191.1]
3 9 ms 9 ms 9 ms 69.90.31.241
4 9 ms 9 ms 8 ms oc48.so-2-1-0.van-spenc-cor-1.peer1.net [216.187.89.249]
5 9 ms 8 ms 8 ms oc48.so-2-0-0.van-hc21e-cor-1.peer1.net [216.187.89.97]
6 69 ms 69 ms 69 ms oc48.so-3-0-2.tor-151f-cor-1.peer1.net [216.187.114.138]
7 77 ms 77 ms 76 ms 10ge-xe-1-0-0.mtl-bvh-cor-2.peer1.net [216.187.114.198]
8 77 ms 92 ms 77 ms g9-8.hd-core02.peer1.mtl.iweb.com [216.187.90.134]
9 * 193 ms 181 ms [67.205.70.12]
Trace complete.
Pinging [67.205.70.12] with 32 bytes of data:
Reply from 67.205.70.12: bytes=32 time=180ms TTL=56
Reply from 67.205.70.12: bytes=32 time=188ms TTL=56
Request timed out.
Request timed out.
Ping statistics for 67.205.70.12:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 188ms, Average = 184ms
*update* 7:30 pm Pacific
Tracing route to [67.205.70.12]
1 1 ms <1 ms <1 ms [192.168.1.1]
2 9 ms 12 ms 8 ms 76-10-191-1.dsl.teksavvy.com [76.10.191.1]
3 9 ms 9 ms 10 ms 69.90.31.241
4 15 ms 12 ms 9 ms oc48.so-2-1-0.van-spenc-cor-1.peer1.net [216.187.89.249]
5 9 ms 9 ms 9 ms oc48.so-2-0-0.van-hc21e-cor-1.peer1.net [216.187.89.97]
6 70 ms 70 ms 70 ms oc48.so-3-0-2.tor-151f-cor-1.peer1.net [216.187.114.138]
7 76 ms 76 ms 77 ms 10ge-xe-1-0-0.mtl-bvh-cor-2.peer1.net [216.187.114.198]
8 78 ms 83 ms 79 ms g9-8.hd-core02.peer1.mtl.iweb.com [216.187.90.134]
9 * * * Request timed out.
10 * * * Request timed out.
11 * 180 ms 187 ms [67.205.70.12]
Trace complete.
Last edited by kenmark; 10-04-2009 at 11:07 PM.
|