From: Joe Hamelin <nethead@gmail.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Inside Amazon’s Effort to Challenge Musk’s Starlink Internet Business
Date: Wed, 20 Dec 2023 14:21:41 -0800 [thread overview]
Message-ID: <CAO0-hXYdANc8a0x+WrVQEBC=PjXBP10Naq3mewpXHSNzL_O_5w@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOgOq_f8FugyE+E3VbOQ5FyRQkntdL5b50h23pof3zd+=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
As a "systems engineer" working for a global aerospace company with
multiple facilities, I think a lot of this is so Amazon can get rid of
having to deal with local network carriers. Even with our 100 or so
locations not a week goes by that there isn't some connection issue caused
by an external vendor. This chews up a lot of time and money. Upgrades
take forever and contracts are hard to get out of. I can't imagine what
it's like at Amazon these days. I used to be a senior network engineer at
Amazon back 23 years ago (I still cry myself to sleep for not vesting those
9000 shares) and even then we spent a lot of time and effort on this
issue. It will be so much simpler for Amazon to have their own LEO network
for all their facilities. Kuiper is mainly for internal use, then they'll
sell the excess, just like they did with AWS and S3.
On Wed, Dec 20, 2023 at 10:21 AM Frantisek Borsik via Starlink <
starlink@lists.bufferbloat.net> wrote:
> https://archive.ph/ZaETA#selection-4555.0-4555.69
>
> Paywalled:
>
> https://www.bloomberg.com/news/features/2023-12-18/amazon-s-project-kuiper-to-challenge-elon-musk-s-starlink-satellite-internet
>
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
[-- Attachment #2: Type: text/html, Size: 3640 bytes --]
prev parent reply other threads:[~2023-12-20 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 18:20 Frantisek Borsik
2023-12-20 22:21 ` Joe Hamelin [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='CAO0-hXYdANc8a0x+WrVQEBC=PjXBP10Naq3mewpXHSNzL_O_5w@mail.gmail.com' \
--to=nethead@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=joe@hamelin.us \
--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