Comments on Transparent Uptime: Transparency case study, courtesy of ylastic

Good discussion of the same event from a different...

2008-11-26T14:39:00.000-08:00

Good discussion of the same event from a different angle: http://blog.programmableweb.com/2008/11/26/the-cloud-does-not-auto-validate-your-work/

That's pretty cool - I've been using an uptime mon...

2008-11-26T08:07:00.000-08:00

That's pretty cool - I've been using an uptime monitoring service called: http://www.internetuptimemonitor.com - They send emails/SMS Cell phone text messages, but not twitter. That's really cool

Sounds like a good plan. Would love to see it when...

2008-11-25T20:48:00.000-08:00

Sounds like a good plan. Would love to see it when it's live!

Thats a nice idea and would be ideal. We are plann...

2008-11-25T20:41:00.000-08:00

Thats a nice idea and would be ideal. We are planning to have a simple status page, and when we publish an update to it automatically farm it out to all the channels - twitter, blog, etc.

Thanks for the insight, especially that you guys w...

2008-11-24T12:37:00.000-08:00

Thanks for the insight, especially that you guys were emailing your customers during the event in addition to the twitter updates. I would still recommend you have an easy to find status page that your users can find easily that has the type of information you provided over email or twitter. Use the broadcast power of the Internet to its potential. That way you don't have to spend time emailing, twittering, and updating your blog, and spend more time fixing the problem. Ideally the status page would update all the communication platforms automatically for you.

Obviously this isn't a priority for you guys right now in this growth stage, but definitely something to think about if downtime happens again. Like you said, just keeping your users in the loop is the most important thing.

Thank you for mentioning us on your blog. We are a...

2008-11-24T04:53:00.000-08:00

Thank you for mentioning us on your blog. We are a small start-up from Atlanta that provides a single interface (web or mobile) for managing your AWS environment. We keep everyone in the loop by using twitter, email and our blog for communicating updates and other items of interest to our users. When we had the recent outage we used twitter extensively and emails to the customers to let them know that there was a problem and that we were working on it. Just saying there is a problem and not following up leaves a bad taste. So we decided to let everyone know exactly what was happening. We did not test our EBS snapshots as religiously as we should have. It would be a cop-out to blame AWS, as AWS doesn't test our snapshots, we do. Lesson learned :-( It's amazing how supportive users/customers are when you keep them in the loop...