It seems incredibly misguided to plug an IP address into hosts from a forum post. Is there an official source from GitHub?
Massive Dyn DNS outage
221–230 of 302 posts
Re: Massive Dyn DNS outage
#222Re: Massive Dyn DNS outage
#223Re: Massive Dyn DNS outage
#224Earlier quoted context omitted.
agreed 100%. This kind of thing shouldn't happen and this widespread. It's like no one is preparing for worse case scenarios until AFTER something tragic happens. On the West Coast and I just lost twitter/soundcloud/github - 9:40 am PST
loss of twitter, soundcloud, and github is what passes for tragic these days?
Re: Massive Dyn DNS outage
#225Re: Massive Dyn DNS outage
#226Important: PagerDuty.com seems affected by this outage. So keep a real good eye on your graphs today -- you might not receive the alert.
pagerduty has switched to AWS + 4 different root TLDS: $ 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.
That said, I still can't load www.pagerduty.com in a browser right now. :/
Re: Massive Dyn DNS outage
#227Re: Massive Dyn DNS outage
#228Amazon DNS must be getting loads of new customers today :)
Unfortunately they lie through their status page pretty regularly. I am not sure what it would take for them to admit they had a major problem.
Re: Massive Dyn DNS outage
#229sie.sps.columbia.edu/enroll