Advice for Rackspace on communicating status updates

To the hard working employees of Rackspace:

Your hosting rocks, your customer service is consistently impressive, and your colleagues are extremely talented. Here's my concern. If I'm a customer, and I'm seeing issues with my Rackspace servers/apps/cloud, I have to quickly determine which of the the following places will tell me what's going on:

• Rackspace Status Twitter account (http://twitter.com/RackStatus)
• The Rackspace Cloud System Status (http://status.rackspacecloud.com/)
• Rackspace Email & Apps System Status Page (http://status.apps.rackspace.com/)
• The Official Rackspace Blog (http://www.rackspace.com/blog/)
• The Rackspace Cloud Blog (http://www.rackspacecloud.com/blog/)
• Rackspace Cloud Twitter account (http://twitter.com/rackcloud)
• Rackspace Twitter account (http://twitter.com/rackspace)

I presume there is a rational explanation for this. I even see a hint of method to this madness. Unfortunately when your customers are in a rush to figure out why their website is collapsing, they won't be in the mood to think about this rationally. Rackspace may be one of the the most experienced companies on the planet when it comes to dealing with frantic people. I would suggest taking some of that experience and putting it to work in raising the bar industry-wide for communicating status updates to your customers. To get you started, here are some ideas:

Suggestions to get you started

1. Consolidate all of your status updates at a single destination. Possibly at http://status.rackspace.com/? If nothing else, have a page there that points visitors to the best place to get updates for their specific service. Link customers to this page from your front page, support portals, and blogs.
2. Work to get Google/Yahoo/Bing/etc to point to this page for searches such as "rackspace status", "rackspace cloud status", "rackspace health", "rackspace uptime".
3. You're going in the right direction with the the Email & Apps System Status Page. I would follow this model for your entire service suite (versus the simple blog style).
4. If you want to differentiate from your competition, you have a number of options. Read this, this, and this.
5. Continue tweeting, blogging, and Scobleizing. The more communication channels and approaches the better. Just don't make people have to hunt around in a time of need.

You guys are doing all of the hard parts well. You are also in a unique position to understand the benefits of transparency and communication. With a little bit of work, you have the opportunity to create more fans, reduce support costs, and push the industry forward in an important area.

Update: Within 5 minutes of posting this, Robert Scoble pointed me to a Twitter list merging all of the Rackspace twitter accounts:

A great resource, though clearly not something that would be easy to find quickly.