Unable to Register Objects

This can occur for several reasons:

• The unique fields of the object you are trying to register already exist in RADb.

• The object was registered by a previous owner of the ASN or prefix and was never removed.

• The object was registered on behalf of your organization by an upstream provider.

• The object was registered by a bad actor.

If you believe this error is incorrect, please contact RADb Support.

They will investigate the issue and take corrective actions if needed.

• This error message usually means that there is either an issue with the mntner object or the maintainer password.

• An invalid admin-c / tech-c attribute in the mntner object will cause this.

• Replacing the admin-c / tech-c with a valid nic-hdl or DUMMY-RADB can fix this.

• If that does not work, contact RADb Support to reset your maintainer password

• This error means that there is an admin-c / tech-c attribute that does not have a role / person object with a referencing nic-hdl in RADb

• This can be fixed by added the role / person object or replacing those attributes with DUMMY-RADB

• If you are unable to register the role / person object, contact RADb Support

• This error means that the RPKI ROA on the IP/ASN conflicts with the object you are trying to register.

• The IP/ASN holder needs to contact the relevant RIR to correct or remove the ROA.

• Once the RIR updates the ROA, it may take up to 2 hours for our system to reflect the changes.

If the object you are creating has the same name as an existing object, it means that the new object isn’t properly scoped.

• RADb uses a global namespace, so each object name must be unique.

• To prevent conflicts, objects should be named in a hierarchical format.

Example:

Instead of using a general name like AS-CUSTOMERS, scope it using your ASN, like:

• AS64496:AS-CUSTOMERS

This approach reduces the risk of name collisions, as it uniquely identifies your object within the global RADb namespace.