Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Kan <michael_kan@pcmag.com>
To: David Lang <david@lang.hm>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>,
	Inemesit Affia <inemesitaffia@gmail.com>,
	starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP)
Date: Mon, 8 Dec 2025 13:22:19 -0800	[thread overview]
Message-ID: <CAD1jbR1nw9XnK8ckFPx8d1aMwXCnSyt=j13Q_fVt+xbiiKr07w@mail.gmail.com> (raw)
In-Reply-To: <64n86r2n-qo8s-45or-36rr-9rrs41ors45p@ynat.uz>

latency for Amazon Leo? https://www.youtube.com/watch?v=nZCx612z930

On Mon, Dec 8, 2025 at 1:15 PM David Lang via Starlink <
starlink@lists.bufferbloat.net> wrote:

> Michael Richardson wrote:
>
> > David Lang <david@lang.hm> wrote:
> >    > Michael Richardson wrote:
> >
> >    >> Would be nice to be able to afford p2p video.
> >    >> Would be fantastic if L3 decisions could occur in space when the
> recipients
> >    >> are "nearby'
> >
> >    > I've seen a lot of people using starlink for zoom calls without
> issues
> >
> > I mean, without zoom or any central server in some DC.
> > "Church' sends video directly.
>
> what uplink bandwith are they needing? I see many people using starlink to
> stream live 4k video of cameras from Starbase Tx, frequently multiple
> cameras
> per starlink.
>
> David Lang
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
>

-- 


This email, its contents and attachments contain information from Ziff 
Davis, Inc. and/or its affiliates which may be privileged, confidential or 
otherwise protected from disclosure. The information is intended to be for 
the addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution or use of the contents of this message is prohibited. If you 
have received this email in error, please notify the sender by reply email 
and delete the original message and any copies.


      reply	other threads:[~2025-12-08 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-06 15:36 [Starlink] Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP) Frantisek Borsik
2025-12-06 16:36 ` [Starlink] " J Pan
2025-12-06 23:58 ` David Lang
2025-12-07  0:02   ` Inemesit Affia
2025-12-07  0:08     ` David Lang
2025-12-08  4:31       ` Inemesit Affia
     [not found]         ` <5098.1765221714@obiwan.sandelman.ca>
2025-12-08 20:57           ` David Lang
     [not found]             ` <2609.1765228007@obiwan.sandelman.ca>
2025-12-08 21:15               ` David Lang
2025-12-08 21:22                 ` Michael Kan [this message]

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='CAD1jbR1nw9XnK8ckFPx8d1aMwXCnSyt=j13Q_fVt+xbiiKr07w@mail.gmail.com' \
    --to=michael_kan@pcmag.com \
    --cc=david@lang.hm \
    --cc=inemesitaffia@gmail.com \
    --cc=mcr+ietf@sandelman.ca \
    --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