Comment on Amazon DNS errorComments−ejdyksen11yAmazon 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 assetsEdit: 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.−stevekemp11yIt'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.−jbinto11yAmazon.com is up for me, but is entirely missing product images.
Comments
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.
Which is one of the reasons I setup https://dns-api.com/ - A way of updating Route53 DNS via git hooks.
Amazon.com is up for me, but is entirely missing product images.