From: Hayden Simon <h@uber.nz>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] The curious case of the missing Starlink spectrum licences
Date: Mon, 13 Nov 2023 01:57:45 +0000 [thread overview]
Message-ID: <TYZPR03MB828289BE95C94A597B2B3232A8B3A@TYZPR03MB8282.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <99ba9654-fd43-47a3-8388-f0c78c4b94ab@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
I asked someone who would know about such things; and he said:
“from the looks of it, most of the licences expired. Either because they weren't being used, or because Starlink forgot to pay for them, or because the RRF is such a giant cluster it ate all their licenses. (this would not be unusual)
I can see eleventy billion expired licenses in there and at least enough to keep their business going that were planned in October and are in "awaiting payment to grant" state now.
“
HAYDEN SIMON
UBER GROUP LIMITED
MANAGING DIRECTOR
E: h@uber.nz
M: 021 0707 014
W: www.uber.nz
53 PORT ROAD | PO BOX 5083 | WHANGAREI | NEW ZEALAND
From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Ulrich Speidel via Starlink
Sent: Monday, November 13, 2023 2:46 PM
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] The curious case of the missing Starlink spectrum licences
Blank.
On 13/11/2023 2:29 pm, Inemesit Affia via Starlink wrote:
Can you look for tibro or oneweb?
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net<mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz<mailto:u.speidel@auckland.ac.nz>
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #2: Type: text/html, Size: 10995 bytes --]
next prev parent reply other threads:[~2023-11-13 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 1:27 Ulrich Speidel
2023-11-13 1:29 ` Inemesit Affia
2023-11-13 1:46 ` Ulrich Speidel
2023-11-13 1:57 ` Hayden Simon [this message]
2023-11-13 2:17 ` Ulrich Speidel
2023-11-13 2:21 ` Hayden Simon
2023-11-13 1:34 ` Inemesit Affia
2023-11-13 2:07 ` Ulrich Speidel
2023-11-14 11:24 ` Alexandre Petrescu
2023-11-15 6:59 ` Inemesit Affia
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=TYZPR03MB828289BE95C94A597B2B3232A8B3A@TYZPR03MB8282.apcprd03.prod.outlook.com \
--to=h@uber.nz \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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