Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Tristan Horn <tristan@ethereal.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] A year of Starlink latency and loss metrics
Date: Tue, 11 Jun 2024 21:32:31 -0700	[thread overview]
Message-ID: <CALWT4TK5uiryD9JG4bLJsZHub_+-eo6S8gb3oQbMZU0ffKOu_Q@mail.gmail.com> (raw)

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

Not my metrics, but spotted this on Reddit and I'm always a sucker for
Grafana graphs:

https://www.reddit.com/r/Starlink/comments/1dd4wjs/i_collected_metrics_on_my_starlink_for_nearly_a/

I probably have little relevant to add (I returned my Starlink terminal in
2023), but the thread inspired me to get some stats going again myself
(using the same ping_exporter <https://github.com/czerwonk/ping_exporter>).
I used to even collect minutely traceroutes and single-stream TCP
throughput ... I've gotten soft, I guess.

Tris

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

             reply	other threads:[~2024-06-12  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  4:32 Tristan Horn [this message]
2024-06-14  3:17 ` Ulrich Speidel
2024-07-08  4:54   ` J 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=CALWT4TK5uiryD9JG4bLJsZHub_+-eo6S8gb3oQbMZU0ffKOu_Q@mail.gmail.com \
    --to=tristan@ethereal.net \
    --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