From: Dave Taht <dave.taht@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Performance Study
Date: Wed, 20 Sep 2023 08:43:20 -0700 [thread overview]
Message-ID: <CAA93jw6kQ4Xk795eKSYqDC==HQ3_g1jr2S8CbA-LzsXrOGN-3Q@mail.gmail.com> (raw)
In-Reply-To: <E9F74F05-1C3F-450B-8853-CE309965D30B@cable.comcast.com>
[-- Attachment #1.1: Type: text/plain, Size: 1550 bytes --]
Attached is a recent cloudflare test of verizon, taken about 1.2 miles from
a rural tower. While the bandwidth was low for reasons unknown, the latency
was... quite tolerable. Perhaps they are figuring this out.
I have no idea how atlas calculates latency or loss. Over what interval? In
the starlink case especially, I look at a typical plot, and I hope that if
more people looked at details like that, they would despair of using
averages ever again.
On Wed, Sep 20, 2023 at 8:05 AM Livingood, Jason via Starlink <
starlink@lists.bufferbloat.net> wrote:
> As some of you may recall I recruiting some US-based Starlink users to
> host RIPE Atlas probes as part of my role as a RIPE Atlas Ambassador. I
> just got word that NetForecast conducted a performance study that looked at
> RIPE Atlas data using some of the data from those and other probes. They
> looked at homes across the US with 5G fixed wireless, LEO satellite, and
> DOCSIS.
>
>
>
> They have posted a first report of this study at
> https://www.netforecast.com/wp-content/uploads/FixedWireless_LEO_CableComparisonReport_NFR5148-1.pdf.
> I am looking forward to other researchers looking into the RIPE Atlas data
> – I know a few are working on this.
>
>
>
> Jason
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
[-- Attachment #1.2: Type: text/html, Size: 3007 bytes --]
[-- Attachment #2: verizon.png --]
[-- Type: image/png, Size: 86657 bytes --]
prev parent reply other threads:[~2023-09-20 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:04 Livingood, Jason
2023-09-20 15:43 ` Dave Taht [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='CAA93jw6kQ4Xk795eKSYqDC==HQ3_g1jr2S8CbA-LzsXrOGN-3Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=Jason_Livingood@comcast.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