Washingtonpost.com appears to be down. Any others out?

[Tactical Peek]

Might be standard snafu, but I smell a big fat commie rat.


https://www.washingtonpost.com/

[C_U_L8R]

1. Extra points for the Dr Strangelove reference

[longship]

13. Indeed! Always appropriate.

And I don't care if this post hare-lips everybody on Bear Creek.

[Foggyhill]

2. This not maintenance, denial of service

Or the like

If someone knows the sites IP address they could verify if it's the DNS that is affected

[regnaD kciN]

3. If Newsweek goes down, I'll get VERY suspicious.

[Foggyhill]

6. Having those dues attacked would just draw

Attention to the news so that would be pretty dumb

[milestogo]

4. I can get to it.

[Foggyhill]

7. I could not a few minutes ago I am currently in Montréal

If they are attacking the DNS, you would get this kind of spotty failure especially ibecausr there local caching of DNS dada

[marybourg]

5. It's up now, according to:

http://www.isitdownrightnow.com/washingtonpost.com.html

[Foggyhill]

8. I think the site itself wasn't down

Just either a major path to it
Or DNS servers had a denial of service attaclk like what happened last week

[marybourg]

10. Down is down. nt.

[Foggyhill]

12. No, the web site could be working

But it's the web browsers that are looking up its name that could not get its ip address

If you had this IP address already, having it in a ststic file or a local DNS server that caches this data, you could still use the site

That's why DNS failures are not seen universally the same way by everyone

[sarcasmo]

9. Angry Russians on the Internet warpath.

[Tactical Peek]

11. Apparently it was available by mobile, or that came back first.

And I can reach it now through the non-mobile link.

Funny that their page 1 story is about the Russians meddling in the election.

[FreeStateDemocrat]

14. My access to WP.com is not available now:

This site can’t be reached

www.washingtonpost.com’s server DNS address could not be found.

[titaniumsalute]

15. Just got to it OK