From: Inemesit Affia <inemesitaffia@gmail.com>
Cc: Michael Kan <michael_kan@pcmag.com>, starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP)
Date: Thu, 11 Dec 2025 02:40:20 +0100 (GMT+01:00) [thread overview]
Message-ID: <0ec7090b-4c44-4c17-a784-ed4107ab5e40@gmail.com> (raw)
In-Reply-To: <554694qo-477p-2915-48qs-qq8qr3413941@ynat.uz>
An image from AWS Invent.
They expect sub 46-50 ms at launch.
None of us live in a POP/NAP but I've seen Speedtest pings on Starlink sub 17ms so..
I wonder what OneWeb is capable of. I'm seeing 45ms as best case for them in the field.
Dec 9, 2025 12:33:51 AM David Lang <david@lang.hm>:
> Michael Kan wrote:
>
>> latency for Amazon Leo? https://www.youtube.com/watch?v=nZCx612z930
>
> Until they have the system operational, be very leery about bandwidth and latency claims.
>
> Remember that Starlink had to do-bloat things to make their user-experienced latency line up with their early lab tests.
>
> David Lang
next prev parent reply other threads:[~2025-12-11 1:40 UTC|newest]
Thread overview: 26+ 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-11 1:40 ` Inemesit Affia [this message]
2025-12-12 14:12 ` [Starlink] Wi-Fi Alliance’s QoS Management Specification Release 2 (R2) what's this new standard about? Inemesit Affia
2025-12-09 1:26 ` [Starlink] Re: Amazon Leo announcing up to 1 Gbps (DOWN) and 400 Mbps (UP) 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
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=0ec7090b-4c44-4c17-a784-ed4107ab5e40@gmail.com \
--to=inemesitaffia@gmail.com \
--cc=michael_kan@pcmag.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