Is this forum and the NLOC website now slower?

[Patrick]

icrosoft Windows 2000 [Version 5.00.2195]
C) Copyright 1985-2000 Microsoft Corp.

:\Documents and Settings\expc-1>tracert nloc.net

racing route to nloc.net [208.100.8.12]
ver a maximum of 30 hops:

1 10 ms 9 ms 9 ms adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.20
.141.89]
2 9 ms 9 ms 9 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

3 10 ms 9 ms 9 ms bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 11 ms 10 ms 10 ms 151.164.93.167
5 10 ms 11 ms 10 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
64.248.214]
6 10 ms 11 ms 11 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 95 ms 76 ms 79 ms cr2-pos-0-7-3-3.chicago.savvis.net [208.172.3.81

8 72 ms 73 ms 73 ms ber2-tengigabitethernet-3-1.chicagoequinix.savvi
.net [204.70.195.118]
9 71 ms 70 ms 71 ms 208.173.176.218
10 85 ms 73 ms 73 ms ip60.216-86-149.static.steadfast.net [216.86.149
60]
11 69 ms 70 ms 70 ms web.nloc.net [208.100.8.12]

race complete.

:\Documents and Settings\expc-1>

[Patrick]

C:\Documents and Settings\expc-1>pathping nloc.net

Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
0 expc-1 [192.168.1.105]
1 adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.203.141.89]
2 dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]
3 bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 151.164.93.167
5 bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.164.248.214]
6 cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 cr2-pos-0-7-3-3.chicago.savvis.net [208.172.3.81]
8 ber2-tengigabitethernet-3-1.chicagoequinix.savvis.net [204.70.195.118]
9 208.173.176.218
10 ip60.216-86-149.static.steadfast.net [216.86.149.60]
11 web.nloc.net [208.100.8.12]

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 expc-1 [192.168.1.105]
0/ 100 = 0% |
1 10ms 0/ 100 = 0% 0/ 100 = 0% adsl-63-203-141-89.dsl.lsan03.pacb
ell.net [63.203.141.89]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% dist4-vlan50.irvnca.sbcglobal.net
[67.114.50.2]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% bb2-g9-0.irvnca.sbcglobal.net [151
.164.92.196]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 151.164.93.167
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% bpr2-ge-2-1-0.LosAngelesEquinix.sa
vvis.net [151.164.248.214]
0/ 100 = 0% |
6 180ms 2/ 100 = 2% 2/ 100 = 2% cr2-pos-0-0-3-0.lay.savvis.net [20
4.70.203.50]
0/ 100 = 0% |
7 186ms 6/ 100 = 6% 6/ 100 = 6% cr2-pos-0-7-3-3.chicago.savvis.net
[208.172.3.81]
0/ 100 = 0% |
8 76ms 0/ 100 = 0% 0/ 100 = 0% ber2-tengigabitethernet-3-1.chicag
oequinix.savvis.net [204.70.195.118]
0/ 100 = 0% |
9 80ms 0/ 100 = 0% 0/ 100 = 0% 208.173.176.218
0/ 100 = 0% |
10 80ms 0/ 100 = 0% 0/ 100 = 0% ip60.216-86-149.static.steadfast.n
et [216.86.149.60]
0/ 100 = 0% |
11 70ms 0/ 100 = 0% 0/ 100 = 0% web.nloc.net [208.100.8.12]

Trace complete.

C:\Documents and Settings\expc-1>

[Patrick]

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\expc-1>pathping nloc.net

Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
0 expc-1 [192.168.1.105]
1 adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.203.141.89]
2 dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]
3 bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 151.164.93.167
5 bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.164.248.214]
6 .cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 cr2-pos-0-7-3-3.chicago.savvis.net [208.172.3.81]
8 ber2-tengigabitethernet-3-1.chicagoequinix.savvis.net [204.70.195.118]
9 208.173.176.218
10 ip60.216-86-149.static.steadfast.net [216.86.149.60]
11 web.nloc.net [208.100.8.12]

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 expc-1 [192.168.1.105]
0/ 100 = 0% |
1 9ms 0/ 100 = 0% 0/ 100 = 0% adsl-63-203-141-89.dsl.lsan03.pacb
ell.net [63.203.141.89]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% dist4-vlan50.irvnca.sbcglobal.net
[67.114.50.2]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% bb2-g9-0.irvnca.sbcglobal.net [151
.164.92.196]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 151.164.93.167
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% bpr2-ge-2-1-0.LosAngelesEquinix.sa
vvis.net [151.164.248.214]
0/ 100 = 0% |
6 100ms 5/ 100 = 5% 5/ 100 = 5% cr2-pos-0-0-3-0.lay.savvis.net [20
4.70.203.50]
0/ 100 = 0% |
7 188ms 3/ 100 = 3% 3/ 100 = 3% cr2-pos-0-7-3-3.chicago.savvis.net
[208.172.3.81]
0/ 100 = 0% |
8 76ms 0/ 100 = 0% 0/ 100 = 0% ber2-tengigabitethernet-3-1.chicag
oequinix.savvis.net [204.70.195.118]
0/ 100 = 0% |
9 81ms 0/ 100 = 0% 0/ 100 = 0% 208.173.176.218
0/ 100 = 0% |
10 80ms 0/ 100 = 0% 0/ 100 = 0% ip60.216-86-149.static.steadfast.n
et [216.86.149.60]
0/ 100 = 0% |
11 69ms 0/ 100 = 0% 0/ 100 = 0% web.nloc.net [208.100.8.12]

Trace complete.

[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 9 ms 9 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 10 ms 10 ms 11 ms 151.164.93.167
5 10 ms 10 ms 11 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 11 ms 11 ms 11 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 69 ms 69 ms 78 ms cr2-pos-0-7-3-3.chicago.savvis.net [208.172.3.81
]
8 75 ms 75 ms 73 ms ber2-tengigabitethernet-3-1.chicagoequinix.savvi
s.net [204.70.195.118]
9 71 ms 70 ms 71 ms 208.173.176.218
10 73 ms 72 ms 75 ms ip60.216-86-149.static.steadfast.net [216.86.149
.60]
11 69 ms 70 ms 70 ms web.nloc.net [208.100.8.12]

Trace complete.

[Silver_2000]

can you do a ping -t and let it run for about 15-20 pings ?

ping nloc.net -t

Make sure its "slow" while you are running the pings

Also describe your experience

you get timeouts ? Have to refresh ? see red x's ? or just have to wait a long time.

THANKS A TON for the info

[Patrick]

Originally Posted by Silver_2000

can you do a ping -t and let it run for about 15-20 pings ?

ping nloc.net -t

Make sure its "slow" while you are running the pings

Also describe your experience

you get timeouts ? Have to refresh ? see red x's ? or just have to wait a long time.

THANKS A TON for the info

Sure, glad to. Please tell me how to do this for 15-20 pings...
As to your comment about doing it when it's slow; Well, it's slow all the time, but not every page I might click on. Seems random. Some will load fast, some slow, and doing a reload can be different, usually faster but not always.

Describe my experience: Well, never get an X and I don't think any time outs, Sometimes it say's "Done" and it's a white page, so I hit refresh and it usually reloads fast. Most of the time if it is a slow loading page, I just have to wait a long time (about 4/5 seconds). I'd say 1/2 the pages load slow.
Just so you know, I use Gen 1 Lightnings - The National Lightning Owners Club, Inc. as my homepage.

One more thing; I have the same problem either with my work computer, on windows 2000 pro and ATT DSL (the higher speed option) or my home laptop, windows vista business Time Warner cable, Firefox browser on both.

Let me know if you need any additional info.. And don't forget, Please tell me how to do this for 15-20 pings...right now it finishes and this is what I send you.

[Silver_2000]

ping -t will run till you stop it

so just let it run till you see 15- 20 replies and hit control c to stop it

[Patrick]

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\expc-1>ping nloc -t
Unknown host nloc.

C:\Documents and Settings\expc-1>ping nloc.net -t

Pinging nloc.net [208.100.8.12] with 32 bytes of data:

Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=90ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=71ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58
Reply from 208.100.8.12: bytes=32 time=68ms TTL=58
Reply from 208.100.8.12: bytes=32 time=69ms TTL=58

Ping statistics for 208.100.8.12:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 90ms, Average = 69ms
Control-C

[Patrick]

Something seems to have changed in that since we talked Doug (on Monday, it's now Tuesday), it seems OK now, both at work and at home. I'll monitor it a couple of days, and let you know.

[Silver_2000]

Originally Posted by Patrick

Something seems to have changed in that since we talked Doug (on Monday, it's now Tuesday), it seems OK now, both at work and at home. I'll monitor it a couple of days, and let you know.

great !! Keep me posted

[Patrick]

Thanks for your help Doug. Seems better now.

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 49 ms adsl-63-203-141-89.dsl.lsan03.pacbell.net [63.20
3.141.89]
2 14 ms 10 ms 19 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

3 10 ms 9 ms 9 ms bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
4 10 ms 10 ms 10 ms 151.164.93.167
5 10 ms 11 ms 10 ms bpr2-ge-2-1-0.LosAngelesEquinix.savvis.net [151.
164.248.214]
6 11 ms 11 ms 11 ms cr2-pos-0-0-3-0.lay.savvis.net [204.70.203.50]
7 72 ms 73 ms 73 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.117]
8 72 ms 72 ms 72 ms ber2-tengigabitethernet-3-1.chicagoequinix.savvi
s.net [204.70.195.118]
9 71 ms 70 ms 71 ms 208.173.176.218
10 71 ms 71 ms 70 ms web.nloc.net [208.100.8.12]

[Silver_2000]

It would be helpful if some of the other folks who replied here would post if thier experience has improved - we think it should have - AND post another tracert especially if you posted one before - I want to see the difference -

[SLVRLTNG]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.



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>


Doug here's one from my connection just run

[Silver_2000]

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

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.

[SLVRLTNG]

same place, same chair even