From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: Update | Starlink Beta
Date: Tue, 6 Apr 2021 07:50:37 -0700 [thread overview]
Message-ID: <CAA93jw7-D03x=C5Z+Hy=0cQU96fKBA-bZ+9_4cQf88ZasSx==g@mail.gmail.com> (raw)
In-Reply-To: <CANmPVK-wsLrn4bp+pJ8j4K-ZYxQfVYqDQSBPLPKoK02KXdHBow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3997 bytes --]
Send a resume to:
*starlinksoftwarejobs@spacex.com <starlinksoftwarejobs@spacex.com>*
If anyone here would like to apply. Got no idea what "dynamic frame
allocation" is, but they are still testing out as quite bloated....
---------- Forwarded message ---------
From: myfriendontheinside <myfriendontheinside@gmail.com>
Date: Mon, Apr 5, 2021 at 10:18 PM
Subject: Fwd: Update | Starlink Beta
To: Dave Taht <dave.taht@gmail.com>
Starlink update email
---------- Forwarded message ---------
From: Starlink <no-reply@starlink.com>
Date: Mon, Apr 5, 2021, 7:23 PM
Subject: Update | Starlink Beta
[image: Starlink Logo]
Throughout the beta program, customer feedback has helped drive some of our
most important changes to date as we continue to test and scale the network.
The Starlink team has implemented a number of improvements since our last
update. Below are some of the key highlights:
*Starlink Expansion*
Since rollout of initial U.S. service in October 2020, Starlink now offers
limited beta service in Canada, U.K., Germany and New Zealand. To date, we
have deposits from almost every country around the world; going forward,
our ability to expand service will be driven in large part by governments
granting us licensing internationally.
*Preventative Maintenance*
Recently some beta users saw short but more frequent outages, particularly
in the evening hours. This was caused by two main issues— preventive
maintenance on various ground gateways, coupled with a network logic bug
that intermittently caused some packet processing services to hang until
they were reset. The good news is fixes were implemented and users should
no longer see this particular issue.
Gateway Availability
As more users come online, the team is seeing an increase in surges of
activity, particularly during peak hours. The gateway infrastructure to
support these types of surges is in place, but we are awaiting final
regulatory approval to use all available channels. Near term fixes have
been implemented to facilitate better load balancing in the interim, and
this issue will fully resolve once all approvals are received.
*Dynamic Frame Allocation*
The Starlink software team recently rolled out our dynamic frame allocation
feature which dynamically allocates additional bandwidth to beta users
based on real time usage. This feature enables the network to better
balance load and deliver higher speeds to the user.
*Connecting to the Best Satellite*
Today, your Starlink speaks to a single satellite assigned to your terminal
for a particular period of time. In the future, if communication with your
assigned satellite is interrupted for any reason, your Starlink will
seamlessly switch to a different satellite, resulting in far fewer network
disruptions. There can only be one satellite connected to your Starlink at
any time, but this feature will allow for choice of the best satellite.
This feature will be available to most beta users in April and is expected
to deliver one of our most notable reliability improvements to date.
These upgrades are part of our overall effort to build a network that not
only reaches underserved users, but also performs significantly better than
traditional satellite internet.
To that end, the Starlink team is always looking for great software,
integration and network engineers. If you want to help us build the
internet in space, please send your resume to *starlinksoftwarejobs@spacex.com
<starlinksoftwarejobs@spacex.com>*.
Thank you for your feedback and continued support!
The Starlink Team
Space Exploration Technologies Corp | 1 Rocket Road, Hawthorne, CA 90250 |
Unsubscribe
Questions? See Starlink FAQs <https://www.starlink.com/faq>
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
[-- Attachment #2: Type: text/html, Size: 20087 bytes --]
parent reply other threads:[~2021-04-06 14:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANmPVK-wsLrn4bp+pJ8j4K-ZYxQfVYqDQSBPLPKoK02KXdHBow@mail.gmail.com>]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7-D03x=C5Z+Hy=0cQU96fKBA-bZ+9_4cQf88ZasSx==g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@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