Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: <tom@evslin.com>
To: "'Luis A. Cornejo'" <luis.a.cornejo@gmail.com>,
	"'Dave Taht via Starlink'" <starlink@lists.bufferbloat.net>,
	"'bloat'" <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Bufferbloat
Date: Thu, 31 Aug 2023 16:22:34 -0400	[thread overview]
Message-ID: <0ede01d9dc48$e10ecd60$a32c6820$@evslin.com> (raw)
In-Reply-To: <CAKJdXWBcijY=V=uLQ6-29WPJ6W3S8Fad08m=sfTHbsmmefLQZQ@mail.gmail.com>


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

I’ve seen isolated results like this from my dish in central Vermont. They were more frequent during the beta.

 

From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Luis A. Cornejo via Starlink
Sent: Thursday, August 31, 2023 4:09 PM
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
Subject: [Starlink] Starlink Bufferbloat

 

I saw this screen shot on Reddit. Seemed like it might of been a fluke? Isolated case? Are they cheating? No way they have seen the light?

 

I don’t have my dishy anymore, but can someone double check for me?

 

https://reddit.com/r/Starlink/s/ysQ0AZ6RKX

 



 


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

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

  reply	other threads:[~2023-08-31 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 20:08 Luis A. Cornejo
2023-08-31 20:22 ` tom [this message]
2023-08-31 20:46   ` Luis A. Cornejo
2023-08-31 21:06     ` tom
2023-08-31 21:59       ` Spencer Sevilla
2023-09-01  6:39         ` Tom Zubko
2023-09-01 12:32           ` Luis A. Cornejo
2023-09-01 14:22             ` Tom Zubko
  -- strict thread matches above, loose matches on Subject: below --
2021-05-18  4:19 [Starlink] Starlink bufferbloat Brenton Roskopf

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/starlink.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='0ede01d9dc48$e10ecd60$a32c6820$@evslin.com' \
    --to=tom@evslin.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=luis.a.cornejo@gmail.com \
    --cc=starlink@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