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

[Rich Brown <richb.hanover@gmail.com>]

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...