From: <tom@evslin.com>
To: "'Luis A. Cornejo'" <luis.a.cornejo@gmail.com>
Cc: "'Dave Taht via Starlink'" <starlink@lists.bufferbloat.net>,
"'bloat'" <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Bufferbloat
Date: Thu, 31 Aug 2023 17:06:28 -0400 [thread overview]
Message-ID: <101301d9dc4f$02eaf520$08c0df60$@evslin.com> (raw)
In-Reply-To: <CAKJdXWDG2gNRYRYkhGPLxzeHc-ZOKkjqdRChWtLvc8U-nf2XYw@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2023-08-31 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 20:08 Luis A. Cornejo
2023-08-31 20:22 ` tom
2023-08-31 20:46 ` Luis A. Cornejo
2023-08-31 21:06 ` tom [this message]
2023-08-31 21:59 ` Spencer Sevilla
2023-09-01 6:39 ` Tom Zubko
2023-09-01 12:32 ` Luis A. Cornejo
2023-09-01 14:22 ` Tom Zubko
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 4:19 [Starlink] Starlink bufferbloat Brenton Roskopf
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='101301d9dc4f$02eaf520$08c0df60$@evslin.com' \
--to=tom@evslin.com \
--cc=bloat@lists.bufferbloat.net \
--cc=luis.a.cornejo@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