Re: [atlas] Satellite based "last mile" and Atlas probes

[Romain Fontugne]

Hi Eric,

This gives you the list of probes that have a last-mile median RTT 
(endpoint_type=LM__gte=495) higher than 495ms:

https://ihr.iijlab.net/ihr/api/network_delay/?timebin=2021-04-21T00%3A15_type=LM__gte=495

Looks like probes 55562 and 1000244 are both in US and over satellite.
I don't see the probes tagged with 'Satellite' but some of these probes 
are <200ms to the K-root... 
https://atlas.ripe.net/api/v2/measurements/1001/results/?probe_ids=14943=1619136000=1619222399=json


Romain

On 4/23/21 12:18 AM, Eric Kuhnke wrote:

Hello all,

I am running what I believe to be the only probe on a Starlink satellite 
connection right now:


https://atlas.ripe.net/probes/1001821/ 



Is anyone aware of a list of probe ID numbers which are definitively 
known to be on some form of satellite-based access technology? I am 
thinking of, for instance, sites on consumer grade geostationary VSATs, 
more serious VSATs, or in island nations which are not known to have any 
submarine cables.


The reason why I am searching for such a list is that I intend to 
consume some of my accumulated credits to run periodic one-off 
measurements of latency, traceroutes and other things to quantify 
improvements in satellite based latency and other performance metrics 
over time. And to quantify what it looks like when an ISP previously 
dependent on geostationary (min 495ms latency) gains access to either 
terrestrial/submarine fiber, or a lower latency low earth orbit based 
service.


The best information I can find right now is to manually pick probes 
which never show below geostationary latency to a first hop in any 
traceroute, and are located on the probes map in certain island 
locations. It's a bit more time consuming to manually search for probes 
in continental locations which are on a VSAT (for instance if anyone 
knows of a probe on a VSAT terminal in a remote part of Wyoming, USA, 
let me know...).

Re: [atlas] Satellite based "last mile" and Atlas probes

[Ponikierski, Grzegorz via ripe-atlas]

This can be good for a start:

https://atlas.ripe.net//api/v2/probes/?tags=Satellite
https://atlas.ripe.net//api/v2/probes/?tags=VSAT

Funny thing is that 'VSAT' is not visible in 
https://atlas.ripe.net/api/v2/probes/tags/

Regards,
Grzegorz

From: "Ponikierski, Grzegorz" 
Date: Thursday 2021-04-22 at 21:52
To: Eric Kuhnke , "ripe-atlas@ripe.net" 

Subject: Re: [atlas] Satellite based "last mile" and Atlas probes

Hi Eric!

I'm not aware about such list but I would use API to get list of all probes and 
look for tags with "satellite" or "sat" in name. 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://beta-docs.atlas.ripe.net/built-in/reference.html#traceroute-5-000-6-999 
+ build in ping tests for 1st and 2nd hop are respectively measurement #1 and 
#2.

Regards,
Grzegorz

From: Eric Kuhnke 
Date: Thursday 2021-04-22 at 17:19
To: "ripe-atlas@ripe.net" 
Subject: [atlas] Satellite based "last mile" and Atlas probes

Hello all,

I am running what I believe to be the only probe on a Starlink satellite 
connection right now:

https://atlas.ripe.net/probes/1001821/

Is anyone aware of a list of probe ID numbers which are definitively known to 
be on some form of satellite-based access technology? I am thinking of, for 
instance, sites on consumer grade geostationary VSATs, more serious VSATs, or 
in island nations which are not known to have any submarine cables.

The reason why I am searching for such a list is that I intend to consume some 
of my accumulated credits to run periodic one-off measurements of latency, 
traceroutes and other things to quantify improvements in satellite based 
latency and other performance metrics over time. And to quantify what it looks 
like when an ISP previously dependent on geostationary (min 495ms latency) 
gains access to either terrestrial/submarine fiber, or a lower latency low 
earth orbit based service.

The best information I can find right now is to manually pick probes which 
never show below geostationary latency to a first hop in any traceroute, and 
are located on the probes map in certain island locations. It's a bit more time 
consuming to manually search for probes in continental locations which are on a 
VSAT (for instance if anyone knows of a probe on a VSAT terminal in a remote 
part of Wyoming, USA, let me know...).

Re: [atlas] Satellite based "last mile" and Atlas probes

[Ponikierski, Grzegorz via ripe-atlas]

Hi Eric!

I'm not aware about such list but I would use API to get list of all probes and 
look for tags with "satellite" or "sat" in name. 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://beta-docs.atlas.ripe.net/built-in/reference.html#traceroute-5-000-6-999 
+ build in ping tests for 1st and 2nd hop are respectively measurement #1 and 
#2.

Regards,
Grzegorz

From: Eric Kuhnke 
Date: Thursday 2021-04-22 at 17:19
To: "ripe-atlas@ripe.net" 
Subject: [atlas] Satellite based "last mile" and Atlas probes

Hello all,

I am running what I believe to be the only probe on a Starlink satellite 
connection right now:

https://atlas.ripe.net/probes/1001821/

Is anyone aware of a list of probe ID numbers which are definitively known to 
be on some form of satellite-based access technology? I am thinking of, for 
instance, sites on consumer grade geostationary VSATs, more serious VSATs, or 
in island nations which are not known to have any submarine cables.

The reason why I am searching for such a list is that I intend to consume some 
of my accumulated credits to run periodic one-off measurements of latency, 
traceroutes and other things to quantify improvements in satellite based 
latency and other performance metrics over time. And to quantify what it looks 
like when an ISP previously dependent on geostationary (min 495ms latency) 
gains access to either terrestrial/submarine fiber, or a lower latency low 
earth orbit based service.

The best information I can find right now is to manually pick probes which 
never show below geostationary latency to a first hop in any traceroute, and 
are located on the probes map in certain island locations. It's a bit more time 
consuming to manually search for probes in continental locations which are on a 
VSAT (for instance if anyone knows of a probe on a VSAT terminal in a remote 
part of Wyoming, USA, let me know...).

Re: [atlas] Satellite based "last mile" and Atlas probes

[Thomas Schäfer]

Am Donnerstag, 22. April 2021, 17:18:59 CEST schrieb Eric Kuhnke:
> Hello all,
> 
> I am running what I believe to be the only probe on a Starlink satellite
> connection right now:
> 
> https://atlas.ripe.net/probes/1001821/

Is there a certain reason, why you are without IPv6?

[atlas] Satellite based "last mile" and Atlas probes

[Eric Kuhnke]

Hello all,

I am running what I believe to be the only probe on a Starlink satellite
connection right now:

https://atlas.ripe.net/probes/1001821/

Is anyone aware of a list of probe ID numbers which are definitively known
to be on some form of satellite-based access technology? I am thinking of,
for instance, sites on consumer grade geostationary VSATs, more serious
VSATs, or in island nations which are not known to have any submarine
cables.

The reason why I am searching for such a list is that I intend to consume
some of my accumulated credits to run periodic one-off measurements of
latency, traceroutes and other things to quantify improvements in satellite
based latency and other performance metrics over time. And to quantify what
it looks like when an ISP previously dependent on geostationary (min 495ms
latency) gains access to either terrestrial/submarine fiber, or a lower
latency low earth orbit based service.

The best information I can find right now is to manually pick probes which
never show below geostationary latency to a first hop in any traceroute,
and are located on the probes map in certain island locations. It's a bit
more time consuming to manually search for probes in continental locations
which are on a VSAT (for instance if anyone knows of a probe on a VSAT
terminal in a remote part of Wyoming, USA, let me know...).

Re: [atlas] Filtering measurements

[Stephane Bortzmeyer]

On Thu, Apr 22, 2021 at 02:20:20PM +0200,
 Stephane Bortzmeyer  wrote 
 a message of 15 lines which said:

> I'm afraid you'll have to download the raw JSON file
> , parse it yourself and
> filter according to the "probes" array.

The small Python program attached gives an example.

% ./read.py meta-20210421.txt 50005
...
Measurement 29755186 uses the probe 50005
Measurement 29755187 uses the probe 50005
Measurement 29755701 uses the probe 50005
Measurement 29755702 uses the probe 50005
Measurement 29755704 uses the probe 50005
Measurement 29756177 uses the probe 50005
Measurement 29756178 uses the probe 50005
...

#!/usr/bin/python3

import json
import sys

filename = sys.argv[1]
probe = sys.argv[2]

f = open(filename)
for line in f.readlines():
data = json.loads(line)
mid = data["msm_id"]
for p in data["probes"]:
if str(p["id"]) == probe:
print("Measurement %s uses the probe %s" % (mid, probe))

Re: [atlas] Filtering measurements

[Stephen Strowes]

Hi,

On 22/04/2021 14:01, Sanaa GHANDI wrote:

For example, I want to get the results coming from sources: X and Y, and 
targeting the anchor 6771.


This kind of query can be where the public bigquery datasets are useful, 
because bigquery will let you walk through the result data directly. 
(Some details and pre-requisites are at [1,2]).


Something as simple as this query would be a good start for the question 
above:


> select distinct msm_id
> from `ripencc-atlas`.yesterday.traceroute
> where (prb_id = X or prb_id = Y)
> and   (af = 4 and dst_addr = "91.201.7.243")


Note we're expanding the available public datasets a bit from what's 
currently in the docs:


 * "yesterday" is a dataset that refers to measurements collected yesterday
 * "24hours" is a dataset referring to the most recent 24 hours
 * "samples" is a truly tiny dataset for prototyping and is great for
   getting started
 * "measurements" is most data reaching 18+ months back, and where you
   should definitely use a date filter in the query :-)

Depending on what you're trying to get out of the data, the above might 
be enough to get you started. Feel free to throw general questions here, 
or technical questions to atlas...@ripe.net



Cheers,

S.



[1] https://github.com/RIPE-NCC/ripe-atlas-bigquery
[2] 
https://github.com/RIPE-NCC/ripe-atlas-bigquery/blob/main/docs/gettingstarted.md







Now I can get the measures targeting the anchor 6771 using this code from Altas 
Cousteau

##
from ripe.atlas.cousteau import MeasurementRequest

filters = {'tags': ['anchoring','mesh',6771] }

measurements = MeasurementRequest(**filters)



But I have no idea of how to make a filter on the sources as well, since all we 
can access through the measurements are the number of anchors requested and not 
their ids.

Do you know a way to get access to the sources of a measurement via Atlas 
Cousteau or another Ripe Tool ?


Thank you

--
Sanaa

Re: [atlas] Filtering measurements

[Stephane Bortzmeyer]

On Thu, Apr 22, 2021 at 02:01:04PM +0200,
 Sanaa GHANDI  wrote 
 a message of 30 lines which said:

> But I have no idea of how to make a filter on the sources as well,
> since all we can access through the measurements are the number of
> anchors requested and not their ids.
> 
> Do you know a way to get access to the sources of a measurement via
> Atlas Cousteau or another Ripe Tool ?

I'm afraid you'll have to download the raw JSON file
, parse it yourself and
filter according to the "probes" array.

[atlas] Custom box and bag

[Slite]

​
Hello,



Have a nice day.



Does your company needs any Custom packaging box/bags for your products? 
We are Chinese supplier who can produce customized packaging/bag with custom 
logo.



Dear,we have cartons,cardboard box,plastic box,metal tin box,paper bag,plastic 
bag,non-woven bag ... to pack your products.




Then tell me which one you want,I will give you best price with good service.



Any of your reply will be appreciated.
Looking forward to your reply.



Best regards,
Slite


Contact Email: sl...@slcpackage.com 
What's app: 0086 15314679598SLC-PACKAGE CO. LTDwww.slcpackage.com
www.slcpackages.comContact Person: Slite Cao
 Address:1406, No 11,Dongyue Huayuan,Nancheng,Xinluo,Longyan,Fujian,China

If you no longer wish to receive mail from us, you can 

Unsubscribe

[atlas] Filtering measurements

[Sanaa GHANDI]

Hello, 

I hope you are all doing well.

I have a few questions concerning the measurements selection, and I am 
interested only on the anchoring mesh measurements.

In fact, for optimisation issues, I would like to be able to select only 
measurements of interest:

For example, I want to get the results coming from sources: X and Y, and 
targeting the anchor 6771.

Now I can get the measures targeting the anchor 6771 using this code from Altas 
Cousteau

##
from ripe.atlas.cousteau import MeasurementRequest

filters = {'tags': ['anchoring','mesh',6771] }

measurements = MeasurementRequest(**filters)



But I have no idea of how to make a filter on the sources as well, since all we 
can access through the measurements are the number of anchors requested and not 
their ids.

Do you know a way to get access to the sources of a measurement via Atlas 
Cousteau or another Ripe Tool ?


Thank you

--
Sanaa