From: Daniel AJ Sokolov <daniel@falco.ca>
To: Benjamin Henrion via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] No RDOF-Funds for Starlink
Date: Mon, 22 Aug 2022 12:47:33 -0700 [thread overview]
Message-ID: <f9e5aed5-ce92-6289-3e03-9f2f7253b77b@falco.ca> (raw)
Hello,
Starlink was posed to receive 900 million USD from the FCC's Rural
Digital Opportunity Fund to bring broadband internet to unserviced areas
of the United States - until it wasn't.
Earlier this month, the FCC decided NOT to give Starlink any of the 900
million dollars after all.
https://docs.fcc.gov/public/attachments/DA-22-848A1.pdf
"The Bureau has determined that, based on the totality of the long-form
applications, the expansive service areas reflected in their winning
bids, and their inadequate responses to the Bureau’s follow-up
questions, LTD and Starlink are not reasonably capable of complying with
the Commission’s requirements. The Commission has an obligation to
protect our limited Universal Service Funds and to avoid extensive
delays in providing needed service to rural areas, including by avoiding
subsidizing risky proposals that promise faster speeds than they can
deliver, and/or propose deployment plans that are not realistic or that
are predicated on aggressive assumptions and predictions. We observe
that Ookla data reported as of July 31, 2022 indicate that Starlink’s
speeds have been declining from the last quarter of 2021 to the second
quarter of 2022, including upload speeds that are falling well below 20
Mbps. Accordingly, we deny LTD’s and Starlink’s long-form applications,
and both are in default on all winning bids (...)"
(For purposes of Starlink, you can ignore the parts about LTD Broadband.)
Also note this 2021 study showing Starlink's impending capacity crunch:
We forecast a capacity shortfall in 2028:
- 56% of RDOF subscribers are congested in a forecasted
low demand scenario
- More locations will be impacted if RDOF usage is higher,
or SpaceX launches fewer satellites by 2028
. RDOF service could be significantly worse if Starlink
capacity is allocated to non-RDOF use cases
https://www.ntca.org/sites/default/files/documents/2021-02/FBA_LEO_RDOF_Assessment_Final_Report_20210208.pdf
FYI
Daniel
next reply other threads:[~2022-08-22 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:47 Daniel AJ Sokolov [this message]
2022-08-22 20:10 ` warren ponder
2022-08-22 20:28 ` David Lang
2022-08-22 20:40 ` warren ponder
2022-08-22 22:16 ` Daniel AJ Sokolov
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=f9e5aed5-ce92-6289-3e03-9f2f7253b77b@falco.ca \
--to=daniel@falco.ca \
--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