Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Luca Muscariello <muscariello@ieee.org>
To: Jared Mauch <jared@puck.nether.net>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] slowdown at starlink?
Date: Sun, 29 Aug 2021 10:25:21 +0200	[thread overview]
Message-ID: <CAH8sseS=nSMxhj92UfD-shiXAbyAKN6nWZ8gFkMCEF0ySqQvfQ@mail.gmail.com> (raw)
In-Reply-To: <3AC81321-C777-4F2D-A096-2677DBC6DE1B@puck.nether.net>

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

I'd be curious to see the packet loss rate.
Could you share the full report?


On Sun, Aug 29, 2021, 02:56 Jared Mauch <jared@puck.nether.net> wrote:

> Here’s what I’m seeing from my system:
>
> pi@pi-starlink:~ $ speedtest-cli
> Retrieving speedtest.net configuration...
> Testing from Starlink (205.174.156.69)...
> Retrieving speedtest.net server list...
> Selecting best server based on ping...
> Hosted by Nitel (New York, NY) [0.09 km]: 49.967 ms
> Testing download
> speed................................................................................
> Download: 5.07 Mbit/s
> Testing upload
> speed......................................................................................................
> Upload: 4.22 Mbit/s
>
> pi@pi-starlink:~ $ speedtest-cli
> Retrieving speedtest.net configuration...
> Testing from Starlink (205.174.156.69)...
> Retrieving speedtest.net server list...
> Selecting best server based on ping...
> Hosted by Starry, Inc. (New York, NY) [0.09 km]: 45.384 ms
> Testing download
> speed................................................................................
> Download: 6.11 Mbit/s
> Testing upload
> speed......................................................................................................
> Upload: 4.81 Mbit/s
>
> Looks bad right now.
>
> - Jared
>
> > On Aug 28, 2021, at 8:51 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > There is a thread on reddit about some major slowdown at starlink.
> > Perhaps they are trying some form of ARED or something that doesn't
> > work
> > well? or  encounering issues with the CGNAT ?
> >
> >
> https://www.reddit.com/r/Starlink/comments/pc8nca/speeds_decreased_significantly_during_the_past/?sort=new
> > --
> > Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
> >
> > Dave Täht CEO, TekLibre, LLC
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

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

  parent reply	other threads:[~2021-08-29  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29  0:51 Dave Taht
2021-08-29  0:56 ` Jared Mauch
2021-08-29  1:08   ` Jared Mauch
2021-08-29  8:25   ` Luca Muscariello [this message]
2021-08-29 19:05     ` Jared Mauch
2021-08-29 19:23       ` Luca Muscariello
2021-08-30  0:13         ` Nick Buraglio
2021-08-30  0:43           ` Nathan Owens
2021-09-01  9:38 ` Joerg Deutschmann

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='CAH8sseS=nSMxhj92UfD-shiXAbyAKN6nWZ8gFkMCEF0ySqQvfQ@mail.gmail.com' \
    --to=muscariello@ieee.org \
    --cc=dave.taht@gmail.com \
    --cc=jared@puck.nether.net \
    --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