Route object is an object created in Internet Routing Registry to specify the Autonomus System Number "ASN" that will propagate this exact IP prefix to Internet. It can also be used to give information about the organisation that advertises this prefix. Route objects are usually protected and only a person with the authorised password can change them.

Route objects are usually used by Internet Service Providers and Upstreams to validate that routes received from their peers are legitimate. This usually help eliminate routes hijacking if used by all providers. They don't eliminate the need for BGP configuration and advertisement.

An LIR may receive an additional allocation when about 80% of all the address space currently allocated to it has been used in valid assignments and/or sub-allocations. A new allocation can also be made if single assignment or sub-allocation requires more addresses than those currently held by the LIR.

An excellent Reverse Delegation "Mini-Howto" is available from the documents' section of our website here. You may also contact hostmaster@afrinic.net if you have properly followed the instructions in the document, and reverse delegation still looks broken/non-functional.

The AFRINIC Database provides mechanisms to control who can make changes in the database and what changes they can make. The distinction of "who" vs. "what" separates authentication from authorisation. The maintainer object serves as a container to hold authentication filters.

Until the launch of AFRINIC’s IRR in 2013, AFRINIC members used the RIPE IRR to register their objects. Now that AFRINIC has its own IRR, members are encouraged to populate it with their objects instead of using the RIPE IRR.

Members can check their free/used allocation via the MyAFRINIC member portal. A query from the whois database can also give an approximate "visual" impression of how much has been utilised, for example to return a list of all registered assignments from 10.0.0.0/16 block; you can use: