General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Has any one seen the VSee Network Stability Test?
Date: Sun, 29 Sep 2024 09:03:50 -0700	[thread overview]
Message-ID: <CAA93jw5+SOxsqcidjQezq-etL70iXg80Yee2VjFDy3nY7KB5Mw@mail.gmail.com> (raw)
In-Reply-To: <3CDF93BB-6257-46E2-B6F3-DEE3246A3CBA@gmail.com>

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

Neat. I ran it concurrently with a few other tests on my starlink, with an
ongoing score of excellent to good.

On Sun, Sep 29, 2024 at 6:04 AM Rich Brown via Bloat <
bloat@lists.bufferbloat.net> wrote:

> I came across an intriguing utility a while back. The "VSee Network
> Stability Test" is a web page that continually monitors the quality of your
> network connection so you can determine whether your Zoom call crapped out
> because of a network problem. (VSee provides telehealth services, and I
> imagine they created this test so they could blame someone else...)
>
> It appears that the test page establishes an RTC connection to their
> server, and uses the response times of the traffic to compute latency,
> jitter, and packet loss. It also computes MOS score (used to rate telephone
> call quality) and shows all three in graphs. Check it out at:
>
> https://test.vsee.com/network/index.html
>
> Although the underlying data is compelling, their web page is as ugly as
> sin (at least for non-techies). I have asked VSee whether they might be
> open to making changes, or if they might make the source code available,
> but I think it's unlikely.
>
> Alternatively, does anyone know of an equivalent facility that has a) a
> nicer web page and b) source code available? Thanks
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>


-- 
Dave Täht CSO, LibreQos

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

  reply	other threads:[~2024-09-29 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29 13:04 Rich Brown
2024-09-29 16:03 ` Dave Taht [this message]
2024-09-29 18:13   ` David Collier-Brown
2024-09-30 17:21 ` 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=CAA93jw5+SOxsqcidjQezq-etL70iXg80Yee2VjFDy3nY7KB5Mw@mail.gmail.com \
    --to=dave.taht@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