Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Jim Forster <jim@connectivitycap.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink on United Airlines
Date: Sat, 6 Dec 2025 19:38:14 -0800	[thread overview]
Message-ID: <AC73384C-83DE-470A-B12F-6E46C2ADE93E@connectivitycap.com> (raw)
In-Reply-To: <MW4PR11MB7104E7C2A5DED40A2AE56103C7C7A@MW4PR11MB7104.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

Hi folks,

Yesterday I was on UA flight, DTW-ORD, with Starlink service.  I managed to run a Cloudflare Speed Test and a LibreQoS Bufferbloat test, 

I have not looked at them in any detail, but here they are.

  — Jim


[-- Attachment #2: Type: text/plain, Size: 3 bytes --]





[-- Attachment #3: Type: text/plain, Size: 2 bytes --]




  parent reply	other threads:[~2025-12-07  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 23:54 [Starlink] Starlink in IRTF Mtg Livingood, Jason
2025-11-04  0:02 ` [Starlink] " J Pan
2025-12-07  3:38 ` Jim Forster [this message]
2025-12-07 19:14   ` [Starlink] Re: Starlink on United Airlines J Pan

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=AC73384C-83DE-470A-B12F-6E46C2ADE93E@connectivitycap.com \
    --to=jim@connectivitycap.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