Internet Outage Update

Glen <glen@amsl.com> Tue, 21 April 2020 20:07 UTC

Return-Path: <glen@amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7E83A0915 for <ietf-announce@ietfa.amsl.com>; Tue, 21 Apr 2020 13:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 S2I1cS0mZsk6 for <ietf-announce@ietfa.amsl.com>; Tue, 21 Apr 2020 13:07:10 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DA073A0911 for <ietf-announce@ietf.org>; Tue, 21 Apr 2020 13:07:10 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 6577E2020BB for <ietf-announce@ietf.org>; Tue, 21 Apr 2020 13:06:34 -0700 (PDT)
Received: from mail-ot1-f47.google.com (mail-ot1-f47.google.com [209.85.210.47]) by c8a.amsl.com (Postfix) with ESMTPSA id EC41C2020BA for <ietf-announce@ietf.org>; Tue, 21 Apr 2020 13:06:33 -0700 (PDT)
Received: by mail-ot1-f47.google.com with SMTP id g19so109254otk.5 for <ietf-announce@ietf.org>; Tue, 21 Apr 2020 13:07:09 -0700 (PDT)
X-Gm-Message-State: AGi0PuYQ1WYDH4z/QMHhQMJQY2QtubS5duWp3cfAGnNLSjiXonlBcK6c GYGIDhQqR6iKgf7J5m0xHSQc8OWasxLuOrpsiKw=
X-Google-Smtp-Source: APiQypIUAm5kj5UBvBNV4baRKj0MfLejow50U2ZMwuaPT55wleVPcBlI58apupgNUxtnRAENJVPdyup3E586nUUIQzw=
X-Received: by 2002:a9d:21ca:: with SMTP id s68mr14602176otb.15.1587499628749; Tue, 21 Apr 2020 13:07:08 -0700 (PDT)
MIME-Version: 1.0
From: Glen <glen@amsl.com>
Date: Tue, 21 Apr 2020 13:06:57 -0700
X-Gmail-Original-Message-ID: <CABL0ig5oJ9TdQWiMB-MhjF_DQWieJog-U6jGOf9NbBr=-FpFSw@mail.gmail.com>
Message-ID: <CABL0ig5oJ9TdQWiMB-MhjF_DQWieJog-U6jGOf9NbBr=-FpFSw@mail.gmail.com>
Subject: Internet Outage Update
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/LYwagmZQF3oK4k4r5-fkdemJirI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 20:07:13 -0000

All -

I've received the following two items from our ISP.  Note that there
are (at least) two cuts in the fiber.

--snip--
IP NOC reports that at the first fiber cut location, the anticipated
slack in the fiber span located in the secondary manhole for the south
end of the span is unable to be used. As such, crews are making
preparations to pull in approximately 3,000 feet of new fiber into a
viable fiber duct. Preparations to the fiber span at the north end
successfully remain ongoing at this time. Field Operations have
provided a tentative estimated time to restore (ETTR) of 0200 GMT on
April 22, 2020.
At the secondary fiber cut location, to expedite service restoration
fiber crews will be performing a single splice point and splicing a
temporary hand hold into service. Splicing efforts are anticipated to
commence at 19:30 GMT.
--snip--

and this just arrived right as I was preparing to send the above:

--snip--
The network is engineered to withstand a single fault in the backbone.
Today, there were multiple fiber cuts that created this unique
situation resulting in abnormal loss and latency inside the backbone
of the network.  The network rerouted traffic as designed around the
cuts and additional traffic engineering has taken place to mitigate
latency observed on IP services. Preparations are underway and
splicing activities are expected to begin in the next 30-minutes on
one of the damaged cables. As these fiber cuts are repaired continued
improvements will be seen as traffic shifts to the most optimal path
per design.  These fiber cuts have been escalated to the highest
levels and all essential repair teams are engaged and focused on the
most expeditious means of repair.
--snip--

Thank you for your patience.

Glen
--
Glen Barney
IT Director
AMS (IETF Secretariat)