Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Podcast on in-flight Wi-Fi (Candela Technologies)
Date: Mon, 12 Jan 2026 18:02:55 -0700 (MST)	[thread overview]
Message-ID: <rq1p197p-850n-119r-pnsp-4s2nn6rrn6s2@ynat.uz> (raw)
In-Reply-To: <23685b96-0e02-43d4-96b9-586f340bc937@auckland.ac.nz>

Ulrich Speidel wrote:

> Starlink is attractive for backhaul due to the fact that it covers the whole 
> globe,

from the reports, starlink also provides lower latency and more bandwidth to the 
aircraft, making it a much better experience (some of that may be due to the 
fact that starlink is debloated while the traditional uplinks have frequently 
ended up with multi-second latency under load)

David Lang

      reply	other threads:[~2026-01-13  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  7:17 [Starlink] Podcast on in-flight Wi-Fi (Candela Technologies) Frantisek Borsik
2026-01-12 15:05 ` [Starlink] " J Pan
2026-01-12 21:06 ` Ulrich Speidel
2026-01-13  1:02   ` David Lang [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=rq1p197p-850n-119r-pnsp-4s2nn6rrn6s2@ynat.uz \
    --to=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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