Hello Ernst,

From the top of my head, the system-generated tags are done based on internal measurements the probe does. 

CTR-HEL09 has had a reboot about 3 days ago, and your probe seems to connect to CTR-HEL09 mostly, so that would explain that disconnect. I am not sure the tagging is related to the connection with the controller being lost, it’s more likely that one of the internal measurements did not get the expected response and concluded IPv4 wasn’t stable enough. It seems to have resolved, just now the probe showed as being stable again.

Hope this helps. Let me know if you need me to dig a bit further.

Regards,

Michel

On 3 Aug 2023, at 22:43, Ernst J. Oud <ernstoud@gmail.com> wrote:

Hi, 

Further to my question; checked my logs and on at the date/time the connection history of this probe is reported as “disconnected” (2023-08-01 06:41:54 UTC) there was no problem whatsoever on my internet connection.

So why was the probe disconnected? I see that status for my probes quite a lot, is it the controller (ctr-hel09) that needs to go get a beer or what?

Regards,

Ernst J. Oud

On 3 Aug 2023, at 22:33, Ernst J. Oud <ernstoud@gmail.com> wrote:

I noticed that the system tag “IPv4 stable 1d” is gone from my probe at:


I use that tag as a criteria to select active probes for measurements. But I noticed that my own probe was not included in my measurements.

Which is weird since my probe has been online for 2.5 days (normally it is more stable, but my ISP had a small downtime).

So my question is what triggers this tag? The tag is self explanatory but what does “stable” mean?

Regards,

Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas