Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Portability Now Available (fwd)
Date: Thu, 5 May 2022 02:21:21 -0700 (PDT)	[thread overview]
Message-ID: <6p4934rq-30ns-9486-5srs-o45r7rornor9@ynat.uz> (raw)
In-Reply-To: <77f03647-c1af-00c3-21b6-19fc62a81e44@auckland.ac.nz>

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

remember that starlink is getting coverage from many satellites as they come 
over, it's not like geostationary satellites that can aim specific antennas at 
specific locations (i.e. 'spotbeams' are not a thing)

In a week or two I'm going to take my dish out and drive around for a few hours 
(just received the inverter I ordered, now to convert the plugs...)

I expect the waitlist is a combination of two things.

1. the number of subscribers already in the area
2. supply availability (I expect this is why Ukraine is a waitlist, they have 
supplied dishes to the government, but if you try to order one yourself, you 
would have to wait)

David Lang

On Thu, 5 May 2022, Ulrich Speidel wrote:

> Date: Thu, 5 May 2022 19:40:01 +1200
> From: Ulrich Speidel <u.speidel@auckland.ac.nz>
> To: starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] Portability Now Available (fwd)
> 
> Cool. Very interesting! That's one pile of information all of a sudden. They 
> could do that more often IMHO.
>
> Nothing like official confirmation that the tropics are an almost 
> Starlink-free zone, and that places reasonably away from the 53rd parallels 
> are secondary service zones. They forgot their 50-odd terminals in Tonga (I 
> heard yesterday about someone in the northern islands who brought a dishy 
> from overseas and found it didn't work... obviously believed the headlines... 
> sigh).
>
> Also interesting that there seems to be, finally, some sort of disclosure on 
> cell size. Someone will need to explain to me why there are waitlist areas in 
> the Auckland area surrounded by full service. The areas concerned are rural, 
> which you'd think they'd want to service with priority over our 
> well-connected CBD... Too many subscribers there already, or not enough to 
> warrant a spot beam? Similar soft spots near Sydney, holes in Foveaux Strait, 
> the Hauraki Gulf, southeast of Murray Bridge in South Australia, southern 
> Chile, ... What do I read into this? Two-fold: Where it's near 53 degrees, 
> they're probably oversubscribed or lack terminal supply, or both. Where it's 
> well away from 53 degrees, I'd guess they probably just lack satellite 
> capacity full stop.
>
> Ukraine is waitlisted...? But wait - didn't Starlink just take over the 
> Internet there? Interesting also that one of the waitlist / no service areas 
> in Germany is right where they had the floods & where Starlink got deployed 
> very publicly with (I understand) some success. Did the locals hang on to the 
> emergency dishys and does this now saturate the network there? And what did 
> the Greeks do to be all waitlisted?
>
> So what happens if you roam from a place with availability into a place with 
> "waitlist" status? Anyone with a dishy up for a road trip with a story to 
> tell?
>
> $25/month sounds steep but is probably modest in comparison to the roaming 
> charges that some cellular providers charge.
>
> On 5/05/2022 7:00 pm, David Lang wrote:
>> received this Wednesday evening.
>> Makes sense,
>> 
>> David Lang
>> 
>> ---------- Forwarded message ----------
>> Portability Now Available
>> 
>> Starlink is excited to announce Portability as an add-on feature for all 
>> Starlink customers. Portability enables customers to temporarily move their 
>> Starlink to new locations and receive high-speed internet anywhere where 
>> Starlink provides active coverage within the same continent. To see active 
>> coverage areas, please view the Starlink Availability Map ( 
>> http://www.starlink.com/map <http://www.starlink.com/map> ).
>> 
>> You can enable Portability for $25/month on your account page ( 
>> https://starlink.com/account <https://starlink.com/account> ). Once 
>> enabled, Portability will take effect immediately, and you can disable 
>> Portability from your account page at any time.
>> 
>> To learn more about Starlink Portability, please read our FAQ page ( 
>> http://www.starlink.com/faq <http://www.starlink.com/faq> ).
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink 
>> <https://lists.bufferbloat.net/listinfo/starlink>
>
>

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

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

  reply	other threads:[~2022-05-05  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  7:00 David Lang
2022-05-05  7:40 ` Ulrich Speidel
2022-05-05  9:21   ` David Lang [this message]
2022-05-05 23:46     ` Larry Press
2022-05-06  2:41       ` Mike Puchol
2022-05-06  3:11         ` Dave Taht
2022-05-06  9:17           ` Mike Puchol
2022-05-06  3:04       ` Bruce Perens

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=6p4934rq-30ns-9486-5srs-o45r7rornor9@ynat.uz \
    --to=david@lang.hm \
    --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