Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: Inemesit Affia <inemesitaffia@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure
Date: Mon, 24 Jun 2024 07:42:00 -0700	[thread overview]
Message-ID: <CAHn=e4iDNpha=nOh3_uJapeQrmT1OJtw-Brt0AO1PxPtDDXATw@mail.gmail.com> (raw)
In-Reply-To: <CAJEhh73M-K5yhoYqMzohtgTk-Jxts3G-QuVJb7Meww+DvGCPXw@mail.gmail.com>

can you give the reference to the complaint so we can dive into it a
bit? once the user packet reaches the satellite, it needs to get to
the ground (sooner than later according to starlink's current
practice), which may run into the same fiber to tunnel the packet from
the landing ground station to the user's home pop. once at the pop,
most starlink pop's now have at least two neighbor pop's, so
theoretically, starlink has the capability to route packets to a
different landing ground station through inter-sat links and another
pop, if it can arrange so properly
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan

On Mon, Jun 24, 2024 at 3:40 AM Inemesit Affia via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> I don't live in Jamaica but I just saw a user complain his service goes out at the same time his local provider does.
>
> The provider is Flow Jamaica and they seem to get service via C&W Caribbean according to another poster.
>
> Service going out together likely means there's shared infrastructure. And buying Starlink as backup and having it fail hard without rerouting several times in a row is below expectations.
>
> There's another provider in Jamaica. Digicel that seems to have separate infrastructure but that might not be value for money to have alternative connectivity.
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2024-06-24 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 17:31 [Starlink] I still dream of an tiny on-orbit repair and inspection robot Dave Taht
2024-06-19 18:44 ` Kenneth Porter
2024-06-24 10:39 ` [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure Inemesit Affia
2024-06-24 14:42   ` J Pan [this message]
2024-06-24 22:19     ` Ulrich Speidel
2024-06-25  3:42       ` David Lang
2024-06-25  4:34         ` Ulrich Speidel
2024-06-25  5:37         ` Sebastian Moeller
2024-06-25  6:54           ` Gert Doering
2024-06-25  7:26             ` Sebastian Moeller
2024-06-25 19:07       ` J Pan

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='CAHn=e4iDNpha=nOh3_uJapeQrmT1OJtw-Brt0AO1PxPtDDXATw@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=inemesitaffia@gmail.com \
    --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