Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Bill Woodcock <woody@pch.net>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Cellular outage in US hits AT&T, T-Mobile and Verizon users, Downdetector shows + Cyberattacks on hospitals are likely to increase, putting lives at risk, experts warn
Date: Fri, 23 Feb 2024 01:03:31 +0100	[thread overview]
Message-ID: <4005F8F2-9D98-49AB-A993-02DD7ED7291A@pch.net> (raw)
In-Reply-To: <CAHxHggcJNJcJ=aPO8CGsSi91VvN=Co0aO+T_2f21ZtfhWfLTAA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]



> On Feb 23, 2024, at 00:42, Vint Cerf via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> Could some non-ATT outages be people trying to reach ATT destinations?

Yes, I think it’s very well established at this point that there were no associated simultaneous outages in any other networks, and that all of the “downdetector” things were just, as you say, people elsewhere trying to reach AT&T customers.

                                -Bill


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-23  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+aeVP_TbNXy-tnUbb27-fiMKd8pggAZmxZqow0g4ygVHteL8A@mail.gmail.com>
2024-02-22 20:51 ` David Bray, PhD
2024-02-22 21:11   ` Dave Taht
2024-02-22 21:24     ` Bill Woodcock
2024-02-22 23:39       ` the keyboard of geoff goodfellow
2024-02-22 23:42         ` Vint Cerf
2024-02-23  0:03           ` Bill Woodcock [this message]
2024-02-23 15:41             ` Dave Taht
2024-02-22 21:37     ` le berger des photons
2024-02-23 19:31       ` David Bray, PhD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4005F8F2-9D98-49AB-A993-02DD7ED7291A@pch.net \
    --to=woody@pch.net \
    --cc=nnagain@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox