[atlas] New on RIPE Labs: Another Look at RIPE Atlas Probe Lifetimes

Hi,

i noticed another problem besides the hardware, the "controllers" are 
not really highly-available? (E.g. ctr-ams07, NL)

Sometimes the probes are disconnected from a RIPE controller for some 
time even though there is no absolutely no network issue at the probes 
site. I suppose this could happen from time to time but it's too often. 
(Maybe it's just me, maybe everyone should check the connection history 
at RIPE atlas).

Also if a controller is not working sometimes it seems to take forever 
until the probe will use a failover controller and in the meanwhile its 
"disconnected"... Any chance to improve the availability?


Best Regards


Max M.


On 25.08.2016 16:37, Colin Johnston wrote:
> maybe virtual vm probes might be useful to investigate and also a split file system for v3 probs with /var/log on a different file system ?
>
> Colin
>
>> On 25 Aug 2016, at 15:30, Mirjam Kuehne <mir at ripe.net> wrote:
>>
>>
>> Dear colleagues,
>>
>> We took another, more detailed look at probe lifetimes and the dynamics
>> of probes connecting and disconnecting from the RIPE Atlas
>> infrastructure to try to understand how to keep the network growing in
>> the long term.
>>
>> https://labs.ripe.net/Members/wilhelm/another-look-at-ripe-atlas-probe-lifetimes?pk_campaign=labs&pk_kwd=list-mat
>>
>> Kind regards,
>> Mirjam Kuehne
>> RIPE NCC
>>
>