Since maintenance is completed, you broke for me at 04:30PM this afternoon localtime Philippines/Manila (PHT)
I tried refer this guide for help. Nothing changed in my network and the probe can’t reconnect to reg-server.
Log:
RESULT 9006 done 1780654876 000acd00076b no reginit.vol start registration
/probe/var/run/ripe-atlas/status/reginit.vol does not exist try new reg
Ping failed
start reg
ATLAS registration starting
REASON_FOR_REGISTRATION NEW NO previous state files
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@193.0.19.247 INIT
reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780655001
Moving reboot-count.txt
RESULT 9006 done 1780655059 000acd00076b no reginit.vol start registration
/probe/var/run/ripe-atlas/status/reginit.vol does not exist try new reg
Ping failed
start reg
ATLAS registration starting
there is WAIT, REG_WAIT_UNTIL , now is 1780655060
REG_WAIT_UNTIL expired go re-reg 1780655001 now 1780655060
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@193.0.19.247 INIT
reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780655191
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/v6addr.txt' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/simpleping' exists
Event Log is listing a ton of SOS messages as well:
It’s been disconnected now for 3 hours 
Has anyone faced similar problem?
Any guidance or suggestions from the community would be greatly appreciated.
Thank you! 
2 Likes
I’m affected as well, cannot get my probe (#1014833) to reconnect:
ripe-atlas-1 | RESULT 9006 done 1780733218 6c4b90a282a4 no reginit.vol start registration
ripe-atlas-1 | /run/ripe-atlas/status/reginit.vol does not exist try new reg
ripe-atlas-1 | Ping works
ripe-atlas-1 | start reg
ripe-atlas-1 | ATLAS registration starting
ripe-atlas-1 | there is WAIT, REG_WAIT_UNTIL , now is 1780733221
ripe-atlas-1 | REG_WAIT_UNTIL expired go re-reg 1780733152 now 1780733221
ripe-atlas-1 | 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
ripe-atlas-1 | ssh -p 443 atlas@193.0.19.247 INIT
ripe-atlas-1 | reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780733344
ripe-atlas-1 | condmv: not moving, destination '/var/spool/ripe-atlas/data/out/v6addr.txt' exists
ripe-atlas-1 | condmv: not moving, destination '/var/spool/ripe-atlas/data/out/simpleping' exists
1 Like
I seem to be affected as well (Probe 1002411). I only recently got it to work properly, so it might still be some local issue. I noticed that my probe wasn’t sending results after 05:30 CEST (this could very well be a local problem :), but was still connected. After restarting, it’s unable to register (same error message as above: `Jun 06 15:51:17 rocky ripe-atlas[160871]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780754001`)
Also, 4 other probes from my AS with stable-30d-tags dropped offline this morning as well ( RIPE Atlas - RIPE Network Coordination Centre ).
Same issue with three of my four software probes. All four were connected until 04:00 UTC today, when I rebooted three of them. They didn’t reconnect afterwards and are still offline. The one which wasn’t rebooted is still online.
Looking at the list of all probes, it seems like these registration servers went down again about 90 minutes after the end of maintenance. Most probes which are currently online connected between 08:45 and 10:15 UTC yesterday. After that, basically nothing.
1 Like
Same issue here. I rebooted my software probe today at about 17:30 UTC and it hasn’t reconnected since.
same here with probe #1013719
I get a REG_WAIT_UNTIL from reg03/reg04
My probe successfully reconnected about 1h ago
2 Likes
Same, all of my probes reconnected between 18:38 and 18:40 UTC.
1 Like
I seem to be successfully reconnected since 06/08/2024 02:38AM (PHT) (06/07/2026 18:38:39 (UTC)) but there is drawbacks:
- Probe 1009225 and 1009707 was connected for couple hours today but in a disconnect state and unable to reconnect again with no reason!
- Other probes were unable to reconnect are affected as well
Probe 1009859 and 1009860 also back to normal and now it’s still stable for 5 hours 
Is there a special problem with sw-probes? Should we update for force controller change?
I really hope the RIPE team will be able to correct the problem to the probes to reconnect, otherwise it doesn’t even make sense to keep the affected probes running as the data is now completely useless.
Indeed we had an issue over the weekend. The situation is improving but it’s not full resolved yet. We have a status page entry about it: RIPE NCC Status - RIPE Atlas software probes degradation
3 Likes
