From: David Lang <david@lang.hm>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] FCC changes for Starlink
Date: Fri, 9 Jan 2026 17:19:26 -0700 (MST) [thread overview]
Message-ID: <q0725pnr-0po3-99so-9279-15824814oon7@ynat.uz> (raw)
https://spaceflightnow.com/2026/01/08/live-coverage-spacex-to-launch-its-falcon-9-rocket-on-midday-starlink-mission-from-cape-canaveral/
approved another 7500 v2 satellites (many will be replacing v1 and v1.5
satellites)
approved lowering orbits (smaller beam footprint)
approved overlapping beams
This should improve available speeds over time. I'm especially going to be
interested in what happens with them now being allowed to have overlapping
beams.
David Lang
reply other threads:[~2026-01-10 0:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=q0725pnr-0po3-99so-9279-15824814oon7@ynat.uz \
--to=david@lang.hm \
--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