Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] RIPE Atlas Probes
Date: Tue, 1 Nov 2022 17:29:24 +0000	[thread overview]
Message-ID: <A75386F5-5002-4BDA-BCE5-340BB1359584@cable.comcast.com> (raw)
In-Reply-To: <94F9DD4F-66DA-42CC-8D5A-90DB9544CE5D@cable.comcast.com>

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

I still need 5 more Starlink folks for RIPE Atlas. Any more takers? Come on…. 😉

Jason

From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Date: Thursday, October 27, 2022 at 09:00
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: RIPE Atlas Probes

In my day job, I just renewed our RIPE Atlas sponsorship and have a bunch of new probes coming in soon. I thought it might be cool to get some folks to deploy these to users of Starlink in the US. If you might be interested in doing so, I am guessing I will have probes be able to ship them in about a month (given the upcoming IETF meeting). Once you receive a probe, it connects to your network via Ethernet and you will need to use the RIPE Atlas site to activate the probe – which is about 5 mins work.

If you might be interested, please email me *OFF LIST* with the following info:

  1.  Your first & last name
  2.  Your shipping address

Don’t know what RIPE Atlas is? See https://atlas.ripe.net/ There are currently ~1,400 active probes in the US.

Thanks!
Jason

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

  reply	other threads:[~2022-11-01 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 16:25 Livingood, Jason
2022-11-01 17:29 ` Livingood, Jason [this message]
2022-12-05 17:38 Livingood, Jason

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

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

  git send-email \
    --in-reply-to=A75386F5-5002-4BDA-BCE5-340BB1359584@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=starlink@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