From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink latencies for Understanding Latency 4.0 webinar series (deadline Dec 11)
Date: Sat, 6 Dec 2025 16:31:16 +0100 [thread overview]
Message-ID: <CAJUtOOgLqjohQNknKK0DzzqZcWfyQu_k-wccVn8YN2O77bH0Ww@mail.gmail.com> (raw)
Hello to all,
I would like to kindly ask if anyone have some latency measurements from
2025 that I can use in "State of the Bloat" presentation at
https://understandinglatency.com
I need to submit my slides on Friday, December 12.
Thanks.
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
next reply other threads:[~2025-12-06 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 15:31 Frantisek Borsik [this message]
2025-12-06 16:40 ` [Starlink] Re: Starlink latencies for Understanding Latency 4.0 webinar series (deadline Dec 11) 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=CAJUtOOgLqjohQNknKK0DzzqZcWfyQu_k-wccVn8YN2O77bH0Ww@mail.gmail.com \
--to=frantisek.borsik@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