Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] First tests of the Starlink REV4 (aka gen3)
Date: Wed, 24 Jan 2024 13:37:50 +0100	[thread overview]
Message-ID: <7849c840-fe56-4867-91bd-613c3d2b5f42@gmail.com> (raw)
In-Reply-To: <10cabe9d-0c0f-4adc-baf7-0ba487867352@olegkutkov.me>

Thanks for the tests!

The dl/ul speeds 300/15 mbit/s are impressive.

At video pointer 5:53 the reported Ping ?/dl/ul 88/204/121 ms and Jitter 
9.2 ms seem interesting.

     ==> I am not sure which of the two (ping or jitter) you name 'latency'?

     ==> I am not sure why the dl (download) ping ms is higher than the ul.

     ==> I don't know what is the first ('?') parameter reported as 88ms 
for Ping?

I wonder whether the DHCPv6-PD is still supported by REV4 and whether 
the allocated prefix is still a non-/64 (i.e. a /56 delivered by 
DHCPv6-PD reported earlier on this email list by Steven on Dec. 12, 2023)?

Alex

Le 23/01/2024 à 10:07, Oleg Kutkov via Starlink a écrit :
> I conducted the initial comparative tests of the new terminal in 
> Ukraine. I guess it's not a really "legal" because the new terminal is 
> not certified and not selling outside the US for the moment. But who 
> cares.
>
> Here's a video: https://youtu.be/hWPMpJrjd1g
>
> I will try to do more technical tests next week. There will be a new 
> video.
>

  reply	other threads:[~2024-01-24 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  9:07 Oleg Kutkov
2024-01-24 12:37 ` Alexandre Petrescu [this message]
2024-01-24 22:47   ` Oleg Kutkov
2024-01-24 23:40     ` Jonathan Bennett
2024-01-24 23:50       ` Oleg Kutkov
2024-01-25  1:29         ` David Lang
2024-01-25  1:54   ` Ulrich Speidel
2024-02-22 12:18     ` Alexandre Petrescu

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=7849c840-fe56-4867-91bd-613c3d2b5f42@gmail.com \
    --to=alexandre.petrescu@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