Quote:
Originally Posted by Patrick  This is on another computer and location using windows 2000 Pro, ATT, DSL.
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 10 ms 9 ms 9 ms adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.20
3.141.89]
2 173 ms 40 ms 10 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]
3 9 ms 9 ms 9 ms bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 11 ms 18 ms 13 ms 151.164.93.167
5 11 ms 10 ms 11 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 2870 ms * 11 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 71 ms 73 ms 71 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.117]
8 73 ms 73 ms 73 ms ber2-tengigabitethernet-3-1.chicagoequinix.savvi
s.net [204.70.195.118]
9 70 ms 69 ms 70 ms 208.173.176.218
10 166 ms 158 ms 113 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.
Not good either. Any suggestions? |
the first one is MUCH better than the second but both have issues.
Only thing I can impact is the return routing - The server has multiple redundant inbound connections and outbound connections - in your case the LA Saavis router is showing an almost 3 second delay. Those issues usually repair themselves.
There are just too many internet users in California ...