How to create a route object when the matching IP range is not allocated or assigned from the RIPE NCC?

Before creating the route object, the "origin" AS number object must be created in the RIPE Database, even if the AS number is registered in another whois database. If you are the party that has been assigned this AS number, please create the corresponding aut-num object by using the aut-num template. If the AS number is assigned to another party, please contact them to create the aut-num object.

To authenticate successfully for the IP space, you need to include the password for RIPE-NCC-RPSL-MNT, along with the passwords for the maintainer of the aut-num and actual route object.

The RIPE-NCC-RPSL-MNT clear text password is mentioned in the object itself:

mntner:     RIPE-NCC-RPSL-MNT
descr: This maintainer may be used to create objects to represent
descr: routing policy in the RIPE Database for number resources not
descr: allocated or assigned from the RIPE NCC.
<snip>
remarks: *******************************************************
remarks: * The password for this object is 'RPSL', without the *
remarks: * quotes. Do NOT use this maintainer as 'mnt-by'. *
remarks: *******************************************************
<snip>

The mnt-by: attribute of the route object should refer to your own maintainer object. Do *not* use RIPE-NCC-RPSL-MNT as the maintainer of the route object; the route object will not be protected with this public maintainer.