Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dotzero <dotzero@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink "Best Effort" offering
Date: Wed, 28 Sep 2022 14:02:51 -0700 (PDT)	[thread overview]
Message-ID: <7qso1o8r-5962-4p61-661q-qrn5n0p92q38@ynat.uz> (raw)
In-Reply-To: <CAJ4XoYc2X+HaysuHZ4BgfSPaUek0TT_Gi8GhCtZk-VbTsfucMA@mail.gmail.com>

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

they sent it to everyone on the waiting lists.

I've used my dishy in 'roaming' mode, which is best effort and it worked better 
than trying to teather to my cell phone (the only other choice in the area) ;-)

I think the results are going to vary wildly depending on how heavy usage is in 
your area.

David Lang

On Wed, 28 Sep 2022, Dotzero via Starlink wrote:

> It appears they sent the email about best effort service to lots of people.
>
> On Wed, Sep 28, 2022 at 4:02 PM Dave Taht <dave.taht@gmail.com> wrote:
>
>> Awesome. We don't have any data on their best effort service. It would
>> be my hope they configure things
>> with buffering suitable for that range of achievable speeds.
>>
>> On Wed, Sep 28, 2022 at 12:53 PM Dotzero via Starlink
>> <starlink@lists.bufferbloat.net> wrote:
>>>
>>> I've been on the wait list for almost 10 months and just received an
>> email that I can sign up for a "best efforts" offering. Seeing as they also
>> indicated the estimated time for regular service is mid-2023, I decided to
>> go with it (You don't lose your place on the wait list). You can also
>> "pause" the best effort service so I don't really have anything to lose.
>>>
>>> Has anyone had experience with this offering? Any input appreciated. If
>> it makes a difference, location is Central East Ohio.
>>>
>>> According to
>> https://www.starlink.com/legal/documents/DOC-1002-69942-69?regionCode=US,
>> latency will be comparable to regular service, down will be 5-100mbs and up
>> will be 1-10mps unless service is deprioritized due to congestion.
>>>
>>> Thanks in advance.
>>>
>>> Mike
>>>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
>>
>>
>>
>> --
>> FQ World Domination pending:
>> https://blog.cerowrt.org/post/state_of_fq_codel/
>> Dave Täht CEO, TekLibre, LLC
>>
>

  reply	other threads:[~2022-09-28 21:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 19:53 Dotzero
2022-09-28 20:01 ` Dave Taht
2022-09-28 20:58   ` Dotzero
2022-09-28 21:02     ` David Lang [this message]
2022-09-28 21:04     ` Dave Taht
2022-09-28 23:07 ` Eugene Y Chang
2022-09-28 23:35   ` David Lang
2022-09-29  0:40     ` Eugene Y Chang
2022-09-29  4:29       ` David Lang
2022-09-29  7:50         ` Eugene Y Chang
2022-09-29  9:10           ` Sebastian Moeller
2022-09-29  9:14             ` David Lang
2022-09-29 19:38               ` Eugene Y Chang
2022-09-30 12:38                 ` Michael Richardson
2022-09-30 12:43                   ` Nathan Owens
2022-09-30 17:24                   ` Eugene Chang
2022-09-30 17:26                     ` Nathan Owens
2022-09-30 18:03                       ` Mike Puchol
2022-09-30 21:39 rob currie
2022-09-30 23:56 ` Eugene Chang

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=7qso1o8r-5962-4p61-661q-qrn5n0p92q38@ynat.uz \
    --to=david@lang.hm \
    --cc=dave.taht@gmail.com \
    --cc=dotzero@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