Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Hesham ElBakoury <helbakoury@gmail.com>,
	5grm-satellite@ieee.org,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Ambani Launches 15 Billion Dollars Space War Against Starlink
Date: Sun, 21 Jun 2026 12:55:33 -0700 (MST)	[thread overview]
Message-ID: <1ns7n619-n244-o592-91q3-38qn9qo4qn55@ynat.uz> (raw)
In-Reply-To: <CAJUtOOhXQJTnfvgm=KgB2t2cU3DhZKET7QvpsH=74nai_N+chA@mail.gmail.com>

Frantisek Borsik via Starlink wrote:

> The same as with Amazon Leo - the biggest issue will be bufferbloat.

I think it is going to depend a lot on who their launch provider is and who 
their satellite manufacturer is.

Leo is going to suffer from having to pay higher launch costs as they avoid 
using SpaceX, and they are building more traditional satellites than Starlink, 
which is both more expensive per satellite and can't launch as many in one shot.

Remember that Elon Musk had to fire the satellite teams management to get them 
into the 'cattle not pets' mindset. I don't think any other aerospace companies 
(other than ones run by former SpaceX folks) really buy in to that yet.

and then there is the huge difference between the SpaceX launc COST and the 
SpaceX launch PRICE (which is still significantly lower then the competition)

Bufferbloat can be an issue, but until you get enough birds in space, it isn't 
going to matter as much, you will actually be very short of bandwidth.

David Lang

  parent reply	other threads:[~2026-06-21 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21 18:11 [Starlink] Ambani Launches 15 Billion Dollars Space War Against Starlink Hesham ElBakoury
2026-06-21 19:03 ` [Starlink] " Frantisek Borsik
2026-06-21 19:11   ` Inemesit Affia
2026-06-21 19:24     ` Frantisek Borsik
2026-06-21 19:55   ` David Lang [this message]
2026-06-22  0:01     ` Joe Hamelin
2026-06-22  1:28 ` David Collier-Brown

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=1ns7n619-n244-o592-91q3-38qn9qo4qn55@ynat.uz \
    --to=david@lang.hm \
    --cc=5grm-satellite@ieee.org \
    --cc=frantisek.borsik@gmail.com \
    --cc=helbakoury@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