DynamoDB has been down for about 25 minutes now and has taken other services with it, like Lambda, Cloudwatch, EC2, ASG, SQS. I'm assuming the 503's on Medium, TheNextWeb and The Guardian are related. Lots of people on Twitter confirming.<p>AWS has updated their status page to say they are looking into increased error rates on DynamoDB and increased APIs errors on EC2 as of 3AM PDT.<p>Full list of services affected:<p>* ASG<p>* CloudFormation<p>* CloudTrail<p>* Cloudwatch<p>* CodeCommit<p>* CodePipeline<p>* Config<p>* Directory Service<p>* DynamoDB<p>* EC2<p>* Elastic MapReduce<p>* Lambda<p>* Mobile Analytics<p>* OpsWorks<p>* RDS<p>* Redshift<p>* SES<p>* SNS<p>* SQS<p>* SWS<p>Heroku is now also reporting they are having issues because of AWS: https://status.heroku.com/incidents/811#update-2808<p>Status page is http://status.aws.amazon.com/
I'll take the opportunity to once again complain about how AWS's status page is a UX clusterfuck.<p>Pretty much the entire us-east-1 region is unreliable, that needs to be glaring from the page. Instead, I need to browse hundreds of happy green checkmarks to find out what is/n't broken by their unreasonable standard.<p>What a fucking joke.
We're seeing the same problems with DynamoDB... it started around 2:20 AM PDT (1 hour ago). We're not having any problems with EC2—what kind of problems are you seeing? I hope it's just affecting the API and not running instances.<p>Side note: Medium posted an article last week about how most of their data is stored in DynamoDB, so I'm sure the Medium outage is related.
Just spoke to AWS Premium Support around 4:35 AM. They don't have any more information than what's on the status page, basically. I was hoping to get an ETA for a resolution, but no such luck.