From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Steve Golson <sgolson@trilobyte.com>
Cc: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Starlink on United
Date: Wed, 28 Jan 2026 19:19:00 +0100 [thread overview]
Message-ID: <CAJUtOOhYjkmCV959tmxyM4hYrtKkpBTeU7KCLXABBj9c4AKNEg@mail.gmail.com> (raw)
In-Reply-To: <4e91379a-a4a6-4105-9c7a-8cf36f938416@trilobyte.com>
Do you have any latency measurements? :-) You can use also our Bufferbloat
speedtest next time:
https://bufferbloat.libreqos.com
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Wed, Jan 28, 2026 at 7:08 PM Steve Golson via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Hi all,
>
> I took two flights over the weekend on United, with Starlink. 200+ Mbps
> from gate to gate. Quite impressive.
>
> On our second flight, while still standing in the terminal, I was able to
> log on to the aircraft's Starlink WiFi. That's pretty good WiFi range! A
> mere 30 Mbps on that connection though, with some packet loss.
>
> -Steve
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
>
next prev parent reply other threads:[~2026-01-28 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 18:08 [Starlink] Starlink on United Steve Golson
2026-01-28 18:14 ` [Starlink] " j pan
2026-01-28 18:19 ` Frantisek Borsik [this message]
2026-01-28 19:13 ` Steve Golson
2026-01-28 19:34 ` Ulrich Speidel
2026-01-28 19:46 ` Steve Golson
2026-01-29 6:02 ` 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=CAJUtOOhYjkmCV959tmxyM4hYrtKkpBTeU7KCLXABBj9c4AKNEg@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=sgolson@trilobyte.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