Quote:
Originally Posted by SLVRLTNG  Doug here's one from my connection just run |
So is it better or worse than 2 weeks ago /
Is this run from the same location as the one you posted previously ?
The route has completely changed
Quote:
C:\Documents and Settings\JR>tracert nloc.net
Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
1 * * * Request timed out.
2 32 ms 31 ms 31 ms L100.DSL-06.STTLWA.verizon-gni.net [71.112.32.1]
3 32 ms 31 ms 31 ms P1-1.LCR-01.STTLWA.verizon-gni.net [130.81.34.11
6]
4 53 ms 52 ms 52 ms 130.81.17.205
5 53 ms 53 ms 52 ms verizon.tge2-1.ar2.sjc1.us.nlayer.net [69.22.153
.61]
6 51 ms 59 ms 51 ms xe-2-3-0.cr1.sjc1.us.nlayer.net [69.22.143.117]
7 103 ms 103 ms 102 ms xe-2-1-0.cr1.ord1.us.nlayer.net [69.22.142.57]
8 104 ms 103 ms 103 ms tge6-3.ar1.ord1.us.nlayer.net [69.31.111.134]
9 103 ms 102 ms 103 ms 69.31.110.26
10 205 ms 139 ms 100 ms ip60.216-86-149.static.steadfast.net [216.86.149
.60]
11 99 ms 100 ms 100 ms web.nloc.net [208.100.8.12]
Trace complete.
C:\Documents and Settings\JR>
C:\Documents and Settings\JR>tracert nloc.net
Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dslmodem.domain [192.168.1.1]
2 32 ms 31 ms 31 ms L100.DSL-06.STTLWA.verizon-gni.net [x.x.32.1]
3 32 ms 31 ms 32 ms P1-1.LCR-01.STTLWA.verizon-gni.net [130.81.34.11
6]
4 34 ms 32 ms 34 ms so-6-0-0-0.PEER-RTR1.SEA81.verizon-gni.net [130.
81.17.137]
5 32 ms 34 ms 33 ms 0.so-7-0-0.XT2.SEA1.ALTER.NET [152.63.104.49]
6 102 ms 100 ms 100 ms 0.so-5-0-0.XL2.CHI13.ALTER.NET [152.63.64.14]
7 99 ms 100 ms 101 ms POS7-0.GW1.CHI13.ALTER.NET [152.63.69.181]
8 180 ms 129 ms 102 ms wbsconnect-gw.customer.alter.net [65.207.236.126
]
9 * * * Request timed out.
Trace complete.
|