Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure
Date: Tue, 25 Jun 2024 16:34:45 +1200	[thread overview]
Message-ID: <43311b09-e739-4bae-8724-0783657a263c@auckland.ac.nz> (raw)
In-Reply-To: <1p491rss-599n-n211-op44-1npn41p68005@ynat.uz>

On 25/06/2024 3:42 pm, David Lang wrote:
> Ulrich Speidel wrote:
>
>> This can also lead to weird effects globally. For example, much of 
>> the traffic between Japan and New Zealand *could* in principle 
>> trundle down to Guam and from there to Sydney and then to Auckland. 
>> Which would be kind of shortest path. And occasionally it does. But 
>> just as often, you see it crossing the Pacific to the US West Coast 
>> (or from Guam to Hawaii) and from there back to New Zealand. Why? 
>> Good question. Was it because US backhaul carriers were cheaper for a 
>> while with the US dollar being soft and the Australian / NZ 
>> currencies surging in comparison? Were there government incentives 
>> for carriers to let traffic run through US territory for intelligence 
>> access (if so, the NSA would have to fear
>
> It's important to realize that BGP doesn't know how long any link is. 
> it defines 'closest' by the number of hops.
>
> so Japan -> LA -> Auckland is 'shorter' than Japan -> Guam -> Sydnes 
> -> Auckland even though it's much longer, probably through more 
> congested links, and higher latency.

Indeed, but that's assuming that (a) there are hops (just because two 
cables land on the same island, it doesn't mean that they are connected 
there) and (b) that pure BGP hop count metric isn't overruled by the 
sending ISPs or someone along the way, as it often is. E.g., Hawaii to 
NZ is just one cable "hop", but traffic from the University of Hawaii to 
Auckland also used to go via the US West Coast for a long time 
(someone's fixed it now) as they didn't peer with Southern Cross.

-- 

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




  reply	other threads:[~2024-06-25  4:34 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
2024-06-24 22:19     ` Ulrich Speidel
2024-06-25  3:42       ` David Lang
2024-06-25  4:34         ` Ulrich Speidel [this message]
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=43311b09-e739-4bae-8724-0783657a263c@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --cc=david@lang.hm \
    --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