Quote:
Originally Posted by Patrick Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\expc-1>tracert nloc.net
Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
1 9 ms 9 ms 9 ms adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.20
3.141.89]
2 10 ms 10 ms 10 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]
3 10 ms 10 ms 10 ms bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 11 ms 10 ms 11 ms 151.164.93.167
5 10 ms 11 ms 20 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 12 ms 11 ms 12 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 70 ms 70 ms 71 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.117]
8 71 ms 71 ms 70 ms ber2-tengigabitethernet-3-1.chicagoequinix.savvi
s.net [204.70.195.118]
9 72 ms 72 ms 71 ms 208.173.176.218
10 70 ms 71 ms 70 ms ip60.216-86-149.static.steadfast.net [216.86.149
.60]
11 74 ms 74 ms 74 ms web.nloc.net [208.100.8.12]
Trace complete.
Looks somewhat better? |
Our Host stated that anything under 80 ms coming out of California was considered good
Must be all those .coms sucking up all the bandwidth