[Tools-discuss] Did AWS outage affect datatracker?
Jim Fenton <fenton@bluepopcorn.net> Tue, 21 October 2025 01:03 UTC
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: tools-discuss@mail2.ietf.org
Delivered-To: tools-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 44ADB7923D9E for <tools-discuss@mail2.ietf.org>; Mon, 20 Oct 2025 18:03:25 -0700 (PDT)
X-Quarantine-ID: <pO95N0Jr-DUE>
X-Virus-Scanned: amavisd-new at ietf.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...T_ADDRESS@@ for details. Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pO95N0Jr-DUE for <tools-discuss@mail2.ietf.org>; Mon, 20 Oct 2025 18:03:23 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 853B27923CAD for <tools-discuss@ietf.org>; Mon, 20 Oct 2025 18:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Subject:To:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Z58GiE9l0ygjZxaHg13e/Z6Ysl9wiBHHh74/QGy1LRg=; b=XhTZMRSBxmx7fD8zCoHLe09ojc XDy0lI0NVymsEcdHj7G2He32sl/yC0dFOSGSfDZYRusVrtpPGb8pa3jJ+O7MaLUAw1df91t/bkw66 11T0fprEcgMCUCS1I01GrgJig4jANe+86Fgi/Er7/ETJVLpNQDdqkj4aXVc3Arc8Kprg=;
Received: from [2601:647:6883:8360:d439:64f:e2c7:f548] (helo=[10.10.20.171]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <fenton@bluepopcorn.net>) id 1vB0mK-00FI7k-2c for tools-discuss@ietf.org; Mon, 20 Oct 2025 18:03:08 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: tools-discuss@ietf.org
Date: Mon, 20 Oct 2025 18:03:07 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <6563C978-BF76-43A1-8B94-F098FF5124D5@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; markup="markdown"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: VGGD675NXAIAEYDRZIDVZDEPCDR65SWP
X-Message-ID-Hash: VGGD675NXAIAEYDRZIDVZDEPCDR65SWP
X-MailFrom: fenton@bluepopcorn.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] Did AWS outage affect datatracker?
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/HBEft2ktyJOOw4x2TXxiaSpGqpw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>
Particularly since this is the internet draft cutoff day before IETF 124, I’m wondering if the AWS outage affected datatracker, and specifically the ability to upload new drafts. I’m aware of one instance where a participant had difficulty submitting a draft that we were expecting for Dispatch (it said that the status is “awaiting manual post”, and I don’t know what triggers that). -Jim