I'm suggesting the same approach as the one the other author used (it turned out to be a peering issue there)
- check your DNS resolver, make sure you get the right IP address (174.132.225.106)
- do a traceroute to the server and make sure you can actually reach it
- try telnetting to the server and see if you can find out anything by observing the response
If you find there is a peering issue (a router somewhere that drops traffic to the subnet HN is hosted on) then a whois on the ip of the router will sometimes give you contact information of the party responsible in case your own ISP gives you the run around.
Oh, and last, make sure nobody is pulling a prank on you, check your own iptables!
- check your DNS resolver, make sure you get the right IP address (174.132.225.106)
- do a traceroute to the server and make sure you can actually reach it
- try telnetting to the server and see if you can find out anything by observing the response
If you find there is a peering issue (a router somewhere that drops traffic to the subnet HN is hosted on) then a whois on the ip of the router will sometimes give you contact information of the party responsible in case your own ISP gives you the run around.
Oh, and last, make sure nobody is pulling a prank on you, check your own iptables!