News for hackers. Stuff that matters.
Re:AWS outage summary by mrkurt on Friday October 26, 2012 @11:57PM (#4705301)
AWS sure does put out amazing post mortems. If only they'd make their status page more useful ...
Re:AWS outage summary by taligent on Saturday October 27, 2012 @12:19AM (#4705343)
How is the status page not useful ? It's so simple to understand.

Green if everything is fine. Green if there are intermittent problems. Green if nothing works.

Re:AWS outage summary by signifiers on Saturday October 27, 2012 @01:20AM (#4705442)
Too true. Today when Google's App Engine failed hard, they flat out said: "App Engine is currently experiencing serving issues – Python, Java, Go … Oct 26 2012, 07:30 AM-11:59 PM … Current Availability: 55.90%" and showed read/write I/O metrics were spiking through the roof. Their dashboard clearly labeled the relevant icon as the most severe "Service Interruption".

I admire that level of transparency.

Re:AWS outage summary by kordless on Saturday October 27, 2012 @01:28AM (#4705458)
Yeah, was thinking the same thing while looking at all the cool graphs.
Re:AWS outage summary by seldo on Saturday October 27, 2012 @05:04AM (#4705779)
And if things are really broken, green with a little "i" icon next to it.
Re:AWS outage summary by bigiain on Saturday October 27, 2012 @02:18AM (#4705544)
You left out "Green if everything is working - except the Chaos Monkey. All systems are working properly, but none of them failing randomly 'for your convenience'"
Re:AWS outage summary by davnola on Saturday October 27, 2012 @08:02AM (#4705981)
Haha. I'd love someone to release a greasemonkey/userscript for that status page to make degraded service more obvious.
Re:AWS outage summary by tonybaroneee on Saturday October 27, 2012 @01:22AM (#4705447)
Lol, thanks for a good laugh.