Live data from Hacker News

Massive Dyn DNS outage

news.ycombinator.com

221–230 of 302 posts

Re: Massive Dyn DNS outage

#224

Earlier 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?

As a programmer, the loss of GitHub is a pretty big deal in terms of work productivity, and as a maintainer of production systems that rely on assets from GitHub, it's a pretty big availability issue.

Re: Massive Dyn DNS outage

#226
post #212
post #20

Important: 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.

I'm not trying to single out PagerDuty in being vulnerable. They run a particularly crucial service, and I'm sure they are doing everything they can to get out from under this.

That said, I still can't load www.pagerduty.com in a browser right now. :/

Re: Massive Dyn DNS outage

#228
post #225

Amazon DNS must be getting loads of new customers today :)

Even though their status page says everything is basically fine -- oh just a blip with API dns this morning no biggie -- they have had major problems today too. Like, can't connect to dynamodb, sqs, kinesis.

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.

Post reply on HN