Hi everyone, I’d like to apologize for all the problems you may have had with SR in the last month. I have been working on building a new co-located server cluster for SR to handle the traffic, and while that was going fine, I planned on installing it and then slowly migrating SR from the old servers to the new cluster as time permitted (i.e. in an orderly way). The old SR main server has been running for 3-4 years continuously, so I wasn’t too worried that everything would be fine. Of course, Murphy had something to say about that, so while the building was taking place, the old SR main server hard drive crashed (in August). I was able to get all the data off, but the new server wasn’t fully put together yet. So SR then automatically switched over to the backup servers, which generally are OK for a week or so, but then they started to crash under the load as well. This was responsible for all of those `can’t connect’ database errors we received emails about. Thanks for the notes — it really helps to know that people use SR and to hear from people! :) So the new server did not come online at the new co-location provider until around Sept 15, which left us with about a month of flaky-downtime that we could not really do anything about. And its funny, all the systems I put in place over the last 2 years to prevent exactly this problem from occurring (prompted by an explosion at our old provider several years ago) only barely held up the growth in traffic. You know, I idly wonder if while Murphy is playing his game, he also listens to `Walter Murphy: A Fifth of Beethoven’… I certainly would, dancing around, poking at cables, kicking peoples’ disks. Whoops! I didn’t mean to knock over that water into your server!