From: "Livingood, Jason" <jlivin00@comcast.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] On "Throttling" behaviors
Date: Thu, 5 Oct 2023 20:24:51 +0000 [thread overview]
Message-ID: <F1FF1412-0C9A-4419-8132-AF94363502C3@cable.comcast.com> (raw)
In-Reply-To: <7o88o9p0-049q-s54r-604p-1n995rq89p60@ynat.uz>
> On 10/4/23, 13:45, "Nnagain on behalf of David Lang via Nnagain" <nnagain-bounces@lists.bufferbloat.net <mailto:nnagain-bounces@lists.bufferbloat.net> on behalf of nnagain@lists.bufferbloat.net <mailto:nnagain@lists.bufferbloat.net>> wrote:
> It's an unfortunate fact of reality that the enviornment in the US is one where
there is very little competition in the ISP space
The SEC 10-K filings of ISPs no longer support that. Most wireline ISPs are losing subscribers (at material levels) to one of the three new national 5G FWA ISPs (Verizon, T-Mobile, AT&T). In addition, we will in a few years see the effects of $45B+ of grant money dedicated to underwrite new broadband access network construction - that is also pretty material.
Per https://telecoms.com/523519/growth-in-5g-fwa-kit-matches-operator-hype/
- " 5G FWA customer premises equipment shipments more than doubled to 7.4 million last year and should reach 13.8 million – that’s 86% growth – this year "
- " The GSA survey shows overall FWA CPE shipments of 25.5 million units last year, "
- " Statistics shared by Leichtman Research Group recently showed that T-Mobile and Verizon together recorded the best part of 900,000 5G FWA net adds in the second quarter of this year, significantly more than the virtually flat cable segment and ahead of the wireline broadband market, which lost almost 62,000 customers in the three months. "
JL
next prev parent reply other threads:[~2023-10-05 20:25 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 17:15 [NNagain] Some backstory on the nn-again mailing list Dave Taht
2023-10-01 18:56 ` Frantisek Borsik
2023-10-01 19:51 ` [NNagain] On "Throttling" behaviors Dave Taht
2023-10-01 20:50 ` Dave Cohen
2023-10-01 22:01 ` Patrick Maupin
2023-10-02 1:34 ` dan
2023-10-02 7:28 ` Sebastian Moeller
2023-10-02 16:29 ` dan
2023-10-04 7:30 ` Sebastian Moeller
2023-10-02 15:30 ` Andy Ringsmuth
2023-10-02 18:28 ` Nathan Loofbourrow
2023-10-02 20:34 ` Colin_Higbie
2023-10-02 21:04 ` Dave Cohen
2023-10-02 21:07 ` rjmcmahon
2023-10-02 21:43 ` Colin_Higbie
2023-10-02 21:55 ` rjmcmahon
2023-10-03 19:29 ` Colin_Higbie
2023-10-03 19:45 ` rjmcmahon
2023-10-04 0:57 ` David Lang
2023-10-03 7:50 ` Sebastian Moeller
2023-10-03 8:10 ` Karl Auerbach
2023-10-03 14:41 ` Sebastian Moeller
2023-10-03 15:34 ` dan
2023-10-03 16:54 ` rjmcmahon
2023-10-03 17:55 ` Sebastian Moeller
2023-10-03 18:09 ` Frantisek Borsik
2023-10-03 18:14 ` dan
2023-10-03 19:44 ` Dick Roy
2023-10-03 18:10 ` dan
2023-10-03 19:23 ` rjmcmahon
2023-10-04 1:05 ` David Lang
2023-10-04 0:39 ` David Lang
2023-10-03 20:26 ` Colin_Higbie
2023-10-03 21:40 ` dan
2023-10-04 15:56 ` Colin_Higbie
2023-10-04 17:45 ` David Lang
2023-10-05 20:24 ` Livingood, Jason [this message]
2023-10-05 22:17 ` Dick Roy
2023-10-05 22:47 ` Jeremy Austin
2023-10-05 22:53 ` Dave Cohen
2023-10-06 15:56 ` Dick Roy
2023-10-06 15:58 ` rjmcmahon
2023-10-04 17:59 ` rjmcmahon
2023-10-04 19:26 ` Dick Roy
[not found] ` <MN2PR16MB3391A66B0DC222C43664DAD6F1CBA@MN2PR16MB3391.namprd16.prod.outlook.com>
2023-10-05 8:44 ` Sebastian Moeller
2023-10-05 19:07 ` David Lang
2023-10-03 23:17 ` Mark Steckel
2023-10-04 7:51 ` Sebastian Moeller
2023-10-02 6:48 ` Sebastian Moeller
2023-10-02 13:43 ` Livingood, Jason
2023-10-02 14:51 ` Mark Steckel
2023-10-02 18:09 ` Livingood, Jason
2023-10-02 18:15 ` Patrick Maupin
2023-10-02 19:18 ` Dick Roy
2023-10-02 6:34 ` Sebastian Moeller
2023-10-02 13:27 ` Livingood, Jason
2023-10-02 6:06 ` [NNagain] Some backstory on the nn-again mailing list Sebastian Moeller
2023-10-02 12:36 ` Bless, Roland (TM)
2023-10-03 7:15 ` Sebastian Moeller
2023-10-02 20:18 [NNagain] On "Throttling" behaviors Livingood, Jason
2023-10-02 20:28 ` Dick Roy
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=F1FF1412-0C9A-4419-8132-AF94363502C3@cable.comcast.com \
--to=jlivin00@comcast.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