Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Jianping Pan <pan@uvic.ca>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Inemesit Affia <inemesitaffia@gmail.com>
Subject: [Starlink] Re: New Customer or route leak?
Date: Fri, 3 Jul 2026 17:36:47 +0000	[thread overview]
Message-ID: <YQBP288MB02896ED3EDF192324ED36B0BA0F42@YQBP288MB0289.CANP288.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0e8dd78c-8d2b-47ef-b8e0-82faf8958f46@gmail.com>

Yes, there is a path from fiber@home (starlink's host for the dhaka pop) through starlink to the world, e.g., https://bgp.he.net/AS10075#_graph6 , although not the main path
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
________________________________
From: Inemesit Affia via Starlink <starlink@lists.bufferbloat.net>
Sent: Friday, July 3, 2026 9:09 AM
To: j pan <panatuvicdotca@gmail.com>; Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: New Customer or route leak?

Try putting that prefix  in BGP.tools or bgp.he and you'll see there's no equal distance route to GSL from that prefix. 103.179.62.0/24


The AS path you'll see is 10075 *14593* 137408

You can try an Australian/Frankfurt/Ashburn looking Glass from GSL or Vultr in Sydney.



Maybe even Vocus or Lumen in Asia/Oceania

From Vultr Sydney

45.76.118.1[Vultr]
???
100.100.200.1
10.74.x.x.
10.74.x.x.
202.77.88.23
206.148.24.194
206.148.24.194
206.148.x.x
206.148.x.x
160.202.164.99[GSL]
206.224.74.121 [Starlink backbone]
???
206.214.228.69 [SB]
163.47.158.229[10075]
103.179.62.1[10075]

While I looked into it I found out it looks like an asymmetric route.


Attached is the traceroute for the forward and reverse path

Jul 3, 2026 3:40:26 PM j pan <panatuvicdotca@gmail.com>:

> how do you know it traverses through starlink? it does not appear so
> from the following
>
> traceroute to 1.1.1.1 (1.1.1.1), 20 hops max, 60 byte packets
> 1  _gateway (103.131.159.193)  0.645 ms  0.617 ms
> 2  103.179.62.76 (103.179.62.76)  0.598 ms  0.596 ms
> 3  103.131.159.145 (103.131.159.145)  1.257 ms  1.261 ms
> 4  103.7.249.234 (103.7.249.234)  26.821 ms  26.818 ms
> 5  one.one.one.one (1.1.1.1)  1.070 ms  1.067 ms
> --
> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
>
> On Fri, Jul 3, 2026 at 4:14 AM Inemesit Affia via Starlink
> <starlink@lists.bufferbloat.net> wrote:
>>
>> 103.179.62.0/24 and other prefixes from a Bangladeshi provider are going to Australia(Singapore?) {GSL} via Starlink.
>>
>> I'm not seeing any latency improvements (HE has similar performance in Sydney) and I also noticed Vocus is taking some traffic from Singapore via Perth to Bangladesh via this path.
>>
>> Seen probes in Frankfurt/Ashburn/elsewhere do the similar.
>>
>>
>> Is there really a Community Gateway working this?
>>
>> Where's it(Singapore/Australia)?
>>
>> When I started at a large multinational Telco decades ago, I met a system that monitored/tracked path latency to pretty much every country/provider and alerted on shifts, is that something unusual to have?
>> _______________________________________________
>> Starlink mailing list -- starlink@lists.bufferbloat.net
>> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
_______________________________________________
Starlink mailing list -- starlink@lists.bufferbloat.net
To unsubscribe send an email to starlink-leave@lists.bufferbloat.net

  parent reply	other threads:[~2026-07-03 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 11:14 [Starlink] New Customer or route leak? Inemesit Affia
2026-07-03 14:40 ` [Starlink] " j pan
2026-07-03 16:09   ` Inemesit Affia
2026-07-03 16:49     ` Inemesit Affia
2026-07-03 17:36     ` Jianping Pan [this message]
2026-07-03 18:03       ` Inemesit Affia
2026-07-04 23:41         ` Jianping 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=YQBP288MB02896ED3EDF192324ED36B0BA0F42@YQBP288MB0289.CANP288.PROD.OUTLOOK.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