Some additional comments from Dave Taht, who does not subscribe to the
nanog list. Also note the early WiFi results, which are spectacular. Your
customers will have bufferbloat both due to the ISP, and due to the WiFi
hop that is usually between them and their home router. Unfortunately,
it's
Just a quick clarifying reply, I have had DSL test give me an A for bufferbloat
and a C for Speed on a 75 Meg line.
On July 22, 2016 3:23:00 PM EDT, Jim Gettys wrote:
>I don't read this list continually, but do archive it; your note was
>flagged for me to comment on.
>
>On
On Fri, Jul 22, 2016 at 4:18 PM, Baldur Norddahl
wrote:
> Den 22. jul. 2016 21.34 skrev "Jim Gettys" :
> >
> >
> > So it is entirely appropriate in my view to give even "high speed"
> > connections low grades; it's telling you that they suck under
Den 22. jul. 2016 21.34 skrev "Jim Gettys" :
>
>
> So it is entirely appropriate in my view to give even "high speed"
> connections low grades; it's telling you that they suck under load
> , like when your kid is downloading a video (or uploading one for their
> friends);
Jim,
No problems, I just knew you were one of the project founders. I found it on
the website shortly after posting.
My google-fu wasn’t up to par.
https://www.bufferbloat.net/projects/cerowrt/wiki/Tests_for_Bufferbloat/
I’m assuming I used the script last time for netperf, but have downloaded
I don't read this list continually, but do archive it; your note was
flagged for me to comment on.
On Thu, Jul 21, 2016 at 8:11 PM, Eric Tykwinski
wrote:
> This is probably for Jim Gettys directly, but I’m sure most others have
> input. I could of sworn that that there
Good point, we would need a piece of websocket code to run before or after NDT
that figures out MAX speed so end users we can compare with other speed tests.
NDT is about the quality of a connection, not absolute maximum quantity that
can be jammed on a link irrespective of errors and all.
And work on accurate measurement of higher link speeds. ;-)
On 7/20/16, 11:42 PM, "NANOG on behalf of Collin Anderson"
wrote:
On Wed, Jul 20, 2016 at 5:00 PM, Antonio Querubin
wrote:
>
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,
On 7/21/16, 2:19 PM, "NANOG on behalf of Jay R. Ashworth"
wrote:
>- Original Message -
>> From: "Janusz Jezowicz"
>
>> Since this morning Speedtest.net is not accessible in Chrome
>> Reason:
>>
- Original Message -
> From: "Janusz Jezowicz"
> 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
On Wed, Jul 20, 2016 at 5:00 PM, Antonio Querubin
wrote:
> Feedback: needs IPv6 connectivity and support.
>
Point well taken. The vast majority of M-Lab sites have IPv6 connectivity,
and we have enabled it for NDT at times, but I believe there was a concern
at one point
On Wed, 20 Jul 2016, Collin Anderson wrote:
Thanks for the mention – for what it's worth, we are testing a more
accessible interface for the web-based NDT test.
Link: https://speed.measurementlab.net/#/
Definitely interested in feedback from the NANOG community.
Feedback: needs IPv6
Thanks for the mention – for what it's worth, we are testing a more
accessible interface for the web-based NDT test.
Link: https://speed.measurementlab.net/#/
Definitely interested in feedback from the NANOG community.
On Wed, Jul 20, 2016 at 10:32 AM, Ishmael Rufus wrote:
On Wed, Jul 20, 2016 at 3:56 PM, David wrote:
> On 2016-07-20 12:52 PM, Jacques Latour wrote:
>
>> In that case, for Canadians, go to http://performance.cira.ca, it's
>> MLAB-NDT based and checks IPv6 and DNSSEC :-)
>>
>> 100% ad free
>>
>>
> And on the flip side, refuses to
Yup, websocket implementations across all browsers not equal
On 2016-07-20, 2:56 PM, "NANOG on behalf of David"
wrote:
>On 2016-07-20 12:52 PM, Jacques Latour wrote:
>> In that case, for Canadians, go to http://performance.cira.ca, it's
On 2016-07-20 12:52 PM, Jacques Latour wrote:
In that case, for Canadians, go to http://performance.cira.ca, it's MLAB-NDT
based and checks IPv6 and DNSSEC :-)
100% ad free
And on the flip side, refuses to work with Safari.
In that case, for Canadians, go to http://performance.cira.ca, it's MLAB-NDT
based and checks IPv6 and DNSSEC :-)
100% ad free
>-Original Message-
>From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Ishmael Rufus
>Sent: July-20-16 10:33 AM
>To: Janusz Jezowicz
>Cc: NANOG list
It is back for us in Houston via NTT and Level 3 ... no warnings when you got
to site...
Robert Jacobs | Network Director/Architect
Direct: 832-615-7742
Main: 832-615-8000
Fax: 713-510-1650
5959 Corporate Dr. Suite 3300; Houston, TX 77036
A Certified Woman-Owned Business
24x7x365
http://www.measurementlab.net/tools/ndt/
100% ad free.
On Wed, Jul 20, 2016 at 7:55 AM, Janusz Jezowicz
wrote:
> It seems that some users reporting the site is back. I am counting 6+ hours
> of outage.
>
> Alan - what you describe is something normal user will never
It seems that some users reporting the site is back. I am counting 6+ hours
of outage.
Alan - what you describe is something normal user will never do. When user
sees red screen like that, he runs screaming. So in theory yes, it was
accessible, but ... wasn't.
Its hard to avoid Google nanny when
Hi,
> Since this morning Speedtest.net is not accessible in Chrome
> Reason:
> https://www.google.com/transparencyreport/safebrowsing/diagnostic/#url=c.speedtest.net
someones complained about the URL based on them stupidly installing
'cleanmymac' or such?
use the non flash junk HTML5 version
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.
e.g.
23 matches
Mail list logo