[Starlink] New Customer or route leak?

[Starlink] New Customer or route leak?

[Inemesit Affia]

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] Re: New Customer or route leak?

[j pan]

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] Re: New Customer or route leak?

[Inemesit Affia]

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] Re: New Customer or route leak?

[Inemesit Affia]

Attached is a better testing pair

Jul 3, 2026 5:10:20 PM Inemesit Affia <inemesitaffia@gmail.com>:

> 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] Re: New Customer or route leak?

[Jianping Pan]

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

[Starlink] Re: New Customer or route leak?

[Inemesit Affia]

If you look at the image I attached you'll see that traffic from GSL to @fiberathome goes over Starlink but the return goes via a Singapore IX.

Surely they aren't deliberately running their traffic asymmetrically.

GSL and this company are settlement free peers and the non-Starlink path is lower latency and likely cheaper for @fiberathome

Jul 3, 2026 6:36:49 PM Jianping Pan <pan@uvic.ca>:

> 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

[Starlink] Re: New Customer or route leak?

[Jianping Pan]

yes https://bgp.tools/as-set/RADB::as-starlink-cust
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan

________________________________________
From: Inemesit Affia <inemesitaffia@gmail.com>
Sent: Friday, July 3, 2026 11:03 AM
To: Jianping Pan; Dave Taht via Starlink
Subject: Re: [Starlink] Re: New Customer or route leak?

If you look at the image I attached you'll see that traffic from GSL to @fiberathome goes over Starlink but the return goes via a Singapore IX.

Surely they aren't deliberately running their traffic asymmetrically.

GSL and this company are settlement free peers and the non-Starlink path is lower latency and likely cheaper for @fiberathome

Jul 3, 2026 6:36:49 PM Jianping Pan <pan@uvic.ca>:

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

[Starlink] Re: New Customer or route leak?

[Inemesit Affia]

I don't have a shell or VPS. I'm using Globalping's website via a remotely accessed browser. (My environment is very locked down sorry)

Since AS10075 is in Starlink's AS-SET we know it's at least somewhat deliberate i.e it isn't a route leak. (Similar to what Vocus and Telstra do)

2403:cd40:8::/48 also has a route that may help give you another vantage point

10075 14593 55850 6461

I'll see what I can do later without spending money on a VPS. GSL has a ping testing interface on their fake looking glass

Jul 5, 2026 1:49:49 AM j pan <panatuvicdotca@gmail.com>:

> it's not clear whether a community gateway is involved or traceroute
> just transits through starlink's ground backbone. can you run "ping -D
> -i 0.01 -c 10000 103.179.62.17 > out.txt" on vultr sydney or better
> singapore in addition to "traceroute -AIe 103.179.62.17" and share the
> results with me? cheers.  -j
> -- 
> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
> 
> On Fri, Jul 3, 2026 at 9:50 AM Inemesit Affia <inemesitaffia@gmail.com> wrote:
>> 
>> Attached is a better testing pair
>> 
>> Jul 3, 2026 5:10:20 PM Inemesit Affia <inemesitaffia@gmail.com>:
>> 
>> 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] Re: New Customer or route leak?

[Inemesit Affia]

*Sometime ago, Starlink applied to sell unfiltered connectivity from Bangladesh. Back then I assumed it was just to allow them to drop traffic from Nepal and Bhutan in Bangladesh instead of carrying it to Singapore.*

*Definitely not to sell IPT. Especially not via (seemingly) Fiber.*

*Seems one customer is 10075*

*I still haven't figured out if there's a community gateway arrangement, and the asymmetric traffic routing is still causing issues with increased latency from Europe for GSL and some Vocus customers outside Australia.*

https://x.com/BassonBrain/status/2073764199545667844?s=20

Bangladesh has approved Starlink's request to export unfiltered internet bandwidth to neighbouring countries.

The approval allows Starlink to export International Private Leased Circuit (IPLC) links to carry unfiltered internet traffic from the country to neighbouring nations, marking the first time the government has formally permitted such an arrangement for a satellite internet provider.

The approval is expected to position Bangladesh as a potential regional connectivity hub while also opening a new avenue for local telecom infrastructure companies to earn foreign currency from international bandwidth exports.

Jul 5, 2026 8:06:59 AM Inemesit Affia <inemesitaffia@gmail.com>:

> I don't have a shell or VPS. I'm using Globalping's website via a remotely accessed browser. (My environment is very locked down sorry)
> 
> Since AS10075 is in Starlink's AS-SET we know it's at least somewhat deliberate i.e it isn't a route leak. (Similar to what Vocus and Telstra do)
> 
> 2403:cd40:8::/48 also has a route that may help give you another vantage point
> 
> 10075 14593 55850 6461
> 
> I'll see what I can do later without spending money on a VPS. GSL has a ping testing interface on their fake looking glass
> 
> Jul 5, 2026 1:49:49 AM j pan <panatuvicdotca@gmail.com>:
> 
>> it's not clear whether a community gateway is involved or traceroute
>> just transits through starlink's ground backbone. can you run "ping -D
>> -i 0.01 -c 10000 103.179.62.17 > out.txt" on vultr sydney or better
>> singapore in addition to "traceroute -AIe 103.179.62.17" and share the
>> results with me? cheers.  -j
>> -- 
>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
>> 
>> On Fri, Jul 3, 2026 at 9:50 AM Inemesit Affia <inemesitaffia@gmail.com> wrote:
>>> 
>>> Attached is a better testing pair
>>> 
>>> Jul 3, 2026 5:10:20 PM Inemesit Affia <inemesitaffia@gmail.com>:
>>> 
>>> 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] Re: New Customer or route leak?

[Inemesit Affia]

A link to the article with several details I've not and won't mention.

https://www.thedailystar.net/business/news/bangladesh-approves-starlink-export-unfiltered-internet-bandwidth-neighbouring-countries-4216406

>Summary from elsewhere that's clearly wrong in practice

Bangladesh approved Starlink’s bandwidth export proposal.
• Traffic will serve foreign customers only.
• Initial capacity request: 40 Gbps.
• Scalable up to 400 Gbps.
• Bandwidth expected via BSCCL

Jul 5, 2026 5:02:46 PM Inemesit Affia <inemesitaffia@gmail.com>:

> *Sometime ago, Starlink applied to sell unfiltered connectivity from Bangladesh. Back then I assumed it was just to allow them to drop traffic from Nepal and Bhutan in Bangladesh instead of carrying it to Singapore.*
> 
> *Definitely not to sell IPT. Especially not via (seemingly) Fiber.*
> 
> *Seems one customer is 10075*
> 
> *I still haven't figured out if there's a community gateway arrangement, and the asymmetric traffic routing is still causing issues with increased latency from Europe for GSL and some Vocus customers outside Australia.*
> 
> https://x.com/BassonBrain/status/2073764199545667844?s=20
> 
> Bangladesh has approved Starlink's request to export unfiltered internet bandwidth to neighbouring countries.
> 
> The approval allows Starlink to export International Private Leased Circuit (IPLC) links to carry unfiltered internet traffic from the country to neighbouring nations, marking the first time the government has formally permitted such an arrangement for a satellite internet provider.
> 
> The approval is expected to position Bangladesh as a potential regional connectivity hub while also opening a new avenue for local telecom infrastructure companies to earn foreign currency from international bandwidth exports.
> 
> Jul 5, 2026 8:06:59 AM Inemesit Affia <inemesitaffia@gmail.com>:
> 
>> I don't have a shell or VPS. I'm using Globalping's website via a remotely accessed browser. (My environment is very locked down sorry)
>> 
>> Since AS10075 is in Starlink's AS-SET we know it's at least somewhat deliberate i.e it isn't a route leak. (Similar to what Vocus and Telstra do)
>> 
>> 2403:cd40:8::/48 also has a route that may help give you another vantage point
>> 
>> 10075 14593 55850 6461
>> 
>> I'll see what I can do later without spending money on a VPS. GSL has a ping testing interface on their fake looking glass
>> 
>> Jul 5, 2026 1:49:49 AM j pan <panatuvicdotca@gmail.com>:
>> 
>>> it's not clear whether a community gateway is involved or traceroute
>>> just transits through starlink's ground backbone. can you run "ping -D
>>> -i 0.01 -c 10000 103.179.62.17 > out.txt" on vultr sydney or better
>>> singapore in addition to "traceroute -AIe 103.179.62.17" and share the
>>> results with me? cheers.  -j
>>> -- 
>>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
>>> 
>>> On Fri, Jul 3, 2026 at 9:50 AM Inemesit Affia <inemesitaffia@gmail.com> wrote:
>>>> 
>>>> Attached is a better testing pair
>>>> 
>>>> Jul 3, 2026 5:10:20 PM Inemesit Affia <inemesitaffia@gmail.com>:
>>>> 
>>>> 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] Re: New Customer or route leak?

[Jianping Pan]

given so little jitter, more likely just transit through starlink backbone instead of community gateway, although a longer sequence with a shorter interval will be more conclusive as well

Host/AS Address Loss%   Sent    Last    Avg     Best    Worst   StDev
1. 7578 l880.sg-eqxsg3-cr7.globalsecurelayer.com (206.148.22.141)       0.0     20      0.3     0.3     0.2     0.9     0.1
2. 7578 po31.sg-eqxsg3-cr8.globalsecurelayer.com (206.148.27.42)        0.0     20      0.2     0.2     0.2     0.4     0.0
3. 137409       unknown.globalsecurelayer.com (160.202.164.99)  0.0     20      0.3     0.3     0.2     0.5     0.1
4. 14593        undefined.hostname.localhost (206.224.74.127)   90.0    20      250.6   142.9   35.3    250.6   107.7
5.      74.245.145.54   0.0     20      0.3     0.3     0.2     0.4     0.1
6. 14593        customer.ord3.mc.starlinkisp.net (206.214.228.69)       30.0    20      45.0    44.9    44.9    45.0    0.1
7. 10075        163.47.158.229  0.0     20      48.2    48.0    47.2    51.1    0.9
8. 10075        103.179.62.65   0.0     20      46.5    46.5    46.4    46.5    0.0
9. 10075        103.179.62.17   0.0     20      46.6    46.5    46.4    46.8    0.1
--
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: Sunday, July 5, 2026 9:38 AM
To: j pan; Dave Taht via Starlink
Subject: [Starlink] Re: New Customer or route leak?

A link to the article with several details I've not and won't mention.

https://www.thedailystar.net/business/news/bangladesh-approves-starlink-export-unfiltered-internet-bandwidth-neighbouring-countries-4216406

>Summary from elsewhere that's clearly wrong in practice

Bangladesh approved Starlink’s bandwidth export proposal.
• Traffic will serve foreign customers only.
• Initial capacity request: 40 Gbps.
• Scalable up to 400 Gbps.
• Bandwidth expected via BSCCL

Jul 5, 2026 5:02:46 PM Inemesit Affia <inemesitaffia@gmail.com>:

> *Sometime ago, Starlink applied to sell unfiltered connectivity from Bangladesh. Back then I assumed it was just to allow them to drop traffic from Nepal and Bhutan in Bangladesh instead of carrying it to Singapore.*
>
> *Definitely not to sell IPT. Especially not via (seemingly) Fiber.*
>
> *Seems one customer is 10075*
>
> *I still haven't figured out if there's a community gateway arrangement, and the asymmetric traffic routing is still causing issues with increased latency from Europe for GSL and some Vocus customers outside Australia.*
>
> https://x.com/BassonBrain/status/2073764199545667844?s=20
>
> Bangladesh has approved Starlink's request to export unfiltered internet bandwidth to neighbouring countries.
>
> The approval allows Starlink to export International Private Leased Circuit (IPLC) links to carry unfiltered internet traffic from the country to neighbouring nations, marking the first time the government has formally permitted such an arrangement for a satellite internet provider.
>
> The approval is expected to position Bangladesh as a potential regional connectivity hub while also opening a new avenue for local telecom infrastructure companies to earn foreign currency from international bandwidth exports.
>
> Jul 5, 2026 8:06:59 AM Inemesit Affia <inemesitaffia@gmail.com>:
>
>> I don't have a shell or VPS. I'm using Globalping's website via a remotely accessed browser. (My environment is very locked down sorry)
>>
>> Since AS10075 is in Starlink's AS-SET we know it's at least somewhat deliberate i.e it isn't a route leak. (Similar to what Vocus and Telstra do)
>>
>> 2403:cd40:8::/48 also has a route that may help give you another vantage point
>>
>> 10075 14593 55850 6461
>>
>> I'll see what I can do later without spending money on a VPS. GSL has a ping testing interface on their fake looking glass
>>
>> Jul 5, 2026 1:49:49 AM j pan <panatuvicdotca@gmail.com>:
>>
>>> it's not clear whether a community gateway is involved or traceroute
>>> just transits through starlink's ground backbone. can you run "ping -D
>>> -i 0.01 -c 10000 103.179.62.17 > out.txt" on vultr sydney or better
>>> singapore in addition to "traceroute -AIe 103.179.62.17" and share the
>>> results with me? cheers.  -j
>>> --
>>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
>>>
>>> On Fri, Jul 3, 2026 at 9:50 AM Inemesit Affia <inemesitaffia@gmail.com> wrote:
>>>>
>>>> Attached is a better testing pair
>>>>
>>>> Jul 3, 2026 5:10:20 PM Inemesit Affia <inemesitaffia@gmail.com>:
>>>>
>>>> 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