How IP Lessees Can Change/Update Subnets in the IPXO Marketplace
Discover what changes/updates you, as an IP lessee in the IPXO Marketplace, can request for the subnets you rent.
As a Marketplace client, you can change/update subnets at IPXO. Most subnets can be updated using the same procedures, regardless of whether they are allocated by AFRINIC, APNIC, ARIN, LACNIC or RIPE NCC. If there are any exceptions for what can and cannot be changed, our team can provide you with more information individually.
IPXO Marketplace clients can use subnets in many different geolocations, and they can also request to have the geolocation updated according to their needs. We send geolocation update requests to MaxMind, IP2Location, DB-IP and IPinfo databases.
Use our IP geolocation guide to learn more about IP geolocation.
The subnet’s Whois information changes are possible for the following data:
- Admin-c/Tech-c (depending on RIR)
- Desc/Remarks (depending on RIR)
- Geolocation (depending on RIR)
- Netname/Name, ORG
Note: Depending on the Regional Internet Registry, changes of additional fields may be possible too.
Here’s an example of Whois information provided by AFRINIC. To demonstrate an example, we use the subnet 18.104.22.168/24.
Here’s an example of Whois information provided by APNIC. To demonstrate an example, we use the subnet 22.214.171.124/24.
Here’s an example of Whois/RDAP information provided by ARIN. To demonstrate an example, we use the subnet 126.96.36.199/24.
Here’s an example of Whois information provided by LACNIC. To demonstrate an example, we use the subnet 188.8.131.52/23.
Here’s an example of Whois information provided by RIPE NCC. To demonstrate an example, we use the subnet 184.108.40.206/24.
Note: Whether or not changes are possible also depend on the subnet’s status/nettype. For example, it is not possible to change the netname and org attributes of a RIPE NCC subnet that has the Allocated PA status.
ROA and Route Object
If you want to have ROA, Whois route object or RADB route object created, you have to assign the subnet to a specific ASN. Follow the instructions below to learn how to do it.
How to assign a subnet to a specific ASN
Step 1: Access the My Leased IPs menu
Log in to the IPXO Portal and go to My Resources (IPAM) -> My Leased IPs.
Step 2: Click Assign
Identify the subnet you want to assign and click the Assign button on the right.
Step 3: Provide assignment information
- Enter the Company name (e.g., IPXO).
- Add the ASN (autonomous system number) of the AS Organization (e.g., 834).
- Check the boxes if you want to create ROA, Whois route object and/or RADB route object.
- Add any Additional information regarding the data you want us to change/update.
- Click Confirm once you fill out the form.
Note: You can add as many ASNs as you want. However, keep in mind that you have to pay $9 per ASN.
Once the assignment is complete, you will receive the LoA (Letter of Authorization) document. You can find and download it from My Resources (IPAM) -> My Leased IPs -> LoA.
IPXO is currently working on the automated rDNS feature, which will enable you to make changes yourself. Until the feature is fully implemented and available for the clients of the IPXO platform, you have to contact us directly if you want a subnet to be delegated to your nameserver. To make a request, contact us via the IPXO Help Desk.
Note: If you want us to update the nameservers, make sure you set them up first. Here’s an example of a nameserver delegation in RIPE.
If you have any questions, feel free to contact us via the IPXO Help Desk.
Still need help?
Get involved in the IPXO Slack community.Ask the IPXO community
If you have any questions, contact our support team!