By way of additional info, this problem is a by-product of a change we made to the Blog*Spot infrastructure a little while back. Since that time, Blog*Spot has, by and large, been more reliable and faster. However, one remaining troublespot is the vulnerability of a particular filer. We're in process of retiring this filer which will make the whole service much more rock solid.
It is our highest priority to make Blog*Spot as quick and responsive as possible - the work we're doing now specifically addresses those goals. Thanks for bearing with us as we address this problem.
