On 6/29/22 00:23, Michael Rabinovich wrote:
Looking forward to reading Emile’s paper, but in the meantime: Nick
Kernan, a graduate student of mine, wrote a python script for selecting
a geographically diverse set of probes from a list of probes.
The paper describes a similar approach, but usin
Hi Eric,
This gives you the list of probes that have a last-mile median RTT
(endpoint_type=LM&median__gte=495) higher than 495ms:
https://ihr.iijlab.net/ihr/api/network_delay/?timebin=2021-04-21T00%3A15&endpoint_type=LM&median__gte=495
Looks like probes 55562 and 1000244 are both in US and ove
Hi Eric,
Thanks for sharing that, I didn't know about that probe. I amazed by the
stability of its last mile RTT (see attached graph LM36492).
It looks like the probe is loosing connectivity to RIPE controllers once
in a while, do you know if this is caused by starlink or is it other
running
Another way is to setup a script listening at measurement id 7000. This
logs all the probes connection/disconnection to RIPE controllers.
Romain
On 12/13/20 6:14 AM, Colin Johnston wrote:
+one from me, asked that this functionality be added 5 years ago.
On 12 Dec 2020, at 09:55, Gert Doerin
onnection flips.
I will be back to you.
wbr
/vty
On 3/11/20 6:04 AM, Romain Fontugne wrote:
Hi,
I found that the following probes are reported disconnected for
several hours a day, more or less at the same time, but all their
built-in measurements are there and seem normal:
https://atlas.r
Hi,
I found that the following probes are reported disconnected for several
hours a day, more or less at the same time, but all their built-in
measurements are there and seem normal:
https://atlas.ripe.net/probes/32639/#!tab-network
https://atlas.ripe.net/probes/28818/#!tab-network
https://at
my non-scientific comparison: looking at RTTs in traceroutes the old v1
seems a msec slower. All are very stable
Romain
On 2/14/20 4:12 AM, Randy Bush wrote:
if someone wants to compare, 4981 (a lovable old v1), 104, and
106 are on the same lan segment in the same pop with the same vr
