Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] some recent starlink waveform results
Date: Mon, 8 May 2023 16:05:34 +0000	[thread overview]
Message-ID: <59414B67-111B-4188-A60F-EF45773FA4F3@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw7pT1C2uA6STT10SKKtzwcyUsRinNTR--=MFcyn4VzF0g@mail.gmail.com>

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

Mildly interesting related to the WaveForm test - there are 83 RIPE Atlas probes on Starlink connections (AS 14593), of which 56 are currently connected.



RTT to a fixed root server destination:
https://atlas.ripe.net/results/maps/rtt-fixed/?measurement=1001&filter=14593



You can also find lots of other data on the Atlas platform. Here is one specific probe for example: https://atlas.ripe.net/probes/1004978/


From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Reply-To: Dave Taht <dave.taht@gmail.com>
Date: Saturday, May 6, 2023 at 11:43
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] some recent starlink waveform results

I have been having difficulty trusting waveform´s uplink results for over 9 months now.

https://www.reddit.com/r/Starlink/comments/134fvis/starlink_and_bufferbloat_how_bad_is_yours/<https://urldefense.com/v3/__https:/www.reddit.com/r/Starlink/comments/134fvis/starlink_and_bufferbloat_how_bad_is_yours/__;!!CQl3mcHX2A!EUTU9U7y3xSR6oKRw6jElsIf9isagaQnhHzN6jMIF61mJg_JPH2ZGY7o8Hkn9fptHe-XRV6-de66qEzqxmVAec9V7N7XWhhfTg$>

--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/<https://urldefense.com/v3/__https:/www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/__;!!CQl3mcHX2A!EUTU9U7y3xSR6oKRw6jElsIf9isagaQnhHzN6jMIF61mJg_JPH2ZGY7o8Hkn9fptHe-XRV6-de66qEzqxmVAec9V7N4MrEqL4w$>
Dave Täht CSO, LibreQos

[-- Attachment #2: Type: text/html, Size: 6895 bytes --]

      reply	other threads:[~2023-05-08 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 15:43 Dave Taht
2023-05-08 16:05 ` Livingood, Jason [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=59414B67-111B-4188-A60F-EF45773FA4F3@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=dave.taht@gmail.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