Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink in Cyclone Gabrielle in NZ
Date: Tue, 14 Feb 2023 20:41:48 +1300	[thread overview]
Message-ID: <2b8d1b20-45f1-91a3-e990-5fb15d92f702@auckland.ac.nz> (raw)

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

After missing the opportunity to "soak test" our Starlink RV kit in the 
Auckland floods the other week, Cyclone Gabrielle (which is still 
noticeably upon us with very strong winds) was an opportunity I couldn't 
let pass. I've learned a lot over the last day or so, and it's been 
interesting to say the least.

So I put Dishy on our deck (slightly obscured view of the southern sky - 
the only bit of sky it will voluntarily look at for any length of time 
here in NZ) and tied it down on my painter's trestle with a few cable 
ties - so far it hasn't blown away.

I set up a ping series with 86400 large packets (1448 bytes to mimic 
you-know-what) to one of our uni machines to last for a day, starting 
just before the worst rain was forecast. I also put a beaker down next 
to it for some rainfall measurements - it collected 152 mm (~6") over 
the duration of the ping experiment. Not as bad as the deluge by a far 
shot but still, decent rain. Plus a lot of other areas got heaps more, 
and with Starlink, gateway and fellow users taking on water also impact 
on what you can do.

I also ran a few speedtest.net tests to a server at a local ISP at 
different times during the rain yesterday afternoon and last night.

Note I used the Starlink Ethernet adapter for this, not the WiFi from 
the router.

Here is what I got in terms of average and minimum RTTs and packet loss 
over a 60 s interval. Times approximate in local time:

   Note:

  * High minimum RTTs to start with (higher than for the speedtest.net
    tests, possibly because the packets are larger, possibly because
    Starlink games speedtest.net, possibly because of congestion thanks
    to everyone having been told to work from home that day and schools
    closing).
  * Noticeable jumps in RTT at around 9:30 pm and just before midnight,
    and then again at around 3:30 and 4:45 am and some time before 7 am.
    There were A LOT of power outages - not at our place (and we're
    USP'd with a 10 kWh solar battery anyway) but around ALL three
    Starlink gateways around the larger Auckland region (Clevedon, Te
    Hana and Puwera). I'm unsure whether it's a result of a large number
    of lifestyle block belters (the only serious Starlink customer group
    around here) losing power and thus freeing up capacity, or whether
    it's some change in the gateway arrangements.
  * Longest continuous ping fail: 22s
  * Packet loss appears elevated during the height of the rain. Rain fade?

Speedtest.net downloads didn't hit or exceed the 100 Mb/s mark until 
about 11 pm, and some runs yielded as little as 6.5 Mb/s down and 1.49 
Mb/s up. Average down was all over the place, average up typically in 
the mid single digits.

On the pro side, Starlink basically remained usable throughout, 
certainly for someone wanting to follow what was happening.

-- 
****************************************************************
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/
****************************************************************



[-- Attachment #2.1: Type: text/html, Size: 4082 bytes --]

[-- Attachment #2.2: gabrielle_rtt_pl.png --]
[-- Type: image/png, Size: 23782 bytes --]

                 reply	other threads:[~2023-02-14  7:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2b8d1b20-45f1-91a3-e990-5fb15d92f702@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --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