Long REG_WAIT_UNTIL

RIPE Atlas
1

After an ISP outage, my probe is still offline

I observe this in the logs:

May 29 19:24:40 bboxgo4 ripe-atlas[1411]: 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
May 29 19:24:40 bboxgo4 ripe-atlas[1411]: ssh -p 443 ``atlas@193.0.19.247`` INIT
May 29 19:24:42 bboxgo4 ripe-atlas[1411]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780712682

What’s the source of the issue? Is there any way to check the status of the “reg server”?
Why is REG_WAIT_UNTIL so far in the future?

2

Hello,

Please provide an probe ID so I can check this status.

3

1009821 and 1009833 appear to be having issues

4

I see there is tag on the probe: system: On hold indicates that beyond these limits will not
be allowed to connect. It’s best to do this in a ticket to atlas@ripe.net with an explanation and we will consider relaxing this limit. We can follow-up (if we haven’t already) in a support ticket.

5

I’m affected as well, cannot get my probe (#1014833) to reconnect.

I get the same “reg server asked us to wait or there was an error. REG_WAIT_UNTIL” error

6

“Beyond these limits” - what limits? What’s being limited?

7

Hello, we recently added measures in this area - please see this FAQ entry: Managing Your Probe | RIPE Atlas Documentation