Re: IETF Service Outage

"Scott Weeks" <surfer@mauigateway.com> Wed, 23 March 2016 18:20 UTC

Return-Path: <surfer@mauigateway.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48CC712D806 for <ietf@ietfa.amsl.com>; Wed, 23 Mar 2016 11:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level:
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyt9YCXrYkyj for <ietf@ietfa.amsl.com>; Wed, 23 Mar 2016 11:20:11 -0700 (PDT)
Received: from imta-38.everyone.net (imta-38.everyone.net [216.200.145.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0A2C12D80D for <ietf@ietf.org>; Wed, 23 Mar 2016 11:20:09 -0700 (PDT)
Received: from pps.filterd (localhost.localdomain [127.0.0.1]) by imta-38.everyone.net (8.14.5/8.14.5) with SMTP id u2NIJLC4023528 for <ietf@ietf.org>; Wed, 23 Mar 2016 11:20:09 -0700
X-Eon-Originating-Account: A5vV6gMaRqt952eYl0ZM25gDGR6lomzsp7efb7ODZ8jC2rAC9piDVyeBACyDkQZg
X-Eon-Dm: m0094771.ppops.net
Received: by m0087795.mta.everyone.net (EON-PICKUP) id m0087795.56ec7a72.90ea; Wed, 23 Mar 2016 11:20:08 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20160323112007.8BBF1AE2@m0087795.ppops.net>
Date: Wed, 23 Mar 2016 11:20:07 -0700
From: "Scott Weeks" <surfer@mauigateway.com>
To: <ietf@ietf.org>
Subject: Re: IETF Service Outage
X-Eon-Sig: AQLAznNW8t5Y3vhFNQEAAAAB,5719cc396f55fb4fa3f4424a2681d400
X-Originating-Ip: 199.211.157.2
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-03-23_09:2016-03-23,2016-03-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1601100000 definitions=main-1603230280
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OZbtxG1zgFSG4jWJKeZnDS00MDM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: surfer@mauigateway.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 18:20:12 -0000


--- glen@amsl.com wrote:
From: Glen <glen@amsl.com>

Our engineers are always looking at additional ways of monitoring
things, but whether this was some kind of denial-of-service attack
against a physical host, or an OS failure of some kind, or maybe just
a bad network cable, we can't yet tell.
---------------------------------------------------


If you can't tell whether it was a DoS or a bad network cable 
you should talk to network operators.  We can help.  We deal 
with these things all the time.

scott