Is this forum and the NLOC website now slower?

[DJ2003]

comcast cable internet, chicago, slow here also

[ASAP]

Pretty quick this morning! Something has deff changed here..

[Patrick]

Originally Posted by Patrick

Might be better. Will let you know tomorrow.

I'm w/ATT (pacbell).

Seems to be OK now, but will keep an eye out for a couple more days. Thanks for working out the solution.

[Patrick]

Originally Posted by Patrick

Trying to return to the forum page:

Visitor 63.203.141.90
Using Browser

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
The page (none) you requested doesnt exist
Please try again The National Lightning Owners Club
Thanks National Lightning Owners CLub

You said"If you are using a shortcut to the forum it may be broken because of that change". Yup, reset my home page (I use NLOC forum as my Firefox browser home page) and it's fine now.

[Patrick]

Originally Posted by Patrick

Seems to be OK now, but will keep an eye out for a couple more days. Thanks for working out the solution.

Well, it's better, but not as good as it was. Probably livable, but it definitely is slower to load pages now. Some worse than others.

[99WhiteBeast]

Slightly slower at times but hardly noticeable

Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms 10.12.64.1
2 9 ms 9 ms * 70.125.218.190
3 9 ms 17 ms 11 ms gig4-4.dllatxgpv-t-rtr2.tx.rr.com [70.125.217.93
]
4 8 ms 11 ms * gig3-4.dllatxgpv-t-rtr2.tx.rr.com [70.125.217.94
]
5 9 ms 9 ms * gig4-4.dllatxcrl-t-rtr2.tx.rr.com [70.125.217.97
]
6 10 ms 10 ms * gig7-2.dllatxcrl-t-rtr2.tx.rr.com [70.125.217.98
]
7 11 ms 10 ms 11 ms gig4-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.10
1]
8 15 ms 15 ms 16 ms gig0-1-0.hstntxl3-rtr1.texas.rr.com [72.179.205.
74]
9 15 ms 15 ms 15 ms te-7-1.car1.Houston1.Level3.net [4.79.88.105]
10 15 ms 15 ms 15 ms ae-11-11.car2.Houston1.Level3.net [4.69.132.234]

11 51 ms 53 ms 53 ms ae-5-5.ebr1.Atlanta2.Level3.net [4.69.132.238]
12 42 ms 53 ms 53 ms ae-62-60.ebr2.Atlanta2.Level3.net [4.69.138.3]
13 60 ms 67 ms 72 ms ae-3.ebr2.Chicago1.Level3.net [4.69.132.73]
14 62 ms 60 ms 64 ms ae-24-54.car4.Chicago1.Level3.net [4.68.101.104]

15 62 ms 61 ms 61 ms WBS-CONNECT.car4.Chicago1.Level3.net [4.79.208.1
54]
16 60 ms 61 ms 62 ms web.nloc.net [208.100.8.12]

Trace complete.

[Patrick]

Originally Posted by Patrick

Well, it's better, but not as good as it was. Probably livable, but it definitely is slower to load pages now. Some worse than others.

Sorry, but the "upgrade" is not near as fast as it was before. Some pages take way long to transfer. Not complaining, just what it is.

[Silver_2000]

the server is MUCH faster than it was

If your experience has changed its, due to the connection from you to the server

if you run a tracert to the server and post the results here

[Patrick]

Originally Posted by Silver_2000

the server is MUCH faster than it was

If your experience has changed its, due to the connection from you to the server

if you run a tracert to the server and post the results here

OK, did it but cannot figure out how to copy and paste the results.
I'm on Vista Business, Firefox and Time Werner. And NLOC forum is my home page.

OK, here it is;
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.



C:\Windows\system32>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

C:\Windows\system32>tracert nloc.net

Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms cpe-76-87-219-50.socal.res.rr.com [76.87.219.50]

2 9 ms 9 ms 9 ms 10.33.64.1
3 9 ms 11 ms 11 ms gig2-3.wmnsca2-rtr2.socal.rr.com [24.30.162.177]

4 9 ms 10 ms 10 ms SRP1-1.GDGVCA1-GSR2.socal.rr.com [24.30.162.66]

5 10 ms 11 ms 8 ms tge4-1-0.tustca1-rtr1.socal.rr.com [24.30.162.23
5]
6 14 ms 10 ms 11 ms te-4-1.car1.Tustin1.Level3.net [4.71.104.157]
7 11 ms 12 ms 12 ms ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
8 12 ms 11 ms 13 ms ae-0-11.bar2.Tustin1.Level3.net [4.69.136.198]
9 45 ms 52 ms 54 ms ae-10-10.ebr1.Dallas1.Level3.net [4.69.136.206]

10 49 ms * 47 ms ae-91-91.csw4.Dallas1.Level3.net [4.69.136.134]

11 43 ms 54 ms 52 ms ae-92-92.ebr2.Dallas1.Level3.net [4.69.136.149]

12 60 ms 53 ms 53 ms ae-2.ebr1.Denver1.Level3.net [4.69.132.105]
13 76 ms 54 ms 52 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
14 89 ms 89 ms 76 ms ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]
15 85 ms 75 ms 84 ms ae-78.ebr2.Chicago1.Level3.net [4.69.134.61]
16 78 ms 75 ms 75 ms ae-24-56.car4.Chicago1.Level3.net [4.68.101.168]

17 77 ms 77 ms 77 ms WBS-CONNECT.car4.Chicago1.Level3.net [4.79.208.1
54]
18 78 ms 76 ms 77 ms web.nloc.net [208.100.8.12]

Trace complete.

[Silver_2000]

you are the second cox user who has reported slowness tonight
He was on NHTOC and was getting tracert results of 200-300 ms

Its the connection from cox to level3 that was the issue with him
Another so cal user that fro some reason has traffic going from socal to dallas to Denver and then back to chicago

Its also a bunch of hops ...

[bgstew6]

Yup I be one of them LOL

COX FTL!

[Patrick]

Originally Posted by Silver_2000

you are the second cox user who has reported slowness tonight
He was on NHTOC and was getting tracert results of 200-300 ms

Its the connection from cox to level3 that was the issue with him
Another so cal user that fro some reason has traffic going from socal to dallas to Denver and then back to chicago

Its also a bunch of hops ...

Oops, I'm on Time Warner, not Cox. Appears to be the same routing, dallas, denver, chicago.. Is this the cause of my slowness in loading pages? Any corrections possible?

[Silver_2000]

Originally Posted by Patrick

Oops, I'm on Time Warner, not Cox. Appears to be the same routing, dallas, denver, chicago.. Is this the cause of my slowness in loading pages? Any corrections possible?

The best thing to do is run a tracert to nloc.net and post it here and then share the results with your ISP
With enough tracerts I can share them with the datacenter that hosts the server BUT one user with slow tracert ONCE isnt enough to convince them of anything

for contrast here is the tracrt from my PC in dallas

C:\WINDOWS\system32>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 DD-WRT [192.168.1.1]
2 2 ms 1 ms 1 ms 10.33.34.6
3 1 ms 1 ms 1 ms P0-3.LCR-03.DLLSTX.verizon-gni.net [130.81.48.12
0]
4 2 ms 2 ms 2 ms 130.81.29.180
5 3 ms 3 ms 3 ms 0.so-1-3-0.XT3.DFW9.ALTER.NET [152.63.0.25]
6 28 ms 28 ms 28 ms 0.so-6-0-0.XL1.CHI13.ALTER.NET [152.63.70.101]
7 27 ms 27 ms 27 ms POS6-0.GW1.CHI13.ALTER.NET [152.63.69.177]
8 29 ms 28 ms 28 ms wbsconnect-gw.customer.alter.net [65.207.236.126
]
9 28 ms 28 ms 28 ms web.nloc.net [208.100.8.12]

The first 2 hops are my router and my FIOS box on the side of the house - so they really dont count - After that there are 7 hops to the server and all the hops are under 30ms - That means that my connection to the server is FLYING and the server is flying.

I know that some of you are seeing slower response but trust me when I tell you its NOT the server - its the internet

post enough tracerts here and contact your ISPs and we can get this corrected - I hope

[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?

[Silver_2000]

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 ...