Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: A hop-by-hop view of Cloudflare network engineer Tom Strickx crossing the Atlantic on Starlink Wi-Fi.
Date: Thu, 05 Nov 2026 13:00:02 -0500	[thread overview]
Message-ID: <14565.1793901602@obiwan.sandelman.ca> (raw)
In-Reply-To: <F81246CD-86DF-4F49-8194-0E8287D57AAA@sandelman.ca>

--------

Michael Richardson via Starlink <starlink@lists.bufferbloat.net> wrote:
    > I take it that the inter satellite laser links are not visible at layer-3?

    > By anycast network, do you mean that Starlink is sending BGP updates
    > for the /56? Or are you saying that there is a constant anycast BGP (of
    > a bigger prefix) from everyone of starlinks' ground stations, and they
    > handle the routing internally?

    > I guess I am trying to understand what Cloudflare sees.  Is there a
    > Redirect at http layer, (and a new cloudflare IP) which steers the
    > traffic to the nearest cloudflare pop?

I re-read the tweet itself (I thought twitter now made everyone login...)
while waiting for my flu show.. but all the text had already been
cross-posted, so I didn't learn anything new.

It seems like a case of two entities doing anycast, and it actually finding
the shortest/best path between DCs.  I guess I'm just astonished, given how
the whole multi-exit/multi-peer stuff never seemed to quite work, creating
demand for other systems managed by SDN PCEs.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
]       My working hours and your working hours may be different.            [
]  Please do not feel obligated to reply outside your normal working hours   [



      parent reply	other threads:[~2026-11-05 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 14:29 [Starlink] A hop-by-hop view of Cloudflare network engineer Tom Strickx crossing the Atlantic on Starlink Wi-Fi Frantisek Borsik
2026-11-05 14:34 ` [Starlink] " Jianping Pan
2026-11-05 16:11   ` Michael Richardson
2026-11-05 16:45     ` Jianping Pan
2026-11-05 18:00     ` Michael Richardson [this message]

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=14565.1793901602@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --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