This is probably for Jim Gettys directly, but I’m sure most others have input. I could of sworn that that there was some test made to detect it directly on switches and routers? Sort of like iperf, but to test bufferbloat specifically given the OS stack which is going to have issues as well, as shown on bufferbloat.net <http://bufferbloat.net/>.
> On Jul 21, 2016, at 6:36 PM, Donn Lasher via NANOG <nanog@nanog.org> wrote: > > On 7/21/16, 2:19 PM, "NANOG on behalf of Jay R. Ashworth" > <nanog-boun...@nanog.org on behalf of j...@baylink.com> wrote: > > > >> ----- Original Message ----- >>> From: "Janusz Jezowicz" <jan...@speedchecker.xyz> >> >>> Since this morning Speedtest.net is not accessible in Chrome >>> Reason: >>> https://www.google.com/transparencyreport/safebrowsing/diagnostic/#url=c.speedtest.net >>> >>> For any ISPs/content providers linking to speedtest.net you may want to >>> swap links to a different website or host your own speed test. >> >> So far, I am very pleased with how it works, though I think it's letter >> grades on speed are a bit pessimistic (65Mbps is a "C"). >> >> Specifically, it measures bufferbloat, with both a realtime graph and a > > > Are you talking about the dslreports speedtest? I like that one, very > detailed results. > > http://speedtest.dslreports.com/ > > > I’d agree with the pessimistic scoring.. 160Mbit was given a “B” grade. > > > >
