New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More on historical AWS outages and lessons #43

Open
jlevy opened this Issue Aug 16, 2016 · 5 comments

Comments

Projects
None yet
4 participants
@jlevy
Copy link
Collaborator

jlevy commented Aug 16, 2016

@rjhintz

This comment has been minimized.

Copy link
Contributor

rjhintz commented Oct 31, 2016

Just parking this link here, though it's about the 2011 outage, since it and the follow on it references are a good resource. The Big List Of Articles On The Amazon Outage

Another: What we learned from the AWS Outage associated with this video with potato quality audio. Interesting that the speaker mentions aligning the AZs for all his accounts with the same numbering.

Other references, to be reviewed for applicability:

@danhermann

This comment has been minimized.

Copy link
Contributor

danhermann commented Nov 1, 2016

It was smaller in scale, but the DNS outage two weeks ago took down a number of AWS services in the us-east-1 region. My apps couldn't access SQS and others reported problems accessing DynamoDB and Kinesis. https://news.ycombinator.com/item?id=12763768

@bwagner5

This comment has been minimized.

Copy link

bwagner5 commented Nov 18, 2016

Oct 2012 Outage and Netflix's Post Mortem:
http://techblog.netflix.com/2012/10/post-mortem-of-october-222012-aws.html

EBS Outage can cause problems for EBS backed storage. Netflix switched to almost completely instance-store backed EC2.

@jlevy

This comment has been minimized.

Copy link
Collaborator

jlevy commented Mar 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment