They're providing updates through the twitters, though not terribly informative ones...<p>@nytimes: Part 1/3: As you are undoubtedly aware, we are experiencing a server issue that has resulted in our e-mail and Web site being unavailable.<p>@nytimes: We believe the outage is the result of an internal issue, which we expect to be resolved soon. (2/3)<p>@nytimes: We will communicate further when we have more information. - from @NYTimesComm (3/3)
From the NY Times Twitter account, <a href="https://twitter.com/nytimes" rel="nofollow">https://twitter.com/nytimes</a><p>"As you are undoubtedly aware, we are experiencing a server issue that has resulted in our e-mail and Web site being unavailable."<p>"We believe the outage is the result of an internal issue, which we expect to be resolved soon."<p>"We will communicate further when we have more information. - from @NYTimesComm"
I've had no issues loading nytimes.com from multiple internet connections and various browsers. So not really down, maybe not updated, but definitely not down. I suppose they had it mostly resolved by time I tried browsing there, though.
When I looked into it earlier, their zone file was pretty empty except for some ns records and www. I'm assuming that something cleaned it out a bit as even the root record didn't resolve.
nslookup nytimes.com<p>Server: 127.0.1.1<p>Address: 127.0.1.1#53<p>Non-authoritative answer:<p>Name: nytimes.com<p>Address: 170.149.168.130<p>Name: nytimes.com<p>Address: 170.149.172.130<p>going to <a href="http://170.149.168.130" rel="nofollow">http://170.149.168.130</a> works but going to nytimes.com doesnot work. Whats going on here?