Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Here is a more detailed analysis of what happened: https://arstechnica.com/information-technology/2018/04/suspicious-event-hijacks-amazon-traffic-for-2-hours-steals-cryptocurrency/ On Apr 24, 2018, at 14:19 , Ryan McGinnis via Outages wrote: I suspect this was related to this issue (via

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

I suspect this was related to this issue (via ycombinator hacker news): https://doublepulsar.com/hijack-of-amazons-internet-domain-service-used-to- reroute-web-traffic-for-two-hours-unnoticed-3a6f0dda6a6f On Tue, Apr 24, 2018 at 8:51 AM, Zach Hanna via Outages wrote: >

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Resolved here too.. On Tue, Apr 24, 2018 at 7:30 AM Phil Lavin via Outages wrote: > Those prefixes had been withdrawn now – traffic is flowing correctly again > for us. If that was the cause, I suspect things are back to rights for > everyone now? > > One wonders why HE

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Those prefixes had been withdrawn now – traffic is flowing correctly again for us. If that was the cause, I suspect things are back to rights for everyone now? One wonders why HE doesn’t apply filters on a peer with 20 legit prefixes… From: Outages On Behalf Of

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

> (Sometimes, RFC 1918 resolvers actually forward to Google Public DNS or another public resolver.) My point about it being general outage referred to the fact that many users could not get answer from route53, even if they directly contacted aws without involvement of Google. DNS during the

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Thanks for confirming. I’ve raised a ticket with HE on our circuit. I presume nobody has a contact at 10297? From: Outages On Behalf Of Joseph B via Outages Sent: 24 April 2018 13:56 To: outages@outages.org Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

On Tue, Apr 24, 2018 at 05:54:21AM -0600, Zach Hanna via Outages wrote a message of 28 lines which said: > Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve > with Google DNS? It seems now OK. With the RIPE Atlas probes, no more SERVFAIL: %

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

On Tue, Apr 24, 2018 at 02:49:17PM +0200, Stephane Bortzmeyer wrote a message of 39 lines which said: > > Feels like a general outage, not specific to 8.8.8.8 > > I tend to disagree. See with 25 RIPE Atlas probes: > With the default resolver (sometimes Google Public DNS,

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

>> Feels like a general outage, not specific to 8.8.8.8 > I tend to disagree. See with 25 RIPE Atlas probes: I see your point. It appears different route53 zones are behaving differently. for example from my local network, instagram.com doesn't resolve, but my own r53 hosted domains do. On

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

On Tue, Apr 24, 2018 at 12:45:06PM +, Sajal Kayan wrote a message of 146 lines which said: > Feels like a general outage, not specific to 8.8.8.8 I tend to disagree. See with 25 RIPE Atlas probes: With Google Public DNS : % blaeu-resolve -r 25 --nameserver 8.8.8.8

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

https://pulse.turbobytes.com/results/5adf25e4ecbe40692e003abb/ 2 out of 4 nameservers for one of my domains hosted on route53 fail consistently from some locations, directly querying route53. Feels like a general outage, not specific to 8.8.8.8 On Tue, Apr 24, 2018 at 7:38 PM Russell Zen via

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

In fact, 3 of 4 nameservers on our main domain are advertised as different /24s by AS 10297. None of these can be queried. The other is advertised by AS 16509 (AWS) – this works. From: Outages On Behalf Of Phil Lavin via Outages Sent: 24 April 2018 13:20 To:

Re: [outages] [External] Re: Google 8.8.8.8 Resolution of Route53 domains

Yeah that looks wrong to me. It appears if I'm reading it correctly that route was published about 90 minutes ago? Timeline sorta matches... On Apr 24, 2018, 08:27, at 08:27, Phil Lavin via Outages wrote: >This doesn’t feel right, though I’ll admit I’ve never checked

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Confirmed Route53 affected on AWS status dashboard. Get Outlook for Android From: Outages on behalf of Stephane Bortzmeyer via Outages Sent: Tuesday, April 24, 2018 5:22:49 AM To:

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

> instagram.com Server: 8.8.8.8 Address:8.8.8.8#53 ** server can't find instagram.com: SERVFAIL > On Tue, Apr 24, 2018 at 6:20 AM, Phil Lavin via Outages wrote: > This doesn’t feel right, though I’ll admit I’ve never checked before. Our > only route to

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Looks more specific to AWS than it does to Google+AWS. Can’t resolve against some of AWS’s NS directly: phil@phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com ; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com ;; global options: +cmd ;; connection timed out; no

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

On Tue, Apr 24, 2018 at 05:54:21AM -0600, Zach Hanna via Outages wrote a message of 28 lines which said: > Anyone else seeing SERVFAIL for route53-hosted domains Can you provide a few names? ___ Outages mailing list

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

UPDATE: Amazon confirms a widespread issue with Route53 in us-east. On Tue, Apr 24, 2018 at 5:54 AM, Zach Hanna wrote: > Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve > with Google DNS? > ___ Outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Yeh. Still digging into it. From: Outages On Behalf Of Zach Hanna via Outages Sent: 24 April 2018 12:54 To: outages@outages.org Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve

[outages] Google 8.8.8.8 Resolution of Route53 domains

Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with Google DNS? ___ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages