If your still having problems. Go to the comand line and excute a trace route

tracert www.clublexus.com

Then post or send all the output to me. I will make sure that problem is fixed.

 

I've noticed things are slow lately too.

 

I have noticed a slowdown from time to time as well this weekend.

 

if you experience slow downs that make the site seem like your browsing on a 28.8 modem. Please do the following, go to start menu--> clik run ---> enter cmd--< click okay. At the commang prompt type in "tracert www.clbulexus.com" sent the resulting out put to me.

Also, please be more verbose.

 

(For those of you who don't know )
verbose

\Ver*bose"\, a. [L. verbosus, from verbum a word. See Verb.] Abounding in words; using or containing more words than are necessary; tedious by a multiplicity of words; prolix; wordy; as, a verbose speaker; a verbose argument.

If I'm right (I'm not into computers so much anymore), these are some loooonnng reply times!
And you guys might want to open the msdos window and do this instead of using the "run" way because on my comp, as soon as it finished tracing, the window closed.

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

C:\>tracert www.clublexus.com

Tracing route to www.clublexus.com [209.120.211.53]
over a maximum of 30 hops:

1 523 ms 532 ms 609 ms ip68-97-112-1.ok.ok.***.net [68.97.112.1]
2 * * * Request timed out.
3 540 ms 585 ms 574 ms mtc3dsrc02-gew0303.rd.ok.***.net [68.12.14.13]
4 579 ms 531 ms 494 ms mtc3bbrc02-pos0101.rd.ok.***.net [68.1.0.108]
5 555 ms 222 ms 548 ms mtc3bbrc01-pos0100.rd.ok.***.net [68.1.0.102]
6 512 ms 629 ms 451 ms dllsbbrc02-pos0103.rd.dl.***.net [68.1.0.107]
7 535 ms 615 ms 499 ms dllsbbrc01-pos0100.rd.dl.***.net [68.1.0.142]
8 576 ms 556 ms 544 ms dllstx2wcx1-pos5-2.wcg.net [64.200.232.213]
9 542 ms 409 ms 216 ms 64.200.110.161
10 321 ms 322 ms 433 ms dllstx9lce1-oc48.wcg.net [64.200.110.82]
11 444 ms 385 ms 448 ms dllstx9lce1-yipes.wcg.net [64.200.226.118]
12 599 ms 447 ms 410 ms 66.7.164.98
13 630 ms 520 ms 568 ms 209.120.209.22
14 * 511 ms 469 ms 209.120.211.53

Trace complete.

 

To give you an idea. Here is my tracert. It should be noted that way tracert works is it pings each router that you pass through. If you getting a ping of 500ms from your first router, that is pretty bad for a high speed internet connection.

1 2 ms 1 ms <1 ms 192.168.0.1
2 12 ms 12 ms 12 ms 67-64-151-254.d
3 14 ms 13 ms 13 ms dist1-vlan120.r

4 16 ms 14 ms 13 ms bb2-g8-0.rcsntx
5 14 ms 15 ms 15 ms bb1-p3-0.eqdltx
6 14 ms 14 ms 15 ms 151.164.89.226
7 15 ms 14 ms 15 ms dllstx9lce1-yip
8 16 ms 17 ms 16 ms 66.7.164.98
9 17 ms 19 ms 18 ms 209.120.209.22
10 * 18 ms 18 ms 209.120.211.53

 

To give you an idea. Here is my tracert. It should be noted that way tracert works is it pings each router that you pass through. If you getting a ping of 500ms from your first router, that is pretty bad for a high speed internet connection.
PLus, your ping times should be going up as you going through different routers. Your ping times are going up and down. can you do a tracert to yahoo.com or amazon or some other popular site so I have a frame of referenc
It should also be noted that being verbose is a very good thing in programing. Often people do not tell you enough information, or are unable to distinguish good information from useless information. I would rather have me someone tell me too much, than not enough.

 

Part of it seems to be my problem. I cold rebooted and things are faster now, although still seem to be slightly off. Now my tracert times were more like yours- ~10-30ms