Malte Appel already partially responded to you questions. I will try to provide more details.

Each probe has build-in measurements for 1^st and 2^nd hop. For your probe it is:

If you take your probe as an example you will notice that your first hop is your local router (Starlink dish?) and it has RTT <1ms. It's your 2^nd hop which can indicate what RTT is generated by Starlink satellite connection (RTT Median Average ~30ms). I'm curious where exactly is located this 2^nd hop :)

Regards,

Grzegorz

From: Ray Bellis <ray@isc.org>
Date: Friday 2021-04-23 at 10:44
To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net>
Subject: Re: [atlas] Satellite based "last mile" and Atlas probes

On 22/04/2021 20:52, Ponikierski, Grzegorz via ripe-atlas wrote:

Checking

first hop can be tricky because this first hop can be local router with

RTT <1ms and second hop can indicate that we are on satellite

connectivity. For that API for sure API must be used. Here is the full

list of build in measurements:

https://urldefense.com/v3/__https://beta-docs.atlas.ripe.net/built-in/reference.html*traceroute-5-000-6-999__;Iw!!GjvTz_vk!CGnJSJwFwnAeSTFJcu_wN5qF5pxMnHYnUY2rcHz_afOJoH0Tp49DDDQm0TvPlSQ$

<https://urldefense.com/v3/__https://beta-docs.atlas.ripe.net/built-in/reference.html*traceroute-5-000-6-999__;Iw!!GjvTz_vk!CGnJSJwFwnAeSTFJcu_wN5qF5pxMnHYnUY2rcHz_afOJoH0Tp49DDDQm0TvPlSQ$ >

+ build in ping tests for 1^st and 2^nd hop are respectively measurement

#1 and #2.

Can you please elaborate on this?

I have a separate need (relating to an ICANN RSSAC WG) to be able to

detect high latency last mile hops but I could not identify the specific

"built-in ping tests for 1st and 2nd hop" that you described.

Were you perhaps suggesting that it was actually just the first couple

of rows of data from the built-in *traceroute* tests that hold this data?

thanks,

Ray