Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: the keyboard of geoff goodfellow <geoff@iconia.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: Thu, 22 Feb 2024 16:39:11 -0700	[thread overview]
Message-ID: <CAEf-zribCGihBn=uudcZWpJFVXMgE0__TBMw8V2Kf6WWXdNZNw@mail.gmail.com> (raw)
In-Reply-To: <5FD342B1-F329-4DDF-A0DA-6ED02B17D164@pch.net>

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

if you look/see The Requisite "HUMPS" of/at all the carriers at
https://downdetector.com/ it seems to be more than just AT&T being involved

On Thu, Feb 22, 2024 at 2:25 PM Bill Woodcock via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> I have not seen any credible evidence of any networks other than AT&T
> being involved.
>
> The rumors of something to do with a SIM database don’t explain all the
> PRI trunks down, but those predated the mobile outages, so it might be two
> unrelated issues.
>
>                 -Bill
>
>
> > On Feb 22, 2024, at 10:12 PM, Dave Taht via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
> >
> > On Thu, Feb 22, 2024 at 3:52 PM David Bray, PhD via Nnagain
> > <nnagain@lists.bufferbloat.net> wrote:
> >>
> >>
> https://www.msn.com/en-gb/money/technology/cellular-outage-in-us-hits-at-t-t-mobile-and-verizon-users-downdetector-shows/ar-BB1iHBMF
> >
> > I had feared this was the natural outgrowth of the devastating DNS
> > KEYTRAP attack that was announced yesterday:
> >
> https://www.darkreading.com/cloud-security/keytrap-dns-bug-threatens-widespread-internet-outages
> >
> > But so far the bet on nanog is that "oops, cisco deleted the sim
> database."
> >
> > I think they are being snarky about "the" sim database. I´m pretty
> > sure they are just being snarky...
> >
> >> A cellular outage in the United States was reported by AT&T, T-Mobile,
> Verizon and other network users on Thursday, according to outage tracking
> website Downdetector.com.
> >>
> >> The number of reports of AT&T outages peaked at 31,931 at around 4:30
> a.m. ET, data from Downdetector, which tracks outages by collating status
> reports from sources including user-submitted errors on its platform,
> showed.
> >>
> >> More than 800 service outages of U.S. wireless carriers Verizon and
> T-Mobile were also reported on the platform.
> >>
> >> Verizon, T-Mobile and AT&T did not immediately reply to Reuters'
> requests for comment.
> >>
> >> And this -  I was just on a call where it's clear this is increasing:
> https://www.msn.com/en-us/health/health-news/cyberattacks-on-hospitals-are-likely-to-increase-putting-lives-at-risk-experts-warn/ar-BB1ihhll
> >>
> >> WASHINGTON (AP) — Cybersecurity experts are warning that hospitals
> around the country are at risk for attacks like the one that is crippling
> operations at a premier Midwestern children's hospital, and that the U.S.
> government is doing too little prevent such breaches.
> >>
> >> Hospitals in recent years have shifted their use of online technology
> to support everything from telehealth to medical devices to patient
> records. Today, they are a favorite target for internet thieves who hold
> systems' data and networks hostage for hefty ransoms, said John Riggi, the
> American Hospital Association’s cybersecurity adviser.
> >>
> >> --
> >> David Bray, PhD Principal, LeadDoAdapt Ventures, Inc.
> >> Loomis Innovation Council Co-Chair & Distinguished Fellow
> >> Henry S. Stimson Center, Business Executives for National Security
> >> _______________________________________________
> >> Nnagain mailing list
> >> Nnagain@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/nnagain
> >
> >
> >
> > --
> > 40 years of net history, a couple songs:
> > https://www.youtube.com/watch?v=D9RGX6QFm5E
> > Dave Täht CSO, LibreQos
> > _______________________________________________
> > Nnagain mailing list
> > Nnagain@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/nnagain
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
>

-- 
Geoff.Goodfellow@iconia.com
living as The Truth is True

[-- Attachment #2: Type: text/html, Size: 6378 bytes --]

  reply	other threads:[~2024-02-22 23:39 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 [this message]
2024-02-22 23:42         ` Vint Cerf
2024-02-23  0:03           ` Bill Woodcock
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='CAEf-zribCGihBn=uudcZWpJFVXMgE0__TBMw8V2Kf6WWXdNZNw@mail.gmail.com' \
    --to=geoff@iconia.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