From: Joe Hamelin <nethead@gmail.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Nick Matthews <matthnick@gmail.com>,
Inemesit Affia <inemesitaffia@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP)
Date: Tue, 9 Dec 2025 17:45:18 -0800 [thread overview]
Message-ID: <CAO0-hXb+rAoRw7xSWOndbsOCBnfbVatupHcq3U1cotzd6s24JA@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOjNfvSOYWX1QDOuNfEuzwatwK-JyofO=+JbPrG1AmFzhg@mail.gmail.com>
Back 25 years ago I was a Sr. Network Eng. at Amazon. I think I know where
they are going with this project.
Even back then (when bringing up an OC-3 Internet circuit was still a big
deal) just keeping all the connections to all the sites took a lot of
networking's time. I can't imagine what it's like now.
Amazon built this as the only practical solution to their last mile
issues. Just pop a dish on a fulfillment center's roof and be done with
it. No more pesky LECs and CLECs to deal with.
Just like S3 and AWS, it started as an effective use of internal resources
but then grew into a valuable product.
This will be interesting to watch, time to order some popcorn (on Amazon,
of course.)
--
Joe Hamelin, W7COM, Portland, OR, +1 360 474 7474
next prev parent reply other threads:[~2025-12-10 1:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 15:36 [Starlink] Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP) Frantisek Borsik
2025-12-06 16:36 ` [Starlink] " J Pan
2025-12-06 23:58 ` David Lang
2025-12-07 0:02 ` Inemesit Affia
2025-12-07 0:08 ` David Lang
2025-12-08 4:31 ` Inemesit Affia
[not found] ` <5098.1765221714@obiwan.sandelman.ca>
2025-12-08 20:57 ` David Lang
[not found] ` <2609.1765228007@obiwan.sandelman.ca>
2025-12-08 21:15 ` David Lang
2025-12-08 21:22 ` Michael Kan
2025-12-08 23:19 ` Inemesit Affia
2025-12-08 23:20 ` Inemesit Affia
2025-12-08 23:33 ` David Lang
2025-12-09 1:26 ` David Collier-Brown
2025-12-09 7:49 ` Frantisek Borsik
2025-12-09 8:11 ` Inemesit Affia
2025-12-09 8:23 ` Frantisek Borsik
2025-12-09 8:21 ` Inemesit Affia
2025-12-09 8:29 ` Inemesit Affia
2025-12-09 21:53 ` Frantisek Borsik
2025-12-10 1:06 ` Nick Matthews
2025-12-10 1:24 ` Frantisek Borsik
2025-12-10 1:45 ` Joe Hamelin [this message]
2025-12-09 13:23 ` Livingood, Jason
2025-12-09 21:33 ` David Lang
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-hXb+rAoRw7xSWOndbsOCBnfbVatupHcq3U1cotzd6s24JA@mail.gmail.com \
--to=nethead@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=inemesitaffia@gmail.com \
--cc=joe@hamelin.us \
--cc=matthnick@gmail.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