You are here: Home > Manage IPs and ASNs > RIPE Database > FAQ: RIPE Database > FAQ: Status Values and Legacy Resources > RIPE Database Operations-Related Questions

RIPE Database Operations-Related Questions

Show or Hide answer Will the “status:” of an AUT-NUM object affect my routing policy or peering agreements?

No. The status of an aut-num is only administrative. It does not affect the usage of an aut-num for any routing purpose.

Show or Hide answer Does the “status:” of an AUT-NUM object affect the creation of ROAs for any certified address space?

No. The status of an aut-num is only administrative. It does not affect the usage of an aut-num for any routing purpose.

Show or Hide answer Will these status changes have any impact on the services I provide using these legacy resources?

No. There will be no interruption to your services as a result of these changes or any long-term impact. It will not affect your routing or reverse delegations.

Show or Hide answer Can I change the “status:” value ‘LEGACY’ on my INETNUM and AUT-NUM objects to something else?

No. As long as it remains a legacy resource, the “status:” value will be ‘LEGACY’ and users are unable to change it.

Show or Hide answer When my AUT-NUM object is being updated, can I manually select the value of the “status:” attribute?

No. With any update, we will generate the correct “status:” attribute value of this aut-num object. The single correct value (‘ASSIGNED’, ‘LEGACY’, or ‘OTHER’) will be added, regardless of any value supplied or not supplied by the user.

Show or Hide answer I made a sub-allocation with “status:” ‘SUB-ALLOCATED PA’ for another organisation from my top-level legacy resource. How can I show this change of responsibility now?

As long as it remains legacy space you cannot show this now using status. It all has the same “status:” of ‘LEGACY’. However, this is what the organisation object is for. You can reference your own organisation object from your top-level legacy resource. You can also reference the organisation object for the other organisation from the sub-allocation object you created. This will show that a different organisation has taken responsibility for this resource and all more specifics to this resource. When looking at the data objects listed in the RIPE Database, the responsible organisation(s) may be hard to interpret. RIPE Database tools developed by the RIPE NCC to provide information, will understand the organisational relationship and will make decisions on that.


You also have the option to convert your top-level legacy resource to ‘ALLOCATED PA’ and then you can have a ‘SUB-ALLOCATED PA’ object as a more specific.

Show or Hide answer Can I still create hierarchies of objects for customers and other organisations more specific to my top-level legacy resource?

Yes. You can build any hierarchy more specific to your top-level legacy resource. You can still partition your address space, make sub-allocations and assignments. The only difference is they will all have the same “status:” of ‘LEGACY’. You can show responsibility by references to organisation objects in appropriate places. Hierarchical authorisation still applies in the same way. For example, a sub-allocation object will still be maintained by you with the “mnt-lower:” set to the mntner of the other organisation.

Show or Hide answer I tried to update my AUT-NUM object and it failed. Is this failure related to the new “status:” attribute?

No. Updates to an aut-num object will never fail because of the new "status:" attribute, only because of clear syntax errors- for example, misspelling the attribute name.

Show or Hide answer Now that a new mandatory "status:" attribute has been introduced to the AUT-NUM object, should I make any changes to my scripts?

There is no need to make any changes to scripts that auto-generate an aut-num object from your own routing data. You may only need to change your scripts if you query your aut-num from the RIPE Database as a starting point for your new object generation. Your query/lookup script will need to be tolerant to the new attribute.


In the long term, it is better if you update your scripts to keep in line with syntax and business rule changes to the RIPE Database. However, there is no urgent need to change anything regarding status.

Show or Hide answer How do I know what the status of my AUT-NUM object should be?

All existing aut-num objects have been updated by the RIPE NCC with the correct value. Any new aut-num objects created by the RIPE NCC or other users will have the correct value, generated by the software. The “status:” attribute cannot be removed, or have its value changed by users or the RIPE NCC. The software will always generate it with the correct value on any update.

Show or Hide answer What happens if my script generates an AUT-NUM object without the mandatory “status:” attribute?

The software will generate the correct value and add the attribute to your object. If you submit an update with the value changed, the software will change it back to the correctly generated value. Neither of these cases will trigger an update error, but will add a warning to the acknowledgement message.

Show or Hide answer Who maintains the legacy resource data in the RIPE Database?

As far as RIPE Database authorisation rights are concerned, all legacy resource objects will be maintained by the legacy resource holders. The RIPE NCC will not have any normal maintainer access rights. However, as RIPE Database administrators, the RIPE NCC can assist legacy resource holders, where necessary.

Show or Hide answer An INETNUM object was created in the RIPE Database for my legacy resource many years ago. How do I get access to update this object?

During the Early Registration Transfer project in 2003/2004, many legacy resources were transferred from the ARIN Database to the RIPE Database. The RIPE NCC auto-generated mntner objects for these resources. A process was set up for the legacy resource holders to get the password for these mntner objects. If you have not yet requested your password, please contact for assistance. You will need to provide some evidence that you are the legacy resource holder.

Show or Hide answer I need to change the reverse delegation or routing information in the RIPE Database for my legacy resource. How do I get access to these objects?

It may be that these objects, and perhaps your legacy resource objects, still have the auto-generated mntner objects on them from the Early Registration Transfer project of 2003/2004. Or, someone else may have set up this information in the RIPE Database many years ago and you no longer have the password. In either case, please contact for assistance. You will need to provide some evidence that you are the legacy resource holder.

Show or Hide answer Do I need an ORGANISATION object?

The RIPE Database structure is modeled on the principle that resources are held by organisations. In this context, individuals are seen as organisations. One of the aims of ripe-605, "RIPE NCC Services to Legacy Internet Resource Holders" is to accurately reflect details of legacy resources in the public RIPE Database as part of the RIPE Registry. You should create an organisation object to show who is holding this legacy resource and to maintain consistency in RIPE Database structure.

Show or Hide answer Do I need an “abuse-c:” attribute?

Yes. All resources documented in the RIPE Database must have a referenced abuse contact.

Show or Hide answer I have a question about status values that is not answered by this FAQ. What should I do?

If your question is related to the introduction of the “status:” attribute in aut-num objects and/or the change in the value of the “status:” attribute of inetnum objects to ‘LEGACY’, please contact  You will receive an auto-response acknowledging your question. The RIPE NCC will collect these questions and may update this FAQ by adding questions, along with the appropriate, corresponding answers.