[Bloat] Cutie Network Quality Test now in alpha-test

[Bloat] Cutie Network Quality Test now in alpha-test

[Rich Brown]

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] Re: Cutie Network Quality Test now in alpha-test

[Sebastian Moeller]

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] Re: Cutie Network Quality Test now in alpha-test

[Frantisek Borsik]

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
>

[Bloat] Re: Cutie Network Quality Test now in alpha-test

[Eric]

On Monday, October 27th, 2025 at 07:47, 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

Hey Rich,

Are you ready to list it on Sebastian's testing thread?

https://forum.openwrt.org/t/2025-current-recommendations-for-bufferbloat-testing/241303

Eric

[Bloat] Re: Cutie Network Quality Test now in alpha-test

[Rich Brown]

Thanks for all these suggestions! Some quick responses:

- No, it’s not ready for a broader audience. My server seems to hang/crash after a while with multiple connections. I am adding logging to see what happens.

- One-way packet loss as implemented by packetlosstest.com is intriguing. I’ll have to think about how to implement the algorithm. The current client sends messages with { seq-num, timestamp } and the server echoes those messages back. The client can then derive latency/jitter and packet loss. 

- Cutie is designed to report on latency/jitter/loss during “normal operation”. Start it up and let it run while you’re on a Zoom call. In that respect, it’s similar to orb.net, except you can run the server locally to test your local network

I’ll send an update when there’s a new version of Cutie. Thanks again!

Rich

> On Oct 27, 2025, at 10: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] Re: Cutie Network Quality Test now in alpha-test

[Rich Brown]

Hi Jason,

Thanks for checking out Cutie. I’m glad it worked for you. It still needs to beef up the server side - it keeps going to sleep after an indeterminate time. I just added more logging.

Rich

> On Oct 29, 2025, at 11:19, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> 
> Very cool! I ran this test via by Comcast cable modem during a Microsoft Teams call with Slack, Chrome, and Outlook in the background. 
> 
> <Screenshot 2025-10-29 at 11.17.16.png>
> <Screenshot 2025-10-29 at 11.17.42.png>
> 
> Latency Monitor
> 
> Metric
> Now
> Min
> Max
> 10s Avg
> MOS Quality
> 4.38
> 4.37
> 4.39
> 4.38
> Packet Loss %
> 0.00 %
> 0.00 %
> 0.00 %
> 0.00 %
> Latency
> 30.20 ms
> 24.80 ms
> 49.00 ms
> 35.49 ms
> Jitter
> 5.51 ms
> 0.00 ms
> 7.80 ms
> 
> 
> 
> From: Rich Brown <richb.hanover@gmail.com>
> Date: Monday, October 27, 2025 at 10:47
> To: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
> Cc: Richard Brown <richb.hanover@gmail.com>
> Subject: [Bloat] Cutie Network Quality Test now in alpha-test
> 
> 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 <https://urldefense.com/v3/__http://netperf.bufferbloat.net:5173/__;!!CQl3mcHX2A!DGUep6rbrYzzIVRDl8vYGmBVcGxpubYs8I8vL2DfN0UmEK9i1Uq5wStI-5RW2ZacTNPoEl8E-U0FKahU77MAjs1VJ8IGTg$ > 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://urldefense.com/v3/__https://github.com/richb-hanover/Cutie-Network-Quality-Test__;!!CQl3mcHX2A!DGUep6rbrYzzIVRDl8vYGmBVcGxpubYs8I8vL2DfN0UmEK9i1Uq5wStI-5RW2ZacTNPoEl8E-U0FKahU77MAjs1we3rw_w$
> 
> 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