Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Brendan Carr: "Six years ago, Americans lived through one of the greatest hoaxes in regulatory history...
Date: Wed, 25 Oct 2023 13:18:49 +0000	[thread overview]
Message-ID: <69B46F6D-38E9-47AB-B2FC-263CDE37EA00@comcast.com> (raw)
In-Reply-To: <CAA93jw5PN-ANqJJSUt-m0AGpOZamXUd8M=Xq0RRdxvBoWQYZuQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 922 bytes --]

On 10/24/23, 15:22, "Nnagain on behalf of Dave Taht 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:



> I do wish that he showed upload speeds, and latency under load,



Upstream usage in the US in 2020 increased 30% - 60% (https://www.bitag.org/documents/bitag_report.pdf). Then it reverted to a normal CAGR.



Also here are two charts of LUL changes across much of the US since 2021 FWIW (don’t have data before that, this is from the SamKnows system – which is pretty good). I don’t know how else to conclude that while there have been improvements, buffer bloat is still pretty atrocious on a national level.

[A graph with blue line  Description automatically generated]





[A graph with blue line  Description automatically generated]





[-- Attachment #1.2: Type: text/html, Size: 3953 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 135360 bytes --]

[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 141572 bytes --]

  parent reply	other threads:[~2023-10-25 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 18:20 the keyboard of geoff goodfellow
2023-10-24 19:21 ` Dave Taht
2023-10-24 19:47   ` Sebastian Moeller
2023-10-25  1:48   ` Vint Cerf
2023-10-25 13:18   ` Livingood, Jason [this message]
2023-10-27 21:24     ` Frantisek Borsik
2023-10-25 13:26   ` [NNagain] RFC: Public Communications on Tech Infrastructure Nathan Simington
2023-10-25 18:54     ` David Bray, PhD
2023-10-25 20:44       ` rjmcmahon
2023-10-25 20:56         ` David Bray, PhD
2023-10-25 21:32           ` rjmcmahon
2023-10-27 15:32     ` Dave Taht
2023-10-28  8:58       ` Frantisek Borsik

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=69B46F6D-38E9-47AB-B2FC-263CDE37EA00@comcast.com \
    --to=jason_livingood@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