From: Sauli Kiviranta <smksauli@gmail.com>
To: David Collier-Brown <davec-b@rogers.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Testing airBaltic free Starlink in-flight WIFI for mining remote operations
Date: Sat, 7 Jun 2025 15:26:37 +0300 [thread overview]
Message-ID: <CAJbqEYDdZ2f3+ynbqKH2YEwRJq6gVpRoWkad_X8GXK9P5zNNiA@mail.gmail.com> (raw)
In-Reply-To: <f566fd32-68b7-4b41-bdfb-a2211705b047@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 2931 bytes --]
Deal all,
The sad thing was that I was completely unprepared! I just sit on my seat,
and after the normal safety instructions I suddenly see familiar logo on
the screen and announcement. I first thought it must be some premium
service or rather just announcement on something they plan to do in the
future. Once it sink in and I connected on my phone and ran some speed
tests to see what was available, I realized that I gotta seize the
opportunity and grab my laptop to try figure out some tests.
David: "Showing a real-world demonstration of how well it worked is a
really cool thing to do."
- Good to hear! I was quite surprised how well it worked! Obviously its
quite ideal in terms of visibility, but everything else, the handovers,
speed of moving compared to the 16 km/h recommended for the roaming dishy
and another 150 users on the same network! Was very cool experience.
Oleg: "Have you tried to run StarDebug or at least official Starlink app on
your phone? I wonder is it possible to access the hardware and get some
debug data :)"
- No, did not think of doing this! Next time I will be prepared! I think we
will just send one of the guys for a cup of coffee in Vienna to collect
data since the interest is there!
JPan: "need more data though" + "do you happen to have any info about your
public ip address while on the plane, so we can figure out its pop and pop
handover behaviors along the way?"
- I only ran some ping sweeps, as I was really focused on the target server
that I ran the remote control tests through, for user-experience and what
it looks like at application layer. Will add this to my script so I always
get it. With 1000 samples, ping sweep 1, min/avg/max =
36.705/50.375/112.491 ms. Sweep 2, min/avg/max = 35.804/51.484/123.599 ms.
Sweep 3, min/avg/max = 35.844/49.873/111.873 ms. Across all samples
P99=73.86389, P50=48.9325, P1=37.88168. Quite impressive!
Spencer: "very interested in that exact detail if you happened to collect
it."
- Will make sure to have it next time!
Nitinder: "If you are embarking on future adventures with Starlink, please
install this in your browser and trigger a few tests"
- Noted! Will certainly do this next time!
*****
Question: Anything else of interest if we send one of our engineers to
collect more data? Please let me know and I will try to organize it!
*****
Best regards,
Sauli
On Fri, Jun 6, 2025 at 8:47 PM David Collier-Brown via Starlink <
starlink@lists.bufferbloat.net> wrote:
> Just a word of praise for Sauli:
>
> Showing a real-world demonstration of how well it worked is a really
> cool thing to do. It proved just how well it can work. It also
> motivated us to ask a lot of questions (:-))
>
> --dave
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 3512 bytes --]
next prev parent reply other threads:[~2025-06-07 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 13:03 Sauli Kiviranta
2025-06-06 14:36 ` J Pan
2025-06-06 14:43 ` Spencer Sevilla
2025-06-06 15:30 ` Nitinder Mohan
2025-06-06 16:03 ` J Pan
2025-06-06 16:59 ` contact
2025-06-06 17:47 ` David Collier-Brown
2025-06-07 12:26 ` Sauli Kiviranta [this message]
2025-06-07 14:17 ` 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=CAJbqEYDdZ2f3+ynbqKH2YEwRJq6gVpRoWkad_X8GXK9P5zNNiA@mail.gmail.com \
--to=smksauli@gmail.com \
--cc=davec-b@rogers.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