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.bor...@gmail.com > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > -- -- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
_______________________________________________ Starlink mailing list Starlink@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/starlink
