[outages] CFR website refusing connections

[Goltz, Jim (NIH/CIT) [E]]

I've had several "looks OK" reports, so it's probably a problem local to me.  I am seeing RST packets apparently from 75.101.137.229, but sometimes someone sets our firewalls to send those instead of silently dropping the traffic, so that could be it.

Thanks, all.

--
Jim Goltz <jgoltz at mail.nih.gov>

From: Frank Bulk [mailto:fbulk at mypremieronline.com]
Sent: Tuesday, 08 January, 2013 14:19
To: Goltz, Jim (NIH/CIT) [E]; 'outages at outages.org'
Subject: RE: CFR website refusing connections

Loads fine for me.  Here's the wget output which shows the address I resolve to.

nagios:~/tmp# wget www.cfr.org<http://www.cfr.org>
--2013-01-08 13:18:10--  http://www.cfr.org/
Resolving www.cfr.org<http://www.cfr.org>... 75.101.137.229
Connecting to www.cfr.org|75.101.137.229|:80<http://www.cfr.org|75.101.137.229|:80>... connected.
HTTP request sent, awaiting response... 200 OK
Length: 143940 (141K) [text/html]
Saving to: âindex.html.1â

100%[=======================================================================================================>] 143,940      398K/s   in 0.4s

2013-01-08 13:18:11 (398 KB/s) - âindex.html.1â

nagios:~/tmp#

Frank

From: outages-bounces at outages.org<mailto:outages-bounces at outages.org> [mailto:outages-bounces at outages.org] On Behalf Of Goltz, Jim (NIH/CIT) [E]
Sent: Tuesday, January 08, 2013 12:24 PM
To: outages at outages.org<mailto:outages at outages.org>
Subject: [outages] CFR website refusing connections

The website for the Council on Foreign Relations, www.cfr.org<http://www.cfr.org>, has been refusing connections for most of the day today.  Normally I'd chalk it up to random problems, but given the recent watering-hole attack against the site, I thought I'd mention it here and see if anyone had heard anything.

--
Jim Goltz <jgoltz at mail.nih.gov<mailto:jgoltz at mail.nih.gov>>
HHS/NIH/CIT/DCSS/HSB/ASIG

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20130108/56b49126/attachment.htm>