Originally Posted by
ju100
I don't see any official statement from Amazon. Either it's good because they're using their time to fix it quickly instead of posting on twitter. Or it's bad because they have a tortoise's reaction time on this sunday morning...
31 affected services: it's bad. I'm not even sure it was that bad when it happened some years ago...
Netflix still running ok in Europe, some complaining in the US
The DynamoDB service is down, and many AWS services are using it internally...that's great...
3:00 AM PDT We are investigating increased error rates for API requests in the US-EAST-1 Region.
3:26 AM PDT We are continuing to see increased error rates for all API calls in DynamoDB in US-East-1. We are actively working on resolving the issue.
4:05 AM PDT We have identified the source of the issue. We are working on the recovery.
4:41 AM PDT We continue to work towards recovery of the issue causing increased error rates for the DynamoDB APIs in the US-EAST-1 Region.
4:52 AM PDT We want to give you more information about what is happening. The root cause began with a portion of our metadata service within DynamoDB. This is an internal sub-service which manages table and partition information. Our recovery efforts are now focused on restoring metadata operations. We will be throttling APIs as we work on recovery.
Posting Permissions
