From: Darrell Budic <budic@onholyground.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] RIPE took a look at their data from Atlas probes behind starlink
Date: Thu, 25 Jul 2024 17:50:14 -0500 [thread overview]
Message-ID: <DB55151E-E6C4-4142-83AB-63E8AA18F633@onholyground.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
Published at the ACM web conference as well:
https://labs.ripe.net/author/nitinder-mohan/a-multifaceted-look-at-starlink-performance-the-good-the-bad-and-the-ugly/
A Multifaceted Look at Starlink Performance - The Good, the Bad and the Ugly
labs.ripe.net
[-- Attachment #2.1: Type: text/html, Size: 3191 bytes --]
[-- Attachment #2.2: iStock-1303115733.jpg --]
[-- Type: image/jpeg, Size: 33265 bytes --]
reply other threads:[~2024-07-25 22:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DB55151E-E6C4-4142-83AB-63E8AA18F633@onholyground.com \
--to=budic@onholyground.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