There is no magic button to push to fix this and if you are referring to me as a post whore because my post total is high, it is there because I have been involved with this club since before the forum existed. I was the first president of the Colorado Chapter, I served as National President, and I am currently serving as Colorado Chapter President again.
As far as my credintials, I have been an EE/CS/ME since probably before you were born. I started with the net when it was called DARPANET.
Just because your browser says the server failed to return the data does not mean that

didn't send out the packets. There may be as many as 50 relay computers between

and your PC. Anyone of these could have problems with its forwarding tables at any time and cause the problem. There could be a problem with the domain name servers along the way. Every time I have seen this problem, and as I said, I have seen this problem before, it has been route related. That means that if I went through a different set of relay computers, there was no problem. That pretty much rules out

. You may not know this but

generates a ton of traffic. The last time I checked,

was one of the to 10 largest forums on the entire web. When you handle that much traffic, it goes out on multiple paths.
I did a route trace once and a single transaction on here took over 30 different paths through the web to get to my computer. Any one of these paths could cause the fault you saw.
This is the nature of the web. I see this type of thing on multiple sites from time to time. Give it some time and it will resolve itself.