Hacker News new | past | comments | ask | show | jobs | submit login

I've been interested to see AWS status page misrepresent this through its icons while annotating the continuing issues.

1) Long before EBS API was returned, AWS adjusted the "Amazon Elastic Compute Cloud (N. Virginia)" status[1] for 24 April to show operational (green). This has since been corrected in the "Amazon EC2 (N. Virginia)" Status History.

2) Their own RDS service, which is instances backed by EBS, remained unavailable for its users, proving that #1 was false. If they couldn't operate a service (RDS) built on themselves (EC2) normally, the underlying service (EC2) should not have been considered Operational in the status page.

3) At present, the icon for "Amazon Elastic Compute Cloud (N. Virginia)" is Green for "Service is operating normally" instead of Yellow for "Performance issues", though the text description is not "Service is operating normally." but "Instance connectivity, latency and error rates."

4) It seems from anecdotal observation they're using the status page at least as "median status", or perhaps closer to "20th percentile status", meaning >80% of something can be down before it toggles to "Service Disruption".

[1] http://status.aws.amazon.com/




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: