Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Mike Puchol <mike@starlink.sx>
To: Dave Taht <dave.taht@gmail.com>, Brennen Smith <brennen@ookla.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Starlink] LUL 220ms flat over starlink
Date: Tue, 2 Aug 2022 17:25:54 +0200	[thread overview]
Message-ID: <35295874-298b-4904-ae68-31aea4dfeae6@Spark> (raw)
In-Reply-To: <CAFwpvt7BeYr2ZEL+ZeqEJVDTHGykYY1ibnzGDD8pFD2TBHXw+w@mail.gmail.com>

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

The status of ISL has improved considerably over the last two months. It is now totally feasible to use in-plane (shown in my simulation, blue lines) and cross-plane (not yet shown, but in use by the constellation) to deliver traffic from Kyiv to Seattle:


Best,

Mike
On Aug 2, 2022, 17:17 +0200, Brennen Smith via Starlink <starlink@lists.bufferbloat.net>, wrote:
> Compared to GEO Sat links, this is very reasonable latency and distance.
>
> Either GeoIP is wrong, or they’re starting to balance within the mesh for capacity. If you look very closely at the maritime announcement - they’re right on schedule for the latter.
>
> > On Tue, Aug 2, 2022 at 07:41 Dave Taht <dave.taht@gmail.com> wrote:
> > > It is my guess over a path this (inaccurately selected? lasered?)
> > > long, the new speedtest doesn't saturate the link.
> > >
> > > https://twitter.com/olegkutkov/status/1554404854763819008
> > >
> > > --
> > > FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
> > > Dave Täht CEO, TekLibre, LLC
> --
> Brennen Smith VP Technology
> (206) 739-0807 | brennen@ookla.com
> linkedin.com/in/brennensmith
>
>
> This email, its contents and attachments contain information from Ziff Davis, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this email in error, please notify the sender by reply email and delete the original message and any copies.
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

[-- Attachment #2.1: Type: text/html, Size: 4336 bytes --]

[-- Attachment #2.2: Attachment.png --]
[-- Type: image/png, Size: 193791 bytes --]

  reply	other threads:[~2022-08-02 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 14:41 Dave Taht
2022-08-02 15:17 ` Brennen Smith
2022-08-02 15:25   ` Mike Puchol [this message]
2022-08-03  8:42     ` Bjørn Ivar Teigen
2022-08-03  9:47       ` [Starlink] [Rpm] " Sebastian Moeller

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=35295874-298b-4904-ae68-31aea4dfeae6@Spark \
    --to=mike@starlink.sx \
    --cc=brennen@ookla.com \
    --cc=dave.taht@gmail.com \
    --cc=rpm@lists.bufferbloat.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