Hi,

Same here. Three of my software probes have disconnected this morning. Nothing 
wrong with internet at those locations. One of these locations also has a 
hardware probe that runs fine.

In the logs it says:

—-
/var/atlas-probe/status/reginit.vol does not exist try new reg
Ping failed
start reg
ATLAS registration starting
there is WAIT, REG_WAIT_UNTIL  , now is 1780758142
 REG_WAIT_UNTIL expired go re-reg 1780758077 now 1780758142
REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 
reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7
ssh -p 443 atlas@2001:67c:2e8:11::c100:13f6 INIT
255  REGINIT exit with error
condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists
condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists
—-

Something definitely wrong with the controller infra!

Regards,

Ernst J. Oud

> On 6 Jun 2026, at 14:16, via ripe-atlas <[email protected]> wrote:
> 
> Hi,
> 
> Same thing is affecting five of my probes since yesterday, also with repeated 
> messages of being asked to wait, or there having been an error:
> 
> 2026-06-06T12:13:24.673341015Z reg server asked us to wait or there was an 
> error. REG_WAIT_UNTIL 1780748131
> 
> I understand that you "updated [y]our controllers so all probes disconnected 
> for a short while" yesterday, but that is now more than a day ago?
> 
> Thanks!
> 
> Kind regards,
> 
> R.
> 
>> On 6/6/26 00:14, Marek Küthe via ripe-atlas wrote:
>> Hello,
>> My probe has disconnected. Could someone take a look at this?
>> The message in the log is as follows:
>> ```
>> Jun 06 00:12:48 laplace ripe-atlas[113935]: condmv: not moving, destination 
>> '/var/spool/ripe-atlas/data/out/simpleping' exists
>> Jun 06 00:12:48 laplace ripe-atlas[113934]: condmv: not moving, destination 
>> '/var/spool/ripe-atlas/data/out/v6addr.txt' exists
>> Jun 06 00:12:48 laplace ripe-atlas[113915]: reg server asked us to wait or 
>> there was an error. REG_WAIT_UNTIL 1780697679
>> Jun 06 00:12:47 laplace ripe-atlas[113915]: ssh -p 443 [email protected] 
>> INIT
>> Jun 06 00:12:47 laplace ripe-atlas[113915]: REGHOSTS reg03.atlas.ripe.net 
>> 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 
>> 2001:67c:2e8:11::c100:13f7
>> Jun 06 00:12:47 laplace ripe-atlas[113915]:  REG_WAIT_UNTIL expired go 
>> re-reg 1780697510 now 1780697567
>> Jun 06 00:12:47 laplace ripe-atlas[113915]: there is WAIT, REG_WAIT_UNTIL  , 
>> now is 1780697567
>> Jun 06 00:12:47 laplace ripe-atlas[113915]: ATLAS registration starting
>> Jun 06 00:12:47 laplace ripe-atlas[1356]: start reg
>> Jun 06 00:12:47 laplace ripe-atlas[1356]: Ping works
>> Jun 06 00:12:44 laplace ripe-atlas[1356]: /run/ripe-atlas/status/reginit.vol 
>> does not exist try new reg
>> Jun 06 00:12:44 laplace ripe-atlas[1356]: RESULT 9006 done 1780697564 
>> 901b0e4bf9d8 no reginit.vol start registration
>> ```
>> I've attached the last 200 lines of the log.
>> Best regards,
>> Marek Küthe
>>> On Fri, 05 Jun 2026 17:00:00 +0000
>>> "RIPE Atlas" <[email protected]> wrote:
>>> ###Probe 1008669 is disconnected ()
>>> 
>>> 
>>> Marek Küthe,
>>> 
>>>  
>>> Your probe 1008669 has been disconnected from the RIPE Atlas infrastructure 
>>> since 2026-06-05 16:25:47 UTC.
>>> 
>>> You may be able to learn more about the possible cause from the "Status" 
>>> tab on your probe's information page:
>>> 
>>> https://atlas.ripe.net/probes/1008669/#!tab-status
>>> 
>>> Probes are tagged with suspected problems every four hours, so if there is 
>>> nothing listed under the Status tab and your probe has just gone offline, 
>>> please check back in a few hours, as more information may be available.
>>> 
>>> If you need further assistance or have any questions, please contact us at 
>>> [email protected].
>>>  
>>> Best regards,
>>> The RIPE Atlas Team
>>> 
>>> **RIPE NCC**
>>> 
>>> Stationsplein 11, 1012 AB, Amsterdam
>>> 
>>> This email was sent to [email protected]
>>> 
>>> You've received this email because you are registered as a RIPE Atlas probe 
>>> host.
>> -----
>> To unsubscribe from this mailing list or change your subscription options, 
>> please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
>> As we have migrated to Mailman 3, you will need to create an account with 
>> the email matching your subscription before you can change your settings.
>> More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
> 
> -----
> To unsubscribe from this mailing list or change your subscription options, 
> please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
> As we have migrated to Mailman 3, you will need to create an account with the 
> email matching your subscription before you can change your settings. More 
> details at: https://www.ripe.net/membership/mail/mailman-3-migration/
-----
To unsubscribe from this mailing list or change your subscription options, 
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the 
email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/

Reply via email to