Re:Summary of the Amazon DynamoDB Service Disruption
by colinbartlett on Wednesday September 23, 2015 @10:01AM
(#10264989)
Some services are reporting problems now. Starting with the same set as last time such as Heroku and lots of services that depend on it:
Re:Summary of the Amazon DynamoDB Service Disruption
by toomuchtodo on Wednesday September 23, 2015 @12:46PM
(#10266159)
DynamoDB, Cloudwatch, EC2, Scaling, and Elastic Beanstalk are all impacted currently.
Re:Summary of the Amazon DynamoDB Service Disruption
by Someone1234 on Wednesday September 23, 2015 @12:08PM
(#10265891)
Their status screen is totally misleading and utterly pointless. Someone needs to get all of the RSS feeds (which are actually accurate) and create a new dash which is honest.
Re:Summary of the Amazon DynamoDB Service Disruption
by reustle on Wednesday September 23, 2015 @01:13PM
(#10266358)
Are the RSS feeds more accurate than the status page?
Re:Summary of the Amazon DynamoDB Service Disruption
by Someone1234 on Wednesday September 23, 2015 @01:25PM
(#10266450)
I'd argue that they are.
Re:Summary of the Amazon DynamoDB Service Disruption
by impostervt on Wednesday September 23, 2015 @11:41AM
(#10265693)
Thank you for this. I was wondering why I was getting slow responses from their API Gateway. It's "green" on their status board, but based on what I saw Sunday, the two services are linked.
Re:Summary of the Amazon DynamoDB Service Disruption
by cddotdotslash on Wednesday September 23, 2015 @11:45AM
(#10265722)
Pretty much the exact same thing that happened the other day. DynamoDB, then Lambda, now API Gateway. I can't update my Lambda functions, a small percentage are timing out, and API Gateway is sending back a "We're out of capacity" message.
6:33 AM PDT We are investigating increased error rates for API requests in the US-EAST-1 Region.
Source: http://status.aws.amazon.com/