Site slowness

[DWS44]

The smilies always have taken forever to load.

Not for me, honestly. Rarely had a problem with them until these recent slowness issues. When the site is running normally, I can click the smiley button and they would fully populate in a second or less.

 

[DWS44]

Maybe when I use it the slowness is not going on at the time. Stoke of good luck.

Still happening for me right now. Interesting that you aren't seeing it.

 

[JSheridan]

The second to the last hop on the tracert is timing out again. Right before the sucuri cloudproxy. Hmm...

 

[charlesrshell]

Not for me, honestly. Rarely had a problem with them until these recent slowness issues. When the site is running normally, I can click the smiley button and they would fully populate in a second or less.

My last post the smiley face loaded quick as usual for me.

 

[JSheridan]

My last post the smiley face loaded quick as usual for me.

Maybe something to do with the different paths to Securi or Securi itself.

 

[navychop]

It's the Russians...

 

[JSheridan]

It's the Russians...

Nah, they're busy.

 

[JSheridan]

I think it just got fast again.

 

[JSheridan]

I think it just got fast again.

For a few minutes it was fast and now back to slow.

 

[lfp302]

Log-in without checking "STAY LOGGED IN" box is broken again.

 

[KE4EST]

Well I guess it is just me, but they always load slow for me, but I hardly ever expand them. I mostly just type in what I want.

 

[Scott Greczkowski]

I am working on our system again...

Noticed something ODD with our Homepage and am currently working on that. it might look empty or strange as I am working on it.

 

[DWS44]

it might look empty or strange as I am working on it.

I'll just go ahead and delete the post I just made asking about that.

 

[buist]

I am still seeing issues not with slowness but with accessing the website. I am able to access the website okay and a few minutes later I am not able to access it. Below is a tracert when it is not working (hopefully that helps). I see this happen on one of my work connections and at home (both are Comcast lines if it matters).

Tracing route to www.satelliteguys.us [192.124.249.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.11.1
2 36 ms 15 ms 21 ms 76.106.147.1
3 10 ms 2 ms 14 ms te-8-4-ur01.avondale.fl.jacksvil.comcast.net [68.86.170.129]
4 7 ms 12 ms 8 ms 10g-8-3-ar01.southsiderdc.fl.jacksvil.comcast.net [68.86.168.141]
5 15 ms 19 ms 16 ms be-33489-cr02.miami.fl.ibone.comcast.net [68.86.95.45]
6 78 ms 16 ms 16 ms hu-0-12-0-1-pe03.nota.fl.ibone.comcast.net [68.86.82.250]
7 15 ms 29 ms 51 ms 50.248.118.242
8 17 ms 21 ms 16 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80.41]
9 27 ms 28 ms 51 ms be2122.ccr41.atl01.atlas.cogentco.com [154.54.24.193]
10 58 ms 44 ms 50 ms be2112.ccr41.dca01.atlas.cogentco.com [154.54.7.157]
11 49 ms 45 ms 46 ms be3083.ccr41.iad02.atlas.cogentco.com [154.54.30.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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.

 

[buist]

For reference here is a tracert when it is working fine:

Tracing route to www.satelliteguys.us [192.124.249.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.11.1
2 392 ms 154 ms 129 ms 76.106.147.1
3 15 ms 19 ms 8 ms GE-3-1-sr01.macclenny.fl.jacksvil.comcast.net [68.86.170.129]
4 9 ms 13 ms 9 ms 10g-8-3-ur01.springfield.fl.jacksvil.comcast.net [68.86.168.77]
5 11 ms 12 ms 12 ms te-0-8-0-2-ar02.southside.fl.jacksvil.comcast.net [68.86.168.122]
6 17 ms 16 ms 16 ms be-33489-cr02.miami.fl.ibone.comcast.net [68.86.95.45]
7 17 ms 18 ms 34 ms hu-0-14-0-1-pe03.nota.fl.ibone.comcast.net [68.86.88.198]
8 18 ms 17 ms 22 ms 50.248.118.242
9 17 ms 17 ms 16 ms be2055.ccr22.mia01.atlas.cogentco.com [154.54.24.233]
10 67 ms 23 ms 25 ms be2123.ccr42.atl01.atlas.cogentco.com [154.54.24.197]
11 66 ms 46 ms 44 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
12 46 ms 45 ms 45 ms be3084.ccr41.iad02.atlas.cogentco.com [154.54.30.66]
13 * * * Request timed out.
14 39 ms 43 ms 39 ms cloudproxy10005.sucuri.net [192.124.249.5]

Trace complete.

Thanks,
Tim

 

[buist]

I had some issues again accessing the website (first time today was fine, but second time had the issues). We have 2 ISP's at my work, so I did a tracert from the other ISP (AT&T). Here are the results from them during the period I could not access the website:

1 12.35.152.33, time=0.167 ms
2 cr1.ormfl.ip.att.net (12.123.34.26), time=16.305 ms
3 cr1.ormfl.ip.att.net (12.123.34.26), time=15.029 ms
4 cr2.attga.ip.att.net (12.122.31.29), time=15.575 ms
5 12.122.117.121, time=14.666 ms
6 ae2-0.atl12.ip4.gtt.net (173.241.128.81), time=14.475 ms
7 et-7-3-0.cr4-was1.ip4.gtt.net (141.136.107.118), time=33.189 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *

Just thought it may be helpful..

Tim