3 ms·
Stack Overflow was down
- digitalpbk 14y agoyup Server: google-public-dns-a.google.com Address: 8.8.8.8 * google-public-dns-a.google.com can't find stackoverflow.com: Server failed
- mflindell 14y agoLooks like I'm finished work for the day! Time to go home
- mossplix 14y agoyou can always use the google cache
- sairamkunala 14y agosuperuser.com - DOWN stackoverflow.com - DOWN serverfault.com - UP cdn.sstatic.net - DOWN Purely a DNS issue dig stackoverflow.com @ns3.serverfault.com # (authoritative DNS) ; <<>> DiG 9.8.3-P1 <<>> stackoverflow.com @ns3.serverfault.com ;; QUESTION SECTION: ;stackoverflow.com. IN A ;; Query time: 400 msec ;; SERVER: 69.59.196.217#53(69.59.196.217)
- kbaker 14y agoYeah, seems like ns3.serverfault.com was SERVFAILing its own record, so now that it has timed out all serverfault domains are down.
- denzil_correa 14y agoDown for me, oh well!
- mattquiros 14y agoHacker News was also briefly down a few minutes earlier: https://twitter.com/mattquiros/status/293220235702566913 https://twitter.com/mattquiros/status/293220235702566913
- rsingla 14y agoLooks like their stack has finally...overflowed.
- lscott3 14y agogood one!
- JasonPunyon 14y agoWe're on it. We're having DNS problems.
- alexholehouse 14y agoFYI: http://www.downforeveryoneorjustme.com http://www.downforeveryoneorjustme.com e.g http://www.downforeveryoneorjustme.com/stackoverflow.com http://www.downforeveryoneorjustme.com/stackoverflow.com
- v33ra 14y agoIf the long name is too hard to remember: http://isup.me/ http://isup.me/ e.g. http://isup.me/stackoverflow.com http://isup.me/stackoverflow.com
- DanBC 14y agohttp://meta.stackoverflow.com/questions/164444/dns-server-failure-for-all-stack-exchange-sites http://meta.stackoverflow.com/questions/164444/dns-server-fa... > It appears the nameservers for Stack Exchange are returning SERVFAIL for all queries, meaning most users are unable to access any Stack Exchange site, or will shortly lose access once their local DNS caches expire.
- KyleBrandt 14y agoAnswer as to the direct cause (posted to that question): "We recently relocated our NY datacenter, and therefore all the IPs in NY changed. We didn't update to the new IP for the master DNS server (in both the named.conf and the zone files), and therefore all of our slaves hit our expiry time (one week). This is fixed now, so things should start coming back up."
- danielhughes 14y agoWhen Stack Overflow went down tonight my productivity dropped precipitously. It reminds me of how grateful I am of the team at Stack Exchange. They built one hell of a resource.
- thejosh 14y agoworking fine now.
- itsbits 14y agoits up now..
- farnsworth 14y agoThis evening realized how dependent I am on SO. Trying to figure out how to dynamically set parameters for a CSS animation (turns out it's harder than it sounds) and the only useful answers I can find are on SO. Also very glad to have Google's cached versions.