Another thought on the template: The "Status" tab on a probe's page no longer seems to exist, so it cannot give more details about why the probe disconnected, and the corresponding URL redirects to the probe's generic "Overview" tab.
07.06.2026 22:24:04 Marek Küthe via ripe-atlas <[email protected]>: > Shortly after I posted this message, my second sample went offline as > well. Today I received emails saying they were reconnected. Just now I > got another email saying the samples are disconnected again. > > A suggestion from me: Maybe adjust the email template a bit: If it’s a > controller issue, add a note saying, 2The problem isn’t on your end, > but on ours. We’re working on a solution." or something like that. > > On Fri, 5 Jun 2026 22:14:45 +0000 > Marek Küthe via ripe-atlas <[email protected]> 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] ----- 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/
