Re: IETF Service Outage

"Scott Weeks" <> Thu, 24 March 2016 19:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5C2512D52B for <>; Thu, 24 Mar 2016 12:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.955
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JSINgGbWKv2A for <>; Thu, 24 Mar 2016 12:54:56 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3422112D508 for <>; Thu, 24 Mar 2016 12:54:56 -0700 (PDT)
Received: from pps.filterd (localhost.localdomain []) by (8.14.5/8.14.5) with SMTP id u2OJqKQp029639 for <>; Thu, 24 Mar 2016 12:54:55 -0700
X-Eon-Originating-Account: 5kgwyzD6kDHgsrTDraGxSDf5WDHXcNnXVHiMnGk-CC73ZzKV1yAU4GJJaGD9ZL_L
Received: by (EON-PICKUP) id m0087795.56ec7a72.cd80; Thu, 24 Mar 2016 12:54:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Message-Id: <>
Date: Thu, 24 Mar 2016 12:54:55 -0700
From: "Scott Weeks" <>
To: <>
Subject: Re: IETF Service Outage
X-Eon-Sig: AQLAznNW9EYPmqnMgAEAAAAB,88e9514111a4be127930438980c28ba2
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-03-24_08:2016-03-24,2016-03-24,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-1603240305
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Mar 2016 19:54:58 -0000

--- wrote:
--- wrote:

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.

My apologies if the tone of the email was not nice.  I 
didn't mean it to be.  Also, it should've been private.  
I should've said I am a network operator of many years 
and am happy to help if I can, just let me know.