Read up on the latest news
at cloud.ca

Image credit: XKCD What happened? Amazon Web Services experienced a service disruption for 8 hours and 33 minutes on Sunday, September 20, 2015, from 2:19 AM PDT to 10:52 AM PDT. The outage, which affected its US-EAST–1 North Virginia location, began with a network disruption that significantly increased error rates on Amazon’s DynamoDB (NoSQL database) service. This led to a cascade whereby some 37 other AWS services would begin to falter and show increased error rates for API requests. Among these were the AWS SQS (Simple Queue Service), EC2 (Elastic Compute Cloud), CloudWatch (resource... Continued

Image credit: XKCD What happened? Amazon Web Services experienced a service disruption for 8 hours and 33 minutes on Sunday, September 20, 2015, from 2:19 AM PDT to 10:52 AM PDT. The outage, which affected its US-EAST–1 North Virginia location, began with a network disruption that significantly increased error rates on Amazon’s DynamoDB (NoSQL database) service. This led to a cascade whereby some 37 other AWS services would begin to falter and show increased error rates for API requests. Among these were the AWS SQS (Simple Queue Service), EC2 (Elastic Compute Cloud), CloudWatch (resource... Continued