From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] recent starlink rrul test result
Date: Thu, 3 Mar 2022 07:15:11 -0800 (PST) [thread overview]
Message-ID: <531qo367-1n76-1668-4n54-2o8nspps382@ynat.uz> (raw)
In-Reply-To: <CAA93jw4yeAATtAiip7wQxCUryuBA4TL1U2NkCEBzWjB=htrepA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
That said, I've been using starlink for work zoom calls for a while with no
significant issues (nothing I can pin on my side vs the other participants)
David Lang
On Thu, 3 Mar 2022, Dave Taht wrote:
> wildly variable bandwidth, adjusted at 15 sec intervals, induced
> latencies of 400ms, really terrible upload throughput relative to
> down.
>
> H/T David Lang for this data.
>
> On Thu, Mar 3, 2022 at 9:31 AM Livingood, Jason
> <Jason_Livingood@comcast.com> wrote:
>>
>> When folks experience sub-par video conferencing over Starlink, it'd be great to see working latency stats at that time - such as via the easy test at https://www.waveform.com/tools/bufferbloat.
>>
>> On 2/23/22, 09:38, "Starlink on behalf of Dave Taht" <starlink-bounces@lists.bufferbloat.net on behalf of dave.taht@gmail.com> wrote:
>>
>> https://urldefense.com/v3/__https://blog.tomevslin.com/2022/02/starlinks-zoomready-rating-is-going-down.html__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj8WTA26WA$
>>
>> --
>> I tried to build a better future, a few times:
>> https://urldefense.com/v3/__https://wayforward.archive.org/?site=https*3A*2F*2Fwww.icei.org__;JSUl!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj-yqmwsLA$
>>
>> Dave Täht CEO, TekLibre, LLC
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!CQl3mcHX2A!TjZjoTCGYO2gkt9xYrGdFrivrejHIdNjVe0TtEsCuQfDJTyNNy4u3_5CxlN2sj_SP7yVhg$
>>
>
>
>
next prev parent reply other threads:[~2022-03-03 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:37 [Starlink] zoomready result Dave Taht
2022-03-03 14:31 ` Livingood, Jason
2022-03-03 14:36 ` [Starlink] recent starlink rrul test result Dave Taht
2022-03-03 14:45 ` tom
2022-03-03 15:03 ` Dave Taht
2022-03-03 15:15 ` David Lang [this message]
2022-03-03 17:16 ` Nathan Owens
2022-03-03 17:42 ` tom
2022-03-03 20:36 ` David Lang
2022-03-03 20:37 ` David Lang
2022-03-09 14:23 ` [Starlink] zoomready result Nathan Owens
2022-03-09 14:57 ` Dave Taht
2022-03-09 15:17 ` Nathan Owens
2022-03-11 17:05 ` Luis A. Cornejo
2022-03-11 22:48 ` Nathan Owens
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=531qo367-1n76-1668-4n54-2o8nspps382@ynat.uz \
--to=david@lang.hm \
--cc=Jason_Livingood@comcast.com \
--cc=dave.taht@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