Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>,
	David Lang via Starlink <starlink@lists.bufferbloat.net>,
	Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure
Date: Tue, 25 Jun 2024 07:37:40 +0200	[thread overview]
Message-ID: <974AF92C-907B-43A3-AC41-449FBAA5EFAE@gmx.de> (raw)
In-Reply-To: <1p491rss-599n-n211-op44-1npn41p68005@ynat.uz>

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

My understanding is routing mostly follows the path of least cost... and is more complex then BGP makes it look, if two ASs have multiple handover points one still needs to pick one for each flow... and even for a simple route between two AS the forward and reverse path might use different hand-over points... think hot-potato routing.


On 25 June 2024 05:42:47 CEST, David Lang via Starlink <starlink@lists.bufferbloat.net> 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.
>
>David Lang
>_______________________________________________
>Starlink mailing list
>Starlink@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/starlink

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2306 bytes --]

  parent reply	other threads:[~2024-06-25  5:37 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
2024-06-25  5:37         ` Sebastian Moeller [this message]
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=974AF92C-907B-43A3-AC41-449FBAA5EFAE@gmx.de \
    --to=moeller0@gmx.de \
    --cc=david@lang.hm \
    --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