Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Larry Press <lpress@csudh.edu>
Cc: "Gary E. Miller" <gem@rellim.com>, David Lang <david@lang.hm>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink at sea
Date: Thu, 14 Jul 2022 00:00:48 -0700 (PDT)	[thread overview]
Message-ID: <92n4s129-6r15-7q75-7293-qpo73q298srn@ynat.uz> (raw)
In-Reply-To: <BYAPR03MB38633C850C22F1ACCB56DF64C2889@BYAPR03MB3863.namprd03.prod.outlook.com>

On Thu, 14 Jul 2022, Larry Press wrote:

> <$50k/month (for all their boats)
>
> Do they have ten ships?

I know of 7 off the top of my head, the three drone ships, the multi-purpose 
recovery ships bob and doug, they got a couple more recently(named for females, 
don't remember the names reliably), all those recovery ships on the east coast, 
so they probably have one or two on the west coast, and I don't think that 
includes the dragon recovery craft.

> >$150k/month with much better service
>
> Is that for uncapped service from a GEO? What speeds do they get for that? Do GEO folks like Hughes offer SLAs to business customers?

that was for 25G of bandwidth from the post I saw mentioned, they didn't mention 
the speed (but they did show the difference in video quality from the barges 
between the old and new)

David Lang

> Does SES offer marine connectivity?
>
> Russian oligarchs will be early customers.
>
> Larry Press
>
> ________________________________
> From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of David Lang via Starlink <starlink@lists.bufferbloat.net>
> Sent: Wednesday, July 13, 2022 5:40 PM
> To: Gary E. Miller <gem@rellim.com>
> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] starlink at sea
>
> 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)
>
> 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)
>
> David Lang
>
>  On Wed, 13 Jul 2022, Gary E. Miller via Starlink wrote:
>
>> Date: Wed, 13 Jul 2022 17:36:02 -0700
>> From: Gary E. Miller via Starlink <starlink@lists.bufferbloat.net>
>> Reply-To: Gary E. Miller <gem@rellim.com>
>> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
>> Subject: Re: [Starlink] starlink at sea
>>
>> Yo Dave!
>>
>> On Wed, 13 Jul 2022 17:20:43 -0700
>> Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
>>
>>> https://urldefense.com/v3/__https://www.royalcaribbeanblog.com/2022/06/28/i-tried-elon-musks-starlink-internet-royal-caribbean-cruise-ship__;!!P7nkOOY!rxlTbVxEkw-MFoqu8DRa85IzMzIO1zBngo2MWxU3hZC2uf--DSi39Jg1_QDzFZyl3ShxZFNhM0oEQFMaJMhpU32Mkw$
>>
>>
>> Did you notice the eye popping cost?
>>
>> https://urldefense.com/v3/__https://www.starlink.com/maritime__;!!P7nkOOY!rxlTbVxEkw-MFoqu8DRa85IzMzIO1zBngo2MWxU3hZC2uf--DSi39Jg1_QDzFZyl3ShxZFNhM0oEQFMaJMgLmSbzsw$
>>
>> "High-speed, low-latency internet with up to 350 Mbps download while at
>> sea. $5,000/mo with a one-time hardware cost of $10,000 for two high
>> performance terminals."
>>
>> I know a bunch of yacthies that have been waiting for this, but are
>> now
>> disappointed.
>>
>> 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
>>
>

  reply	other threads:[~2022-07-14  7: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
2022-07-14  1:36       ` David Lang
2022-07-14  5:46     ` Larry Press
2022-07-14  7:00       ` David Lang [this message]
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=92n4s129-6r15-7q75-7293-qpo73q298srn@ynat.uz \
    --to=david@lang.hm \
    --cc=gem@rellim.com \
    --cc=lpress@csudh.edu \
    --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