Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Gary E. Miller" <gem@rellim.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink at sea
Date: Wed, 13 Jul 2022 17:59:57 -0700	[thread overview]
Message-ID: <20220713175957.5fc577a4@spidey.rellim.com> (raw)
In-Reply-To: <rrq4187s-5s6-n338-rq5p-155r1pq58326@ynat.uz>

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

Yo David!

On Wed, 13 Jul 2022 17:40:38 -0700 (PDT)
David Lang <david@lang.hm> wrote:

> it all depends on what you are comparing it to. This isn't designed
> for a 30 ft boat, but rather for commercial operations. SpaceX had
> talked about how this replaces the earlier satellite services they
> have had on their boats that were unreliable and cost >$150k/month
> with much better service listing for <$50k/month (for all their boats)

Yes, it compares favorably to the existing alternatives.  A mega-yauct
owner would not notice the price.

> This is designed to be an all-weather allways-on service, most
> boaters could just use a standard starlink RV setup and put it out
> when they need it (taking it down when the weather is poor)

Excapt, Starlink will not let yuo use the RV roaming plan when offshore.
The maritime plan explicitly covers open ocean.  The RV plan hardly goes
beyond the sight of land.

I imagine the main driver of the high cost is the prolem in getting
downlink stations between California and Hawaii, etc.  This will be a
real test of the sat to sat relaying.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 851 bytes --]

  reply	other threads:[~2022-07-14  1:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  0:20 Dave Taht
2022-07-14  0:31 ` David Lang
2022-07-14  0:36 ` Gary E. Miller
2022-07-14  0:40   ` David Lang
2022-07-14  0:59     ` Gary E. Miller [this message]
2022-07-14  1:36       ` David Lang
2022-07-14  5:46     ` Larry Press
2022-07-14  7:00       ` David Lang
2022-07-14 11:15         ` Mike Puchol
2022-07-14 11:32           ` Sebastian Moeller
2022-07-14 12:02             ` Mike Puchol
2022-07-14 12:34               ` Sebastian Moeller
2022-07-14 12:49                 ` Nitinder Mohan
2022-07-14 12:57                   ` Jared Mauch
2022-07-14 13:05                     ` Nitinder Mohan
2022-07-14 13:33                       ` Nitinder Mohan
2022-07-14 14:56                         ` Mike Puchol
2022-07-14 15:28                           ` Sebastian Moeller
2022-07-14 15:32                             ` Nathan Owens
2022-07-27 21:17           ` Dave Taht
2024-07-02 20:40 Dave Taht
2024-07-03  3:40 ` Ulrich Speidel
2024-07-03 17:21   ` Larry Press
2024-07-03  4:21 ` Marc Blanchet
2024-07-03  4:26   ` J Pan
2024-07-03 17:06   ` Larry Press
2024-07-03 22:06   ` Michael Richardson
2024-07-14 19:32     ` J Pan

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=20220713175957.5fc577a4@spidey.rellim.com \
    --to=gem@rellim.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