Massive Dyn DNS outage
211–220 of 302 posts
Re: Massive Dyn DNS outage
#212Important: PagerDuty.com seems affected by this outage. So keep a real good eye on your graphs today -- you might not receive the alert.
$ host -t NS pagerduty.com
pagerduty.com name server ns-219.awsdns-27.com.
pagerduty.com name server ns-739.awsdns-28.net.
pagerduty.com name server ns-1198.awsdns-21.org.
pagerduty.com name server ns-1569.awsdns-04.co.uk.
I think I'm satisfied.
Re: Massive Dyn DNS outage
#213Re: Massive Dyn DNS outage
#214Re: Massive Dyn DNS outage
#215As example
https://cleantalk.org/blacklists There are 2 084 161 IP's blacklisted.
Re: Massive Dyn DNS outage
#216Re: Massive Dyn DNS outage
#217As example
https://cleantalk.org/blacklists There are 2 084 161 IP's blacklisted.
Re: Massive Dyn DNS outage
#218Re: Massive Dyn DNS outage
#219Re: Massive Dyn DNS outage
#220All this talk about redundancy, real-time apps, scalable architecture and and a "simple" DDOS against DNS architecture brings half of the internet down. Honestly did nobody think about having a spare dns at some other company? or even backup dns server exactly for a situation like that?
From where I'm looking at the internet (central Europe), I don't notice anything. Maybe your internet on the other side of the Atlantic is broken, ours seems to be working fine. ;-) Edit: Looks like the eastern part of the USA is affected: https://cloudharmony.com/status-for-dyn