"works on my machine"<p>Our infrastructure is heavily using Route53 and we are not seeing any outage. (~1000 domains)<p>Edit: from <a href="http://status.aws.amazon.com/" rel="nofollow">http://status.aws.amazon.com/</a><p>"5:19 AM PDT We are investigating reports of problems resolving some DNS records hosted on Route53 using the third party DNS resolvers 8.8.8.8 and 8.8.4.4 . DNS resolution using other third-party DNS resolvers or DNS resolution from within EC2 instances using the default EC2 resolvers are not affected at this time.<p>5:49 AM PDT We have identified the cause for an elevation in DNS resolution errors using third party DNS resolvers 8.8.8.8 / 8.8.4.4 and are working towards resolution. DNS resolution using other third-party DNS resolvers or DNS resolution from within EC2 instances using the default EC2 resolvers continues to work normally.<p>6:10 AM PDT Between 4:05 AM PDT and 5:56 AM PDT, some customers may have experienced elevated errors resolving DNS records hosted on Route 53 using DNS resolvers 8.8.8.8 / 8.8.4.4 . The issue has been resolved and the service is operating normally."
Probably the source of outage: <a href="https://news.ycombinator.com/item?id=16914698" rel="nofollow">https://news.ycombinator.com/item?id=16914698</a>
I saw issues resolving via azure dns servers (i have gitlab runners on there) as well:<p>ssh 10.0.1.7 ping -c 1 github-production-release-asset-2e65be.s3.amazonaws.com<p>ping: github-production-release-asset-2e65be.s3.amazonaws.com: Temporary failure in name resolution```