Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Michael Richardson <mcr@sandelman.ca>,
	"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Starlink D2D observation - fwiw
Date: Fri, 27 Feb 2026 13:08:05 +1300	[thread overview]
Message-ID: <c05d44bc-8693-4635-9c2d-96ceb20acee0@auckland.ac.nz> (raw)
In-Reply-To: <10005.1772147265@obiwan.sandelman.ca>

On 27/02/2026 12:07 pm, Michael Richardson wrote:
> Ulrich Speidel via Starlink<starlink@lists.bufferbloat.net> wrote:
>      > As expected, coverage was much better outdoors, although it seemed to
>      > occasionally manage to pick up the network through a window as well. Sending
>      > text from indoors didn't work for me at all. But having that option was nice.
>
> In the 2G days, there were actually useful passive reflectors/antenna that
> one could put in a window to "boost" the signal.  (It always seemed like total
> black magic to me)
> I had one, it improved things for reception in my basement office, then 3G
> was no problem for awhile, and then it became a problem again.
> (My did-not-answer call forward goes to a voip service that relays to my
> * and Cisco desktop phone via IP...)
>
> I wonder if such a thing could exist for the satellite link.  If so, such
> remote cabins could just have some.
> As you said, it took some minutes to work, and I wonder how much of that is
> waiting for the right coverage window with the overhead things.
All good questions. With 4G and 5G, there's a lot more to a signal than 
in 2G, and anything that meddles with phase and direction is potentially 
problematic.
> Glad you found the tap on the water tanks.
It wasn't actually on any of the tanks - just below the top of one in 
terms of level, and the pump it was connected through must have stopped 
in a state in which it permitted flow of a couple of litres a minute.
> After August 2003 blackout, multiple buildings in Ottawa discovered that
> one needed electricity in order to pump the diesel to the backup generator's
> tanks, which were often located on the roof.  Nobody had considered that
> power might be out longer than the tanks had fuel for.
Secondary issues like these are common unfortunately.
>      > One road opened again the next morning, and the power came back on later that
>      > day, along with the 4G coverage.
>
> In the interlude between the storm and the roads opening, was it sunny?
It became sunny, yes, but in terms of using something solar PV that day 
you would have had a hard time on the first day after the storm. I run 
my house (including a granny flat) on grid-connected PV with battery 
backup, and this is what the weather system looked like on our PV system 
monitor two days earlier when it passed over Auckland:

Basically it spent a lot of time re-charging the battery (green solid 
area). That was before the weather system went out into the Pacific 
southeast of NZ and "refueled". So what you see above is an optimistic view.

In comparison, this is what this Tuesday looked like, when it was mostly 
nice and sunny here (note the different kW scale on the left):

It's still summer here, and only a small part of the yield went into 
battery re-charge - the rest mostly powered our neighbours. Note the 
steep drop after the battery reaches maximum SOC isn't weather related, 
it's regulatory: We're only allowed 5 kW of AC generation per phase. 
That's meant to change but our local lines company is not quite there yet.

> Was the hiking good?

-- 
****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)

The University of Auckland
u.speidel@auckland.ac.nz 
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************



  parent reply	other threads:[~2026-02-27  0:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  3:42 [Starlink] Starlink D2D observation - fwiw Ulrich Speidel
2026-02-26  3:54 ` [Starlink] " J Pan
2026-02-26  4:19   ` Ulrich Speidel
     [not found] ` <10005.1772147265@obiwan.sandelman.ca>
2026-02-27  0:08   ` Ulrich Speidel [this message]
     [not found]     ` <24488.1772211381@obiwan.sandelman.ca>
2026-02-28  2:25       ` Ulrich Speidel
2026-02-28  6:17         ` J Pan
2026-02-28  8:09           ` Ulrich Speidel

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=c05d44bc-8693-4635-9c2d-96ceb20acee0@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --cc=mcr@sandelman.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