[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Proving Gig Speed

Subject: Proving Gig Speed
From: nanog at radu-adrian.feurdean.net (Radu-Adrian Feurdean)
Date: Sun, 22 Jul 2018 13:26:26 +0200
In-reply-to: <871529190.3073.1531921504776.JavaMail.mhammett@ThunderFuck>
References: <DM6PR17MB207641B5B0FDAAD24EEABA36CA5D0@DM6PR17MB2076.namprd17.prod.outlook.com> <CAE-M_OBQTxjf0RZODST_jS67Ldy5OoYbgactqqw_gKWPTAaawg@mail.gmail.com> <[email protected]> <CAE-M_OAJZAXeLEVphAEQXdr0fdLcSRtjqm911NSnPPyDhzQXUA@mail.gmail.com> <[email protected]> <CAE-M_ODN0L_BY=naeaOLo3q7G2frkcDVhqfxfe9XpdkF6UW-ig@mail.gmail.com> <[email protected]> <CAE-M_OA=zq8kjfzK3bcCdaL=OrfzU6GU-yLAB=q-jZtfgqXMNg@mail.gmail.com> <871529190.3073.1531921504776.JavaMail.mhammett@ThunderFuck>

On Wed, Jul 18, 2018, at 15:45, Mike Hammett wrote:
> Fast.com will pull from multiple nodes at the same time. I think there 

Here in Europe, fast.com consistently proven to be 100% UNreliable, especially on high-speed FTTH. OOKla and nPerf gave better results for high-speed connections 100% of the time.

Follow-Ups:
- Proving Gig Speed
  - From: niels=nanog at bakker.net (Niels Bakker)

References:
- Proving Gig Speed
  - From: CGross at ninestarconnect.com (Chris Gross)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)
- Proving Gig Speed
  - From: mark.tinka at seacom.mu (Mark Tinka)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)
- Proving Gig Speed
  - From: mark.tinka at seacom.mu (Mark Tinka)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)
- Proving Gig Speed
  - From: mark.tinka at seacom.mu (Mark Tinka)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)
- Proving Gig Speed
  - From: nanog at ics-il.net (Mike Hammett)

Prev by Date: Proving Gig Speed
Next by Date: issues through CGNat (juniper ms-mpc-128g in mx960)
Previous by thread: Proving Gig Speed
Next by thread: Proving Gig Speed
Index(es):
- Date
- Thread