From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Re: Cutie Network Quality Test now in alpha-test
Date: Mon, 27 Oct 2025 17:38:16 +0100 [thread overview]
Message-ID: <CAJUtOOiX+Hw4itcR1YphZVXADdfMcpq1W1mFAbFpDt1Wmsn9TQ@mail.gmail.com> (raw)
In-Reply-To: <762B8320-B928-4CC2-BF2B-3B8CD0BF7A24@gmx.de>
Hey Rich,
Looking good. Something like https://orb.net, to the some extent? Or rather
the idea of somehow constant connection on the background, not saturating
the link as a typical speedtest would do...
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
On Mon, Oct 27, 2025 at 4:58 PM Sebastian Moeller via Bloat <
bloat@lists.bufferbloat.net> wrote:
> Hi Rich,
>
> most excellent!
>
> One question though would it be possible to also split out the packet loss
> per direction?
>
> https://packetlosstest.com/ does do this and this has been quite helpful
> for debugging odd things happening on links... I hope that WebRTC is
> verbose enough to report this in a useful way.
>
>
>
> > On 27. Oct 2025, at 15:46, Rich Brown <richb.hanover@gmail.com> wrote:
> >
> > With some trepidation (and a little bit of pride), I announce the Cutie
> network quality test. Inspired by the VSee Network Stability Test, Cutie is
> a completely new implementation of that concept that establishes a WebRTC
> connection to its backend server, then uses the RTC stream (10 messages per
> second) to measure and chart latency, jitter, and packet loss.
> >
> > You can try the demo site at: netperf.bufferbloat.net:5173 <
> http://netperf.bufferbloat.net:5173/> or you can install Cutie on a local
> server to test your own network.
> >
> > There’s lots more information in the Github repo at:
> https://github.com/richb-hanover/Cutie-Network-Quality-Test
> >
> > Comments and bug reports welcome. Enjoy!
> >
> > Rich
> >
> > PS Why “Cutie”? It’s a vaguely humorous pronunciation of “QT” for
> Quality Test...
> > _______________________________________________
> > Bloat mailing list -- bloat@lists.bufferbloat.net
> > To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
>
> _______________________________________________
> Bloat mailing list -- bloat@lists.bufferbloat.net
> To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
>
next prev parent reply other threads:[~2025-10-27 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 14:46 [Bloat] " Rich Brown
2025-10-27 15:58 ` [Bloat] " Sebastian Moeller
2025-10-27 16:38 ` Frantisek Borsik [this message]
2025-10-27 16:54 ` Eric
2025-10-28 3:08 ` Rich Brown
[not found] ` <MW4PR11MB71047059F01078746A3F27E4C7FAA@MW4PR11MB7104.namprd11.prod.outlook.com>
2025-10-30 2:11 ` Rich Brown
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJUtOOiX+Hw4itcR1YphZVXADdfMcpq1W1mFAbFpDt1Wmsn9TQ@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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