Response time very slow?

[Bodofish]

So ever since the network outage a few weeks ago, the site has been dog slooooooooooow. Pages take forever to load, I first thought it was my habit of a million windows open but even when I close everything else, it's slow. Oh yeah, I have a 20 meg connection and it's just fine. I don't know if it will help but I'm inclined to look at the colo. Here's a couple of hey yous that may help. I've bolded the offending router or whatever device it is. As a Hummmmmm this is the same device I was unable to get past during the last "site down time".

C:\Users\Matt>tracert http://www.washingtonlakes.com" onclick="window.open(this.href);return false;

Tracing route to http://www.washingtonlakes.com" onclick="window.open(this.href);return false; [208.179.13.29]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 73.104.196.1
3 9 ms 9 ms 9 ms te-0-0-0-3-ur06.bellevue.wa.seattle.comcast.net
[68.86.113.9]
4 10 ms 10 ms 11 ms ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.117]
5 22 ms 14 ms 21 ms he-1-8-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.229]
6 27 ms 29 ms 27 ms 4.59.234.25
7 32 ms 28 ms 27 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

8 28 ms 28 ms 31 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
9 32 ms 29 ms 38 ms ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 35 ms 36 ms 35 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
11 37 ms 37 ms 47 ms ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.2
2]
12 35 ms 35 ms 35 ms ae-2-70.edge3.LosAngeles1.Level3.net [4.69.144.7
3]
13 38 ms 38 ms 39 ms TIERZERO-IN.edge3.LosAngeles1.Level3.net [4.59.6
0.166]
14 40 ms 39 ms 94 ms ge-0-0-0.cr02.lax1.tierzero.net [216.31.128.70]

15 40 ms 41 ms 42 ms colo2-1.lax1.ca.us.tierzero.net [216.31.153.31]

16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Matt>pathping http://www.washingtonlakes.com" onclick="window.open(this.href);return false;

Tracing route to http://www.washingtonlakes.com" onclick="window.open(this.href);return false; [208.179.13.29]
over a maximum of 30 hops:
0 Bodo.Surfin [192.168.1.101]
1 192.168.1.1
2 73.104.196.1
3 te-0-0-0-3-ur06.bellevue.wa.seattle.comcast.net [68.86.113.9]
4 ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.117]
5 te-1-2-0-1-cr01.seattle.wa.ibone.comcast.net [68.86.95.213]
6 4.59.234.25
7 ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]
8 ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
9 ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
10 ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201]
11 ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.22]
12 ae-2-70.edge3.LosAngeles1.Level3.net [4.69.144.73]
13 TIERZERO-IN.edge3.LosAngeles1.Level3.net [4.59.60.166]
14 ge-0-0-0.cr02.lax1.tierzero.net [216.31.128.70]
15 colo2-1.lax1.ca.us.tierzero.net [216.31.153.31]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bodo.Surfin [192.168.1.101]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 73.104.196.1
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% te-0-0-0-3-ur06.bellevue.wa.seattle.comcast.net [68.86.113.9]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.117]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% te-1-2-0-1-cr01.seattle.wa.ibone.comcast.net [68.86.95.213]
0/ 100 = 0% |
6 32ms 0/ 100 = 0% 0/ 100 = 0% 4.59.234.25
0/ 100 = 0% |
7 34ms 0/ 100 = 0% 0/ 100 = 0% ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
0/ 100 = 0% |
9 32ms 0/ 100 = 0% 0/ 100 = 0% ae-2-2.ebr2.SanJose5.Level3.net [4.69.148.141]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201]
0/ 100 = 0% |
11 42ms 0/ 100 = 0% 0/ 100 = 0% ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.22]
0/ 100 = 0% |
12 39ms 0/ 100 = 0% 0/ 100 = 0% ae-2-70.edge3.LosAngeles1.Level3.net [4.69.144.73]
0/ 100 = 0% |
13 40ms 0/ 100 = 0% 0/ 100 = 0% TIERZERO-IN.edge3.LosAngeles1.Level3.net [4.59.60.166]
0/ 100 = 0% |
14 40ms 0/ 100 = 0% 0/ 100 = 0% ge-0-0-0.cr02.lax1.tierzero.net [216.31.128.70]
100/ 100 =100% |
15 --- 100/ 100 =100% 0/ 100 = 0% colo2-1.lax1.ca.us.tierzero.net [216.31.153.31]

[Bodofish]

I guess I should explain;

In the pathping, 14 40ms 0/ 100 = 0% 0/ 100 = 0% ge-0-0-0.cr02.lax1.tierzero.net [216.31.128.70]
100/ 100 =100% | the 100/100 is showing 100% packet loss, although it's sending on requests for the next hop it's causing all the devices before it to think it's dead so they keep sending re-requests because of no response, we eventually get enough replys from the upstream devices to put a the web page together but it really slows the show. Maybe they could look at "ge-0-0-0.cr02.lax1.tierzero.net" ? fail it over, re-start it, replace a card, check the programming...... so many things.

[Dan Boone]

I don`t really get any of this, but yeah the site has been slow for me recently as well.

[Amx]

No problems here.

What's a 'colo'?

And all that stuff means nothing to me, but Aaron probably knows all that by heart. :-)

[Bodofish]

No problems here.

What's a 'colo'?

And all that stuff means nothing to me, but Aaron probably knows all that by heart. :-)

Colo or Co-location is where the web site is physically hosted/located. In this case, down in LA with a backup site in TX somewhere. I've had them bounce me to TX on occasion. I don't expect anyone but a few to know what all that stuff is but I'm sure Aaron does. That's one of the things that makes my brain feel like it on fire some nights. Ya just can't get there from here.

[oneshot]

maybe the server has been smoking some legal weed..

[Bodofish]

maybe the server has been smoking some legal weed..

Hehehehehe.... not in LA or TX....

[oneshot]

Texas? that could explain a lot...

and i'm not gonna ever knock the great state of Texas beings my home state and all.. but the servers and server peoples?
lets just say they ain't no a- of v- trash over yonder there, ya'll..

[Toni]

I haven't noticed any delay.

[Mike Carey]

I noticed some issues the other day. I thought it was just IE because Chrome seemed to work just fine.

Thanks for the specifics. I'll alert Aaron to this, although I bet he is aware.

[MotoBoat]

Nor here. My ping is dinging just fine! 15mb up load/ 5mb download. Have noticed no punch drunken sloooooowneeeeessssatttttalllllllllllllllllllllll.

[Amx]

But your o, s, e, t, & ! keys are sticking.

[MotoBoat]

But your o, s, e, t, & ! keys are sticking.

Yep, how do I fix thaaaaaaaaaaat?

[Amx]

But your o, s, e, t, & ! keys are sticking.

Yep, how do I fix thaaaaaaaaaaat?

I have no idea, but it's spreading to your a key.