Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Brandon Butterworth" <brandon-ml@bogons.net>
To: "Dave Taht via Starlink" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] I had forgotten how good this was
Date: Sat, 18 Jan 2025 21:59:33 +0000	[thread overview]
Message-ID: <eme936ee76-c805-4db2-9be2-b547387914d6@dd6059ae.com> (raw)
In-Reply-To: <CAA93jw5bxhcxKLpt_7P0b6b4Uzx0p9qOwUTtrFeyTxHG9ucrPw@mail.gmail.com>

saw this, thought oh that's awfully nice of them to go
to all that bother

https://x.com/SpaceBiz1/status/1880601039386141049
https://orbitaltoday.com/2025/01/15/spacex-tests-solution-to-starlink-satellites-interferening-with-on-ground-astronomy/

then saw these:

https://x.com/CatSE___ApeX___/status/1880640102889849065
"Nothing to do with astronomers.
Replenishrate down there is very expensive. Very frequent
beam to beam handovers. They’re forced. BC of a) Harq ACK
timeout (they don’t have ASTs patented trick) and b) FCC
throttled their power due to bad ACLR and nonexistent
sidelobe mitigation."

https://x.com/Megaconstellati/status/1880643289897894228
"Note that this is for the SpaceX Gen 2 satellites which ar
Ku-band broadband satellites, not D2D, the latter which
have never done their orbital raising but remained in
VLEO - most likely for the reason you mention"

brandon


  reply	other threads:[~2025-01-18 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 22:24 Dave Taht
2025-01-18 21:59 ` Brandon Butterworth [this message]
2025-01-21  7:35 ` Mike Puchol
2025-01-22 22:52   ` Dave Taht
2025-01-23  0:26     ` Ulrich Speidel

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=eme936ee76-c805-4db2-9be2-b547387914d6@dd6059ae.com \
    --to=brandon-ml@bogons.net \
    --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