Occasional Slowness with Smugmug -over 6 months

orisky

First, let me say that I've been having this problem for over half a year. SM support has been gracious enough to work with me even though we're not sure where the problem lies. I'm hoping a greater network of ppl can help out.

Details:
-Occasional slowness connecting to my SM site (as well as others). (DISREGARD THIS LINE)
-This happens on my desktop which is hard wired
-On my laptop, which is wireless
-On other laptop, which is wireless
-Usually happens in the evenings, bandwidth is NOT an issue as I get 15/1.5 mbps tested
-Traceroutes don't complete
-Slowness only seems to happen when connecting to SM
-Sometimes it's not just slowness, it doesn't even load the page
-Posts on other forums referencing the pics sometimes don't load
-Linksys WRT54G router running DD-WRT. I've tried a direct connection as well bypassing the router.


Line tests from DSL reports:
<table style="border-style: solid;" align="center" border="0" cellpadding="2" cellspacing="0" width="80%"><tbody><tr><td nowrap="nowrap">medium bandwidth stream
<small>10secs of 128k/bit ping stream 512byte packets </small></td> <td align="middle" bgcolor="#ffff00" nowrap="nowrap">13% loss </td> <td align="middle" nowrap="nowrap">81.2ms </td> <td align="middle">83.4ms </td> <td align="middle">91.4ms </td> <td align="middle"><small>
fail
</small></td></tr></tbody></table>
<table width="100%"><tbody><tr> <td>4</td> <td align="right" bgcolor="#ff8080"><small>vl3492.mpd01.jfk05.atlas.cogentco.com</small></td> <td align="middle" bgcolor="#ff8080">10%</td> <td>54</td> <td>60</td> <td><small>0.96</small></td> <td><small>13.13</small></td> <td><small>205.44</small></td></tr> <tr> <td>5</td> <td #ffffff="" align="right"><small>cox.jfk05.atlas.cogentco.com</small></td> <td #ffffff="" align="middle">0%</td> <td>60</td> <td>60</td> <td><small>1.02</small></td> <td><small>2.70</small></td> <td><small>14.87</small></td></tr> <tr> <td>6</td> <td align="right" bgcolor="#ffff80"><small>rsmtdsrj02-ge710.0.rd.oc.cox.net</small></td> <td align="middle" bgcolor="#ffff80">7%</td> <td>56</td> <td>60</td> <td><small>74.19</small></td> <td><small>81.16</small></td> <td><small>189.71</small></td></tr></tbody></table>
I've asked COX to look into this, but when they "test the lines", they claim there's no thing wrong with it and I should contact the site owners since it only happens with SM.

I'll try to get some realtime tests run when the problem happens again.

Any network engineers lurking around?

TIA!

DrDavid

Sounds like your router is acting up. Replace it and see if that fixes the problem.

Oh, I'm a Microsoft Certified Systems Engineer. I'm the "Network Engineer" you were hoping would see it

ack.. didn't read... But, I still think if it's not the router, it's the modem.

David

DrDavid

Quick test.. See if you can ping between your computers.. Do it for a few minutes/hours. You shouldn't have ANY lost packets. Also, ping for a few minutes/hours the gateway address. Again, there shouldn't be anything wrong. If there is, check your hardware. I'd also try replacing wires to see if that's the problem.

David

orisky

DrDavid wrote:

Quick test.. See if you can ping between your computers.. Do it for a few minutes/hours. You shouldn't have ANY lost packets. Also, ping for a few minutes/hours the gateway address. Again, there shouldn't be anything wrong. If there is, check your hardware. I'd also try replacing wires to see if that's the problem.

David

I'll try the ping test...but if either of these things are an issue, wouldn't going to other sites cause problems?

DrDavid

orisky wrote:

I'll try the ping test...but if either of these things are an issue, wouldn't going to other sites cause problems?

You said you get other sites where it's slower too.

I'd first want to ensure that your equipment is good. That's my first thought, especially since it's Linksys hardware (which isn't known to last forever).

If the ping test is good, I suspect that you're seeing bandwidth issues on cable. Cable shares resources amongst your neighbors. In the evening, I suspect there's a LOT of filesharing and bittorrents going on; and that would drain your bandwidth.

David

DrDavid

So, how is the ping test going?

Do you know how to run a ping test in 'test' mode so that it will keep going until you stop it? (Given that you have DD-WRT, I assume you do.)

David

orisky

DrDavid wrote:

So, how is the ping test going?

Do you know how to run a ping test in 'test' mode so that it will keep going until you stop it? (Given that you have DD-WRT, I assume you do.)

David

Thanks for trying to help out. I do appreciate it. Both ping tests are fine. I've only been running it for about a min but here's the result to the gateway:

Ping statistics for 192.168.1.10:
Packets: Sent = 86, Received = 86, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Should I try bigger packets?

The thing about sites other than smugmug was sort of a typo. The other site thing is very occasionally...that could have been just a hiccup. The one I'm continually having problems with is SM.

DrDavid

Do me a favor, run a ping test to: www.smugmug.com

Again, you really shouldn't get any lost packets. If you do tonight, but in the morning you aren't, I'd suspect it's a bandwidth issue with the way cable works combined with the high usage on SM at night.

You also said traceroute's fail. Can you do one and post the results? I'd like to see what route your traverse.. Maybe there's a clue?

As for bigger packets... hm, probably wouldn't make a big deal, but, go ahead and try it with nice large packets. Give your router a run for its money

David

orisky

DrDavid wrote:

You said you get other sites where it's slower too.

I'd first want to ensure that your equipment is good. That's my first thought, especially since it's Linksys hardware (which isn't known to last forever).

If the ping test is good, I suspect that you're seeing bandwidth issues on cable. Cable shares resources amongst your neighbors. In the evening, I suspect there's a LOT of filesharing and bittorrents going on; and that would drain your bandwidth.

David

Dont think its bandwidth. I've run bw tests before and they're fine. I'll confirm if it happens again tonight. I can get to sm fine right now.

So let's say the issue happens again, what tests do you think I should run while the problem is happening?

-DSL line quality test
-Speednet test to San Jose (I think this was recommended by SM support)
-Ping test (should I increase the packet size)?
-Test from multiple machines
-Ask others to test at the same time

DrDavid

orisky wrote:

Dont think its bandwidth. I've run bw tests before and they're fine. I'll confirm if it happens again tonight. I can get to sm fine right now.

So let's say the issue happens again, what tests do you think I should run while the problem is happening?

-DSL line quality test
-Speednet test to San Jose (I think this was recommended by SM support)
-Ping test (should I increase the packet size)?
-Test from multiple machines
-Ask others to test at the same time

Definately do the speedtest to San Jose and post the results. Your line quality has already been shown to be poor (lost packets). But, doing it again shouldn't hurt. Try to increase the packet size shouldn't make too much of a difference. After 86+ packets we're not losing anything, and everything was in received in order.

I still keep thinking the router or modem is a problem. Probably because I just had a switch go bad on me and it caused a very similar problem... Can you try a new modem at all? or, do you have a friend who's on cable too (close by your home) that can try it too?

Cable does share bandwidth.. Even though you THINK you're getting 15/1.5, you really share that with your neighbors. If you have a really annoying kid nearby that does a ton of bittorrents, you WILL see a slowdown.

David

orisky

oooh oooh, problem is happening now!

DrDavid

orisky wrote:

oooh oooh, problem is happening now!

Only time you'll ever be excited that a problem is happening!

Well, post some results.. Ping your gateway again too..

I still have my bets on your modem.

orisky

Here you go:



C:\Documents and Settings\orion>tracert www.smugmug.com

Tracing route to hera.smugmug.com [63.81.134.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.10
2 8 ms 9 ms 10 ms ip68-4-100-1.oc.oc.cox.net [68.4.100.1]
3 10 ms 8 ms 7 ms ip68-4-13-137.oc.oc.cox.net [68.4.13.137]
4 * * * Request timed out.
5 9 ms 11 ms 9 ms langbbrj01-ae2.0.r2.la.cox.net [68.1.0.107]
6 16 ms 9 ms 14 ms ve6.fr4.lax.llnw.net [69.28.171.206]
7 23 ms 23 ms 24 ms tge1-3.fr3.sjc.llnw.net [69.28.171.118]
8 19 ms 33 ms 19 ms smugmug.ge3-1.fr3.sjc.llnw.net [208.111.152.78]

9 20 ms 18 ms 19 ms hera.smugmug.com [63.81.134.23]

Trace complete.

C:\Documents and Settings\orion>tracert www.smugmug.com

Tracing route to hera.smugmug.com [63.81.134.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.10
2 9 ms 9 ms 7 ms ip68-4-100-1.oc.oc.cox.net [68.4.100.1]
3 9 ms 8 ms 8 ms ip68-4-13-137.oc.oc.cox.net [68.4.13.137]
4 8 ms 6 ms 7 ms rsmtdsrj02-ge600.0.rd.oc.cox.net [68.4.14.213]
5 10 ms 11 ms 9 ms langbbrj01-ae2.0.r2.la.cox.net [68.1.0.107]
6 12 ms 8 ms 12 ms ve6.fr4.lax.llnw.net [69.28.171.206]
7 28 ms 22 ms 24 ms tge1-3.fr3.sjc.llnw.net [69.28.171.118]
8 20 ms 20 ms 30 ms smugmug.ge3-1.fr3.sjc.llnw.net [208.111.152.78]

9 20 ms 19 ms 19 ms hera.smugmug.com [63.81.134.23]

Trace complete.

C:\Documents and Settings\orion>tracert orisky.smugmug.com

Tracing route to orisky.smugmug.com [63.81.134.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.10
2 9 ms 8 ms 7 ms ip68-4-100-1.oc.oc.cox.net [68.4.100.1]
3 8 ms 7 ms 7 ms ip68-4-13-137.oc.oc.cox.net [68.4.13.137]
4 8 ms 7 ms 7 ms rsmtdsrj02-ge600.0.rd.oc.cox.net [68.4.14.213]
5 10 ms 9 ms 10 ms langbbrj01-ae2.0.r2.la.cox.net [68.1.0.107]
6 9 ms 16 ms 10 ms ve6.fr4.lax.llnw.net [69.28.171.206]
7 18 ms 19 ms 21 ms tge1-3.fr3.sjc.llnw.net [69.28.171.118]
8 21 ms 18 ms 33 ms smugmug.ge3-1.fr3.sjc.llnw.net [208.111.152.78]

9 18 ms 19 ms 17 ms hera.smugmug.com [63.81.134.23]

Trace complete.

C:\Documents and Settings\orion>tracert orisky.smugmug.com

Tracing route to orisky.smugmug.com [63.81.134.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.10
2 10 ms 9 ms 8 ms ip68-4-100-1.oc.oc.cox.net [68.4.100.1]
3 9 ms 8 ms 8 ms ip68-4-13-137.oc.oc.cox.net [68.4.13.137]
4 10 ms 10 ms 8 ms rsmtdsrj02-ge600.0.rd.oc.cox.net [68.4.14.213]
5 10 ms 10 ms 12 ms langbbrj01-ae2.0.r2.la.cox.net [68.1.0.107]
6 12 ms 11 ms 13 ms ve6.fr4.lax.llnw.net [69.28.171.206]
7 25 ms 24 ms 24 ms tge1-3.fr3.sjc.llnw.net [69.28.171.118]
8 26 ms 20 ms 19 ms smugmug.ge3-1.fr3.sjc.llnw.net [208.111.152.78]

9 23 ms 18 ms 20 ms hera.smugmug.com [63.81.134.23]

Trace complete.


Not a blip on my gateway ping nor a blip on pinging my printer's IP.

orisky

And when I said tracerts don't complete, I'm talking about the one from
http://www.smugmug.com/homepage/traceroute.mg


1 10.27.3.2 (10.27.3.2) 0.509 ms 0.848 ms 0.886 ms
2 r2.sv1.smugmug.net (63.81.134.2) 9.790 ms 11.596 ms 1.033 ms
3 ge3-1.fr3.sjc.llnw.net (208.111.152.77) 1.770 ms 1.937 ms 0.970 ms
4 tge1-1.fr4.lax.llnw.net (69.28.171.117) 16.588 ms 17.368 ms 10.184 ms
5 ve6.fr3.lax.llnw.net (69.28.171.205) 10.256 ms 10.076 ms 13.520 ms
6 cox.tge1-3.fr3.lax.llnw.net (69.28.144.142) 10.212 ms 12.344 ms 10.471 ms
7 * rsmtdsrj02-ge710.0.rd.oc.cox.net (68.1.0.189) 11.964 ms 20.798 ms
8 ip68-4-13-138.oc.oc.cox.net (68.4.13.138) 12.443 ms 12.617 ms 12.631 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
</pre>Traceroute complete! That wasn't so bad, was it?

DrDavid

And yet you're seeing a slowdown? 20mbps (I'm jealous... I can get 30/15, but it's EXPENSIVE.. I'm only 15/2 right now on fios)..

a traceroute dying like that one trace isn't a big deal. That's kinda common on the internet. You're also pinging 19ms to San Jose so your latency is fantastic. There isn't any reason why it's being slow given the data I have in front of me.

Is the modem in a well ventilated place? Is it hotter than normal?

Have you been pinging www.smugmug.com ? Any lost packets?

David

DrDavid

orisky wrote:

And when I said tracerts don't complete, I'm talking about the one from
http://www.smugmug.com/homepage/traceroute.mg

That's just because you have ping reply disabled on your router. I'd ignore that result for the most part.

David

orisky

DrDavid wrote:

And yet you're seeing a slowdown? 20mbps (I'm jealous... I can get 30/15, but it's EXPENSIVE.. I'm only 15/2 right now on fios)..

a traceroute dying like that one trace isn't a big deal. That's kinda common on the internet. You're also pinging 19ms to San Jose so your latency is fantastic. There isn't any reason why it's being slow given the data I have in front of me.

Is the modem in a well ventilated place? Is it hotter than normal?

Have you been pinging www.smugmug.com ? Any lost packets?

David

sorry, had to let the dog out to pee

pinging smugmug
Ping statistics for 63.81.134.23:
Packets: Sent = 287, Received = 287, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 40ms, Average = 19ms
restarting the ping again

note that the problem isn't happening again.

DrDavid

Do you have any firewall software installed? Filtering software? Anything that would watch internet traffic?

David

orisky

DrDavid wrote:

Do you have any firewall software installed? Filtering software? Anything that would watch internet traffic?

David

Windows firewall, Symantec AV on a desktop and a laptop but not the 3rd laptop. Nothing else I believe that monitors traffic.

modem is well vented. Open air, even the shelf its on is slotted can't believe its the modem if other sites work. How do I ping the modem?

DrDavid

orisky wrote:

Windows firewall, Symantec AV on a desktop and a laptop but not the 3rd laptop. Nothing else I believe that monitors traffic.

modem is well vented. Open air, even the shelf its on is slotted can't believe its the modem if other sites work. How do I ping the modem?

It's not the modem if the ping tests are good to the router Too bad though, would have been an easy answer..

Symantec AV is a pain in the butt.. You said it's not on the 3rd laptop; do you have the same slowdown on that computer?

David

orisky

DrDavid wrote:

It's not the modem if the ping tests are good to the router Too bad though, would have been an easy answer..

Symantec AV is a pain in the butt.. You said it's not on the 3rd laptop; do you have the same slowdown on that computer?

David

i'm 99% sure it was happening too, but i'll check again the next time. I'll also turn SAV off on this too.

DrDavid

I'm actually starting to think that the problem is that SM itself is overloaded at those times you see the slowdown. Unless it's a transient issue with your hardware.. Do some ping tests overnight.. See what it looks like in the morning

David

orisky

i'll leave the pings going overnight to see if anything surfaces. I've asked the SM staff before and they said there weren't any issues on their side. I'm sure they're using some enterprise quality site monitoring tool with alerting that allows them to have this historical information...right?

DrDavid

orisky wrote:

i'll leave the pings going overnight to see if anything surfaces. I've asked the SM staff before and they said there weren't any issues on their side. I'm sure they're using some enterprise quality site monitoring tool with alerting that allows them to have this historical information...right?

THEY probably do.. But, don't know if they'd actually tell you that information (or if their support heros have access to that type of data).

David

orisky

Here are some results from last night:

Ping statistics for 63.81.134.23: (Smugmug)
Packets: Sent = 33977, Received = 33844, Lost = 133 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 1368ms, Average = 22ms

Ping statistics for 192.168.1.10: (Router)
Packets: Sent = 35987, Received = 35983, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 10ms, Average = 1ms

I also ran a ping utility called RoboTest, here are a few snippets of the 5mb log:

5208 02:56:06 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5208 02:56:06 Mar 30, 2008 Success: 0.02 secs
www.yahoo.com
5208 02:56:06 Mar 30, 2008 Success: 0.05 secs
www.google.com

5209 02:56:07 Mar 30, 2008 Failure: 2.13 secs
www.smugmug.com
5209 02:56:10 Mar 30, 2008 Success: 1.97 secs
www.yahoo.com
5209 02:56:12 Mar 30, 2008 Success: 2.00 secs
www.google.com

5210 02:56:15 Mar 30, 2008 Success: 2.00 secs
www.smugmug.com
5210 02:56:17 Mar 30, 2008 Success: 2.00 secs
www.yahoo.com
5210 02:56:19 Mar 30, 2008 Success: 2.00 secs
www.google.com

5211 02:56:22 Mar 30, 2008 Success: 2.00 secs
www.smugmug.com
5211 02:56:24 Mar 30, 2008 Success: 2.00 secs
www.yahoo.com
5211 02:56:26 Mar 30, 2008 Success: 2.00 secs
www.google.com

5212 02:56:29 Mar 30, 2008 Success: 2.00 secs
www.smugmug.com
5212 02:56:31 Mar 30, 2008 Success: 2.00 secs
www.yahoo.com
5212 02:56:33 Mar 30, 2008 Success: 2.00 secs
www.google.com

5213 02:56:36 Mar 30, 2008 Success: 2.00 secs
www.smugmug.com
5213 02:56:38 Mar 30, 2008 Success: 2.00 secs
www.yahoo.com
5213 02:56:40 Mar 30, 2008 Failure: 1.00 secs
www.google.com

5214 02:56:42 Mar 30, 2008 Failure: 1.47 secs
www.smugmug.com
5214 02:56:44 Mar 30, 2008 Success: 1.64 secs
www.yahoo.com
5214 02:56:46 Mar 30, 2008 Success: 1.83 secs
www.google.com

5215 02:56:49 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5215 02:56:49 Mar 30, 2008 Success: 1.94 secs
www.yahoo.com
5215 02:56:51 Mar 30, 2008 Success: 1.05 secs
www.google.com

5216 02:56:53 Mar 30, 2008 Success: 0.03 secs
www.smugmug.com
5216 02:56:53 Mar 30, 2008 Success: 0.03 secs
www.yahoo.com
5216 02:56:53 Mar 30, 2008 Success: 0.03 secs
www.google.com

5217 02:56:54 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5217 02:56:54 Mar 30, 2008 Success: 0.03 secs
www.yahoo.com
5217 02:56:54 Mar 30, 2008 Success: 0.05 secs
www.google.com

5218 02:56:55 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5218 02:56:55 Mar 30, 2008 Success: 0.03 secs
www.yahoo.com
5218 02:56:55 Mar 30, 2008 Success: 0.03 secs
www.google.com

5219 02:56:56 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5219 02:56:56 Mar 30, 2008 Success: 0.03 secs
www.yahoo.com
5219 02:56:56 Mar 30, 2008 Success: 0.03 secs
www.google.com

5220 02:56:57 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5220 02:56:57 Mar 30, 2008 Success: 0.19 secs
www.yahoo.com
5220 02:56:57 Mar 30, 2008 Success: 0.06 secs
www.google.com

5221 02:56:58 Mar 30, 2008 Success: 2.33 secs
www.smugmug.com
5221 02:57:01 Mar 30, 2008 Success: 2.05 secs
www.yahoo.com
5221 02:57:03 Mar 30, 2008 Failure: 17.25 secs
www.google.com

5222 02:57:22 Mar 30, 2008 Success: 5.75 secs
www.smugmug.com
5222 02:57:27 Mar 30, 2008 Success: 0.02 secs
www.yahoo.com
5222 02:57:27 Mar 30, 2008 Success: 0.05 secs
www.google.com

5223 02:57:28 Mar 30, 2008 Success: 0.02 secs
www.smugmug.com
5223 02:57:28 Mar 30, 2008 Success: 0.02 secs
www.yahoo.com
5223 02:57:28 Mar 30, 2008 Success: 0.05 secs
www.google.com


I also have a big block between 4:00 and 4:10 where all 3 were having times between 0 and 3secs. I think I set the router to auto reboot at a certain time, but I can't find the setting anywhere. That would possibly explain a hiccup for a few minutes at 4am, but for 10 mins seems long.</ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping></ping>

DrDavid

Everything looks basically fine. It's got to be a SM issue... I don't see anything that would make it slow other than a SM issue.

Wish I had a better answer. I hate not finding the real problem. BTW, what part of Orange County do you live in? (I'm assuming OC is Orange County California, right?)

David

orisky

Trying to revive this thread. I had a Smug site outage for about 5 minutes again just now. I was able to surf several other sites fine but the SM site just wouldn't come up. However, pings sent were fine:

Ping statistics for 63.81.134.23:
Packets: Sent = 140, Received = 140, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 46ms, Average = 21ms

docwalker

Orisky,

First, let me say thanks to DrDavid for helping out. I am not certain after reading all of what you wrote what is going on either. I have been having tons of trouble with getting to SmugMug and a few other locations but I know that it is my ISP. I am using Comcast from my home in Virginia. Just so you can see what I am getting: http://www.dslreports.com/linequality/nil/2378527

I feel your pain :cry. When I work from other locations on my lappy things run fine.

I see that you are in CA. We have had a few reports of problems from various CA users, as well as Comcast, and ATT users from around the US while others are not having any problems. I do not have access to the network monitoring data that you mentioned earlier.

I know that our engineers are monitoring the situation and they are making changes all the time to improve performance.

I see that you mention a 3rd laptop. Have you tried these laptops from other locations? I just want to see if they are off of your network and if they work ok.

Have you ran the DSLReports Linequality test? I would like to see those results if you have them.

www.dslreports.com/linequality/

DrDavid

docwalker wrote:

Orisky,

First, let me say thanks to DrDavid for helping out.

I'm on Verizon FIOS, and I see it routinely. Slow SM responses, slow loading, etc.. I'm at 15mbps, yet it can take a while to load a page. I kinda deal with it, but, I do also hear about it from a lot of clients that it's slow to come up. But, other times it pops up instantly.

Are you guys getting hammered by DDOS? or..?

David

docwalker

DrDavid wrote:

Are you guys getting hammered by DDOS? or..?

Not that I am aware of.

Up until this last few days when Comcast started acting up, I have had a rocket fast connection to SmugMug.

That is why when you say that it has been running slow for a while makes me .

DrDavid

docwalker wrote:

Not that I am aware of.

Up until this last few days when Comcast started acting up, I have had a rocket fast connection to SmugMug.

That is why when you say that it has been running slow for a while makes me .

Dunno... I have no latency issues. I use IPCop as my firewall (linux based.. it can handle WAY more traffic than it is currently used for), good wiring, great wifi signals, etc.. SM just loads slow sometimes. I'd swear it was capacity issues on SM servers.

David