Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Last Mile ISP Quality Measurements
Date: Tue, 8 Aug 2023 17:00:55 -0700	[thread overview]
Message-ID: <CAA93jw4WWjkeakUSmiyFvTZZKOYvKtTHbFrJPDV_qPiiycJbfA@mail.gmail.com> (raw)
In-Reply-To: <1521535877.2256.1691528896540.JavaMail.mhammett@Thunderfuck2>

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

---------- Forwarded message ---------
From: Mike Hammett <nanog@ics-il.net>
Date: Tue, Aug 8, 2023 at 2:34 PM
Subject: Last Mile ISP Quality Measurements
To: NANOG <nanog@nanog.org>


What are other last mile ISPs doing to measure the quality of their
connections? We all know pinging various destinations. We also all know
that pinging a destination doesn't necessarily tell you the whole quality
story.

I currently have Smokeping pulling the HTTPS for about 20 - 25 of the "top"
websites, per the old Alexa rankings. I feel as though I could be doing
more. I am more closely wanting to emulate the end-user experience in a
repeatable, quantifiable fashion. I'd like to do A/B comparisons as well.
When I make X change, how does it change?


If I'm already doing the low-hanging fruit path, then so be it.



-----
Mike Hammett
Intelligent Computing Solutions <http://www.ics-il.com/>
<https://www.facebook.com/ICSIL>
<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>
<https://www.linkedin.com/company/intelligent-computing-solutions>
<https://twitter.com/ICSIL>
Midwest Internet Exchange <http://www.midwest-ix.com/>
<https://www.facebook.com/mdwestix>
<https://www.linkedin.com/company/midwest-internet-exchange>
<https://twitter.com/mdwestix>
The Brothers WISP <http://www.thebrotherswisp.com/>
<https://www.facebook.com/thebrotherswisp>
<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>


-- 
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos

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

           reply	other threads:[~2023-08-09  0:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1521535877.2256.1691528896540.JavaMail.mhammett@Thunderfuck2>]

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/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4WWjkeakUSmiyFvTZZKOYvKtTHbFrJPDV_qPiiycJbfA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=libreqos@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