18 comments

[ 3.0 ms ] story [ 53.9 ms ] thread
(comment deleted)
Anyone know on what's going on?
An internal issue, not a cyberattack as previously reported.
Yet if you browse to the IP's directly, it is up...

http://170.149.168.130

"Wednesday, August 14, 2013 Last Update: 11:07 AM ET" 2 hours ago as of this post.
Weird didn't seem like a DNS problem.
Updated time is a few hours out, might be a cache server?
From the NY Times Twitter account, https://twitter.com/nytimes

"As you are undoubtedly aware, we are experiencing a server issue that has resulted in our e-mail and Web site being unavailable."

"We believe the outage is the result of an internal issue, which we expect to be resolved soon."

"We will communicate further when we have more information. - from @NYTimesComm"

They're providing updates through the twitters, though not terribly informative ones...

@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.

@nytimes: We believe the outage is the result of an internal issue, which we expect to be resolved soon. (2/3)

@nytimes: We will communicate further when we have more information. - from @NYTimesComm (3/3)

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.
It's back up, mostly.
nslookup nytimes.com

Server: 127.0.1.1

Address: 127.0.1.1#53

Non-authoritative answer:

Name: nytimes.com

Address: 170.149.168.130

Name: nytimes.com

Address: 170.149.172.130

going to http://170.149.168.130 works but going to nytimes.com doesnot work. Whats going on here?

if I had to play a hunch, name based virtualhost settings got messed up. Or a proxy/caching server not handling hostname passing correctly.
How does this get to the frontpage of HN?
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.
Oh no, where will I find out what to think now?