For the record, I think my probe was one of these. Initially I thought it was associated with some maintenance that I performed on my network. Turns out it was related to this thread. I reconnected the probe and several days later it successfully reconnected and seems to have remain connected.
John +1-484-962-0060 On May 17, 2017, at 06:41, Alun Davies <[email protected]<mailto:[email protected]>> wrote: A few points of clarification are warranted following the previous mail. The firmware alluded to in the previous email was released in February 2017. Since then, approximately 100 RIPE Atlas V1 probes have disconnected - about 15% of the total number of V1 probes on the network. The fix that is currently in the making is expected to be released in a month or so. If at that time you have still been unable to reconnect your V1 probe, you can then return your probe to be fixed. Alternatively, you may apply for a V3 probe by following the usual process as described here: https://atlas.ripe.net/get-involved/become-a-host/ Cheers, Alun Davies RIPE NCC On 16 May 2017, at 16:22, Alun Davies <[email protected]<mailto:[email protected]>> wrote: Hello all, Due to an unfortunate bug in a recently released probe firmware (version 4760), a number of RIPE Atlas V1 probes are not currently able to connect to the network. The bug leads to excessive memory fragmentation which impacts that V1 probes because they have no MMU and only 8 MByte worth of memory. For reasons that are not yet clear, the issue has only affected well below half of the V1 probes. We are working on a new firmware that will correct this issue, but probes that will not connect will need to be returned to the RIPE NCC in order for the fix to be carried out. Once the new firmware is ready, users can either return their V1 probes to us to be fixed, or request a V3 probe instead. Thank you to Wilfred Woeber for reporting this and requesting an update on the current issue with the V1 probes. Cheers, Alun Davies RIPE NCC
