News for hackers. Stuff that matters.
Re:January 28th Incident Report by paulddraper on Wednesday February 03, 2016 @11:24PM (#11031967)
The most recent issue that affected me was when all EC2 instances in VPCs couldn't connect to S3. At all.

It wasn't indicated on the status page until after it was fixed. And it was indicated as a green check in a sea of green checks. With a small "i" in the corner to represent the outage.

I love AWS. It's not without fault but overall I think it's been well architected, well documented, and well implemented.

But the status page has got to be the ultimate example of what not to do.

Re:January 28th Incident Report by jrochkind1 on Wednesday February 03, 2016 @11:31PM (#11031996)
Huh, I wonder if the status page is in fact based on any automated monitoring at all, or just manual updates? I guess probably automated monitoring, just not very good automated monitoring.
Re:January 28th Incident Report by bm1362 on Thursday February 04, 2016 @01:56AM (#11032454)
IIRC, it's manual and way up the chain.
Re:January 28th Incident Report by jrochkind1 on Thursday February 04, 2016 @12:20PM (#11035451)
That is pretty ridiculous.
Re:January 28th Incident Report by madeofpalk on Thursday February 04, 2016 @01:16AM (#11032361)
Considering how slow it is, my guess would be that it's manual.