Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>,
	 starlink@lists.bufferbloat.net
Subject: Re: [Starlink] a puzzling starlink uplink trace
Date: Thu, 31 Aug 2023 06:54:08 -0700 (PDT)	[thread overview]
Message-ID: <q0711q39-qrpr-n385-p750-q83r10op3792@ynat.uz> (raw)
In-Reply-To: <CAA93jw4mDaNgZ8QDwxhaxafX66wRDwEVWxZQnGLh3-uSUEsYig@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]

On Thu, 31 Aug 2023, Dave Taht via Starlink wrote:

> I like the idea of starlink finding some way to leverage satellites
> moving into the right orbits. (the timestamp of this trace was
> 2023-08-27 06:59:35 UTC and I am in half moon bay, ca) This would
> imply that they can transmit data at full thrust, and also, perhaps,
> VLEO (I am not sure if that is an established acronym - very low earth
> orbit operations) -  feasible. Dropping the things even lower, making
> the shell more aerodynamic, and burning fuel to stay there might well
> be an interesting option. It seems to me the current altitude(s) are
> pretty conservative and given the fuel consumption reported on the
> maneuvering side, they can last at 530km much longer than 5 years, and
> with the pace of technology and launch rates, moving them lower would
> be a huge win for bandwidth and latency.

It's not just a fuel issue, it's a matter of their assigned orbits (not getting 
in the way of other satellites)

Here are the altitudes they are authorized to operate in and the current count 
per orbit (from wikipedia so I don't know how up to date they are given the 
frequent launches, but I suspect pretty close)

Altitude	Authorized	Active	Decaying/deorbited
550 km		1584[313]	1457	268
570 km		720		404	4
560 km		348		233	10
540 km		1584		1567	70
560 km		172
335.9 km	2493
340.8 km	2478
345.6 km	2547

it's not a matter of being able to operate while under thrust from a technical 
point of view, it's a matter of them being authorized by the FCC to do so and 
anti-collision rules.

the US considers 'space' to start at a round number of 50 miles (just over 
80km), the metric world picked 100km (another nice round number, just over 62 
miles), so any satellite at 70km is technically not 'in space' and will die in a 
few orbits

David Lang

[-- Attachment #2: Type: image/png, Size: 368976 bytes --]

[-- Attachment #3: Type: application/gzip, Size: 196415 bytes --]

[-- Attachment #4: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2023-08-31 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 18:07 Dave Taht
2023-08-30 19:43 ` Sebastian Moeller
2023-08-31 13:42   ` Dave Taht
2023-08-31 14:31     ` Sebastian Moeller
2023-08-31  8:56 ` Alexandre Petrescu
2023-08-31  9:13   ` Alexandre Petrescu
2023-08-31 11:43     ` David Lang
2023-08-31 13:36     ` Dave Taht
2023-08-31 13:54       ` David Lang [this message]
2023-09-15 11:17       ` 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=q0711q39-qrpr-n385-p750-q83r10op3792@ynat.uz \
    --to=david@lang.hm \
    --cc=alexandre.petrescu@gmail.com \
    --cc=dave.taht@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