<p><pre><code> @tumblr
Tumblr has taken the site down in order to resolve a
network issue. We will update as we know more.
</code></pre>
<a href="https://twitter.com/tumblr/status/279000741706878976" rel="nofollow">https://twitter.com/tumblr/status/279000741706878976</a>
Incidentally, this means every startup (and some of the bigger kids) that hosts its status page on Tumblr is missing a status page at the moment... eg:
<a href="http://status.twitter.com" rel="nofollow">http://status.twitter.com</a>
<p><pre><code> dig +trace www.tumblr.com
*snip*
tumblr.com. 300 IN SOA pdns1.ultradns.net. hostmaster.tumblr.com. 2012121602 86400 7200 604800 300
;; Received 108 bytes from 204.74.108.1#53(204.74.108.1) in 21 ms
</code></pre>
Looks like their dns is down alright. You could try in your hosts file:<p><pre><code> 72.32.231.8 www.tumblr.com tumblr.com
</code></pre>
The ip is from their whois info and appears to be giving the We're sorry error message.
Seems it started with just a normal outage: <a href="http://thenextweb.com/insider/2012/12/12/tumblr-confirms-users-are-experiencing-slow-loading-and-intermittent-errors-engineers-are-on-it/" rel="nofollow">http://thenextweb.com/insider/2012/12/12/tumblr-confirms-use...</a>
Remember when we all decided Tumblr wasn't stable to host a professional site? Well... these people didn't.<p><a href="http://theatlantic.tumblr.com/" rel="nofollow">http://theatlantic.tumblr.com/</a>
<a href="http://fox411.blogs.foxnews.com/" rel="nofollow">http://fox411.blogs.foxnews.com/</a>
<a href="http://motherjones.tumblr.com/" rel="nofollow">http://motherjones.tumblr.com/</a>
<a href="http://gq.tumblr.com/" rel="nofollow">http://gq.tumblr.com/</a>
<a href="http://tumblr.elle.com/" rel="nofollow">http://tumblr.elle.com/</a>
Visit this page to see the length of downtime -> <a href="http://www.websitetest.com/ui/tests/50c922b17a6c8757bb000005" rel="nofollow">http://www.websitetest.com/ui/tests/50c922b17a6c8757bb000005</a>.<p>The test will run every 10 minutes for the next 10 hours. Testing is only good for diagnosing issues like downtime and performance issues.
They get hundreds of extra points for hosting their status page on their own service.<p>That's basically the main (already widely accepted) lesson people should take from this -- people want twitter updates as well as an outside-hosted blog and monitor for service availability.
The main site/webapp is still down (3 hours later) but individual sites are up. <a href="http://theparisreview.tumblr.com/" rel="nofollow">http://theparisreview.tumblr.com/</a><p>They're returning 66.6.36.7 for DNS.
That's pretty bad.<p>Admittedly, they update their zone very frequently (every time a user signs up/changes name/deletes themselves), but you'd think they would have an independent secondary DNS provider somewhere.