From: Dave Taht <dave.taht@gmail.com>
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 10:41:05 -0500 [thread overview]
Message-ID: <CAA93jw4fBytFF24pnaNhg2COH__vpO18Zk0zWrXHUzm8h_TsCg@mail.gmail.com> (raw)
In-Reply-To: <4005F8F2-9D98-49AB-A993-02DD7ED7291A@pch.net>
A strong point for resilience can be made by noting that the wifi
component of the network remained up. We have more than just phone
numbers to communicate, being able to also layer voice over signal,
videoconferencing, facetime and a zillion other tools that did not go
down.
The best and most snarky response I have seen yet to the debacle thus
far was "Upgrade to room 641A went south".
https://en.wikipedia.org/wiki/Room_641A
On Thu, Feb 22, 2024 at 7:03 PM Bill Woodcock via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
>
>
>
> > 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
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
--
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2024-02-23 15:41 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
2024-02-23 15:41 ` Dave Taht [this message]
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=CAA93jw4fBytFF24pnaNhg2COH__vpO18Zk0zWrXHUzm8h_TsCg@mail.gmail.com \
--to=dave.taht@gmail.com \
--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