Here's someone's monitoring setup with high frequency pings:
https://snapshot.raintank.io/dashboard/snapshot/eL3CqijxCvIn0yJz05QQkg47OTNlk05A?orgId=2
Looks better than the 50-115ms reported.

On Mon, May 17, 2021 at 8:34 AM Neal Cardwell <ncardwell@google.com> wrote:

> On Sat, May 15, 2021 at 7:00 PM Matt Mathis via Bloat
> <bloat@lists.bufferbloat.net> wrote:
> >
> > I don't understand: starlink doesn't terminate the TCP connection,
> > does it?   Or are you referring to YT's BBR adequately addressing
> > Starlinks variable RTT?   "Adequately" is probably the operative word.
> > It is not too hard to imagine what goes wrong with BBR if the actual
> > path length varies, and on an underloaded network, you may not be able
> > to even detect the symptoms.
>
> On that note, the article mentions:
>   "Starlink itself measures ping times for Counter-Strike: Go and
> Fortnite in its app, and I rarely saw those numbers dip below 50ms,
> mostly hovering around 85-115ms."
>
> If the range 50ms to 115ms is representative of two-way propagation
> delays on their network, then it sounds like BBR can probably perform
> reasonably well in that environment. The algorithm is designed to
> tolerate factor-of-two variations in RTT and still maintain full
> utilization, if there is reasonable buffering.
>
> neal
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>