I maintain this site at TypePad because I haven’t yet reached the point of geekery that I want to keep it on a server in my own home. That’s partly because, for the first time in many years, I have just one functional computer in my house, a PowerBook that wouldn’t handle hosting a site very well at all.
But it’s mostly because I’ve thoroughly enjoyed TypePad’s service, its flexibility with weblog design and its ease of use, particularly for someone like me whose knowledge of HTML, CSS, scripting, and other web-publishing goodness was limited but growing. I figured a hosted service would let me get my feet wet with the basics of bloggery and design and publishing, and would offer some flexibility to move from hosted to self-hosting via Movable Type if I decided that was the way to go.
I’ve now been with TypePad for over two years, first as a beta tester and later (and still) with a paid account. And with a couple of (unfortunately glaring) exceptions, I’ve been quite pleased with it. On the plus side, when I have had problems, the support I’ve received has been phenomenal. Generally quite fast response times, helpful information and suggestions to solve problems, and so on. These people really know how to run an email-only help desk, and from my own experience running a telephone-based help desk, I have exacting standards about it.
The downsides have been at times like the last two weeks as TypePad has experienced another period of growing pains, phenomenal growth and combined with limitations in its data center that prohibit adding equipment and capacity. When I start to see error messages and daily "performance degraded" notices and nothing beyond that, the frustration level mounts rapidly.
So I’m pleased today to see a detailed post on Mena’s Corner (via Everything TypePad) with details about the causes of the recent problems and what’s being to done to alleviate them.
I already knew TypePad was moving to a new data center; I’ve had a status update about it atop this site since Sun 10/23 (though I removed that notice this morning, changed the wording a bit to reflect my mounting frustration). I’m happy to know it’s in progress and to see more information about the nuts-and-bolts operation of TypePad.
Frustration level way down. Not gone, but it’s much better to get explicit confirmation that they are aware of the annoyance this causes, they’re already working on it, and when they expect to have it finished.
I’ve included the full text of Mena’s post after the jump so I have it for posterity in case it updates.