News for hackers. Stuff that matters.
Re:Amazon DNS error by ejdyksen on Wednesday November 26, 2014 @07:50PM (#8665445)
Amazon appears to be up for me, but a number of places are still affected:

- All of Vox Media's properties (The Verge, Polygon, Vox.com, SBNation, etc)

- All of Atlasssian's services (Bitbucket, Jira OnDemand, etc)

- Flowdock

- Instagram

- aws.amazon.com has no assets

Edit: console.aws.amazon.com has no assets, either, so it's also currently worthless.

It's probably worth having a DNS failover strategy for Route53 (if that's what you're using) that doesn't involve the UI on console.aws.amazon.com.

Re:Amazon DNS error by stevekemp on Thursday November 27, 2014 @12:55AM (#8666162)
> It's probably worth having a DNS failover strategy for Route53 (if that's what you're using) that doesn't involve the UI on console.aws.amazon.com.

Which is one of the reasons I setup https://dns-api.com/ - A way of updating Route53 DNS via git hooks.

Re:Amazon DNS error by jbinto on Wednesday November 26, 2014 @08:12PM (#8665517)
Amazon.com is up for me, but is entirely missing product images.