Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>,
	"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] An update on Tonga
Date: Sun, 01 Sep 2024 22:26:40 -0400	[thread overview]
Message-ID: <22997.1725244000@obiwan.sandelman.ca> (raw)
In-Reply-To: <57a985b7-84f5-4723-9a6c-68343d2b4c30@auckland.ac.nz>

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


Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
    > There were quite a few folk on this list a couple of years back who were
    > interested in what was happening to Internet in Tonga after the big volcanic
    > eruption there. I'm not sure where I left off.

Thank you for the update.

    > Spare cable was ordered from France and was installed middle of 2023,
    > restoring the TDCE to service.

How long was the outage caused by lack of spare cable?
Is there an effort to keep more spare cable closer?

    > location. The operators were well aware of the risk, however re-routing the
    > cable would have required it to be lengthened, with the need to insert
    > repeaters, upgrade terminal equipment, and conduct a new marine survey, which
    > would have meant further delays.

Is this on the long-term plan?

    > On 26 August 2024, 11:29 am, a M6.9 quake struck in the area at a depth of
    > about 106 km. Our Science building in Auckland has a "citizen science"
    > seismograph with a big display in its foyer, and my student and I noticed the

That's pretty neat.

    > Meanwhile, Starlink has been licensed to operate commercially in Tonga. For
    > many Pacific Island countries, this is a double-edged sword: On the one hand,
    > this provides short-term relief, on the other hand, it deprives local ISPs of
    > customers and therefore impacts on aspirations to achieve cable connectivity
    > which could provide more bandwidth in the medium term.

Yeah.  I see those edges.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  parent reply	other threads:[~2024-09-02  2:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31  7:35 Ulrich Speidel
2024-09-01 22:17 ` Dave Taht
2024-09-02  9:36   ` Ulrich Speidel
2024-09-02  2:26 ` Michael Richardson [this message]
2024-09-02 10:30   ` Ulrich Speidel
2024-09-10 23:42 ` 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=22997.1725244000@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --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