Live data from Hacker News

Massive Dyn DNS outage

news.ycombinator.com

201–210 of 302 posts

Re: Massive Dyn DNS outage

#201

Issue came from dynect.net: $ dig +trace github.com ; > DiG 9.8.3-P1 > +trace github.com [...] ;; Received 488 bytes from 192.228.79.201#53(192.228.79.201) in 154 ms github.com. 172800 IN NS ns1.p16.dynect.net. github.com. 172800 IN NS ns3.p16.dynect.net. github.com. 172800 IN NS ns2.p16.dynect.net. github.com. 172800 IN NS ns4.p16.dynect.net. ;; Received 178 bytes from 192.42.93.30#53(192.42.93.30) in 54 ms ;; conne…

If you need access to GitHub, add these to your hosts file:

192.30.253.113 github.com

151.101.4.133 assets-cdn.github.com

Re: Massive Dyn DNS outage

#203
post #85

I'm a GitHub employee and want to let everyone know we're aware of the problems this incident is causing and are actively working to mitigate the impact. "A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time." is the content from our latest status update on Twitter ( https://twitter.com/githubstatus/status/789452827269664769 ). Reposted here since some peo…

how did you post on twitter which is down too?

Twitter isn't down, just DNS resolution of twitter.com

Re: Massive Dyn DNS outage

#205
post #201

Issue came from dynect.net: $ dig +trace github.com ; > DiG 9.8.3-P1 > +trace github.com [...] ;; Received 488 bytes from 192.228.79.201#53(192.228.79.201) in 154 ms github.com. 172800 IN NS ns1.p16.dynect.net. github.com. 172800 IN NS ns3.p16.dynect.net. github.com. 172800 IN NS ns2.p16.dynect.net. github.com. 172800 IN NS ns4.p16.dynect.net. ;; Received 178 bytes from 192.42.93.30#53(192.42.93.30) in 54 ms ;; conne…

If you need access to GitHub, add these to your hosts file: 192.30.253.113 github.com 151.101.4.133 assets-cdn.github.com

Thank you!
Post reply on HN