[Starlink] Starlink Bufferbloat

[Starlink] Starlink Bufferbloat

[Luis A. Cornejo]

[-- Attachment #1.1: Type: text/plain, Size: 260 bytes --]

I saw this screen shot on Reddit. Seemed like it might of been a fluke?
Isolated case? Are they cheating? No way they have seen the light?

I don’t have my dishy anymore, but can someone double check for me?

https://reddit.com/r/Starlink/s/ysQ0AZ6RKX

[-- Attachment #1.2: Type: text/html, Size: 539 bytes --]

[-- Attachment #2: A3B740C6-EC7B-49E5-8094-CD73FB8A14ED.png --]
[-- Type: image/png, Size: 361700 bytes --]

Re: [Starlink] Starlink Bufferbloat

[tom]

[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]

I’ve seen isolated results like this from my dish in central Vermont. They were more frequent during the beta.

 

From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Luis A. Cornejo via Starlink
Sent: Thursday, August 31, 2023 4:09 PM
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
Subject: [Starlink] Starlink Bufferbloat

 

I saw this screen shot on Reddit. Seemed like it might of been a fluke? Isolated case? Are they cheating? No way they have seen the light?

 

I don’t have my dishy anymore, but can someone double check for me?

 

https://reddit.com/r/Starlink/s/ysQ0AZ6RKX

 



 


[-- Attachment #1.2: Type: text/html, Size: 3160 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 361700 bytes --]

Re: [Starlink] Starlink Bufferbloat

[Luis A. Cornejo]

[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]

I had an almost identical result via the waveform tool. But was never able
to reproduce it, so I took it as a fluke or waveform mis measurement.

Just judging by the speed it might just be in an isolated cell, not a not
busy time.

It seems that Ookla seems to be gamed by the ISPs frequently. So that might
explain it also.

Have you tried the Cloudflare speed test on your dishy with the same loaded
pings?

-Luis

On Thu, Aug 31, 2023 at 3:22 PM <tom@evslin.com> wrote:

> I’ve seen isolated results like this from my dish in central Vermont. They
> were more frequent during the beta.
>
>
>
> *From:* Starlink <starlink-bounces@lists.bufferbloat.net> *On Behalf Of *Luis
> A. Cornejo via Starlink
> *Sent:* Thursday, August 31, 2023 4:09 PM
> *To:* Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <
> bloat@lists.bufferbloat.net>
> *Subject:* [Starlink] Starlink Bufferbloat
>
>
>
> I saw this screen shot on Reddit. Seemed like it might of been a fluke?
> Isolated case? Are they cheating? No way they have seen the light?
>
>
>
> I don’t have my dishy anymore, but can someone double check for me?
>
>
>
> https://reddit.com/r/Starlink/s/ysQ0AZ6RKX
>
>
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3184 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 361700 bytes --]

Re: [Starlink] Starlink Bufferbloat

[tom]

[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]

Actually my results were with the cloudflare speedtest

 

From: Luis A. Cornejo <luis.a.cornejo@gmail.com> 
Sent: Thursday, August 31, 2023 4:47 PM
To: tom@evslin.com
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Bufferbloat

 

I had an almost identical result via the waveform tool. But was never able to reproduce it, so I took it as a fluke or waveform mis measurement.

 

Just judging by the speed it might just be in an isolated cell, not a not busy time.

 

It seems that Ookla seems to be gamed by the ISPs frequently. So that might explain it also.

 

Have you tried the Cloudflare speed test on your dishy with the same loaded pings?

 

-Luis

 

On Thu, Aug 31, 2023 at 3:22 PM <tom@evslin.com <mailto:tom@evslin.com> > wrote:

I’ve seen isolated results like this from my dish in central Vermont. They were more frequent during the beta.

 

From: Starlink <starlink-bounces@lists.bufferbloat.net <mailto:starlink-bounces@lists.bufferbloat.net> > On Behalf Of Luis A. Cornejo via Starlink
Sent: Thursday, August 31, 2023 4:09 PM
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net> >; bloat <bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net> >
Subject: [Starlink] Starlink Bufferbloat

 

I saw this screen shot on Reddit. Seemed like it might of been a fluke? Isolated case? Are they cheating? No way they have seen the light?

 

I don’t have my dishy anymore, but can someone double check for me?

 

https://reddit.com/r/Starlink/s/ysQ0AZ6RKX

 



 


[-- Attachment #1.2: Type: text/html, Size: 5967 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 361700 bytes --]

Re: [Starlink] Starlink Bufferbloat

[Spencer Sevilla]

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

FWIW, I got 188 down a few weeks ago in the high Arctic (~70 degrees latitude). DL usually hung out around 100 more or less, at times was as low as 30, and then this was the highest result I saw.

> On Aug 31, 2023, at 14:06, Tom Evslin via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> Actually my results were with the cloudflare speedtest
>  
> From: Luis A. Cornejo <luis.a.cornejo@gmail.com> 
> Sent: Thursday, August 31, 2023 4:47 PM
> To: tom@evslin.com
> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <bloat@lists.bufferbloat.net>
> Subject: Re: [Starlink] Starlink Bufferbloat
>  
> I had an almost identical result via the waveform tool. But was never able to reproduce it, so I took it as a fluke or waveform mis measurement.
>  
> Just judging by the speed it might just be in an isolated cell, not a not busy time.
>  
> It seems that Ookla seems to be gamed by the ISPs frequently. So that might explain it also.
>  
> Have you tried the Cloudflare speed test on your dishy with the same loaded pings?
>  
> -Luis
>  
> On Thu, Aug 31, 2023 at 3:22 PM <tom@evslin.com <mailto:tom@evslin.com>> wrote:
>> I’ve seen isolated results like this from my dish in central Vermont. They were more frequent during the beta.
>>  
>> From: Starlink <starlink-bounces@lists.bufferbloat.net <mailto:starlink-bounces@lists.bufferbloat.net>> On Behalf Of Luis A. Cornejo via Starlink
>> Sent: Thursday, August 31, 2023 4:09 PM
>> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>>; bloat <bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net>>
>> Subject: [Starlink] Starlink Bufferbloat
>>  
>> I saw this screen shot on Reddit. Seemed like it might of been a fluke? Isolated case? Are they cheating? No way they have seen the light?
>>  
>> I don’t have my dishy anymore, but can someone double check for me?
>>  
>> https://reddit.com/r/Starlink/s/ysQ0AZ6RKX
>>  
>> <image001.png>
>>  
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


[-- Attachment #2.1: Type: text/html, Size: 9965 bytes --]

[-- Attachment #2.2: Screenshot 2023-08-15 at 08.02.43.png --]
[-- Type: image/png, Size: 241683 bytes --]

Re: [Starlink] Starlink Bufferbloat

[Tom Zubko]

[-- Attachment #1: Type: text/html, Size: 10838 bytes --]

Re: [Starlink] Starlink Bufferbloat

[Luis A. Cornejo]

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

Tom,

Did you perhaps forget to attach images or include links?

-Luis

On Fri, Sep 1, 2023 at 1:41 AM Tom Zubko via Starlink <
starlink@lists.bufferbloat.net> wrote:

> Hi Spencer
>
> A degree or so south from your experience, and closer to Alaska. But same
> polar laser cross linked environment.
>
> First one is a HP dish. Second one is a residential unit. Usually a bit
> more spread between the 2 but not as much as I expected.
>
> Obviously we are sucking hard on the pipe!!
>
> Tom Zubko
> New North
> C 1-867-777-6190
> O 1-867-777-2111
>
> On Aug 31, 2023, at 15:59, Spencer Sevilla via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
> FWIW, I got 188 down a few weeks ago in the high Arctic (~70 degrees
> latitude). DL usually hung out around 100 more or less, at times was as low
> as 30, and then this was the highest result I saw.
> <Screenshot 2023-08-15 at 08.02.43.png>
>
> On Aug 31, 2023, at 14:06, Tom Evslin via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
> Actually my results were with the cloudflare speedtest
>
> *From:* Luis A. Cornejo <luis.a.cornejo@gmail.com>
> *Sent:* Thursday, August 31, 2023 4:47 PM
> *To:* tom@evslin.com
> *Cc:* Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <
> bloat@lists.bufferbloat.net>
> *Subject:* Re: [Starlink] Starlink Bufferbloat
>
> I had an almost identical result via the waveform tool. But was never able
> to reproduce it, so I took it as a fluke or waveform mis measurement.
>
> Just judging by the speed it might just be in an isolated cell, not a not
> busy time.
>
> It seems that Ookla seems to be gamed by the ISPs frequently. So that
> might explain it also.
>
> Have you tried the Cloudflare speed test on your dishy with the same
> loaded pings?
>
> -Luis
>
> On Thu, Aug 31, 2023 at 3:22 PM <tom@evslin.com> wrote:
>
> I’ve seen isolated results like this from my dish in central Vermont. They
> were more frequent during the beta.
>
> *From:* Starlink <starlink-bounces@lists.bufferbloat.net> *On Behalf Of *Luis
> A. Cornejo via Starlink
> *Sent:* Thursday, August 31, 2023 4:09 PM
> *To:* Dave Taht via Starlink <starlink@lists.bufferbloat.net>; bloat <
> bloat@lists.bufferbloat.net>
> *Subject:* [Starlink] Starlink Bufferbloat
>
> I saw this screen shot on Reddit. Seemed like it might of been a fluke?
> Isolated case? Are they cheating? No way they have seen the light?
>
> I don’t have my dishy anymore, but can someone double check for me?
>
> https://reddit.com/r/Starlink/s/ysQ0AZ6RKX
>
> <image001.png>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

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

Re: [Starlink] Starlink Bufferbloat

[Tom Zubko]

[-- Attachment #1.1: Type: text/html, Size: 11445 bytes --]

[-- Attachment #1.2: image.png --]
[-- Type: image/png, Size: 810908 bytes --]

[Starlink] Starlink bufferbloat

[Brenton Roskopf]

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

I, too, have noticed inordinate amounts of latency concurrent with
aggressive file transfers and speed tests (with some healthy losses,
occasionally). Anything I can do to help with testing? Anywhere I can
"upvote" a support ticket or something? Already on:
https://starlinkstatus.space/stations

Not using the Starlink router. But have several openwrt instances (vm and
physical) and other routers connected over IPv4 CGNAT and IPv6 to the WAN
(I think 3 separate dual-stack configs and an IPv4-dedicated one). I am
also scripting dynamic DNS to godaddy if intra-network testing using iperf,
flent or some other tool is useful.

Just switched to 1.1.1.1 for DNS and seeing the DoH traffic, but, sadly,
haven't really noticed much relief. Recent dishy updates seem to have
improved things, but I did need to make significant tweaks to sysctl.conf
on my public-facing Linux VM in order to get decent speedtests using
speedtest-cli... Not really sure how to do that on a Windows system.

-the_notnerb

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