Removing Internet Routing
Registry Objects
ISP’s rely on the Internet Routing Registry (IRR) records to further validate the route announcements. To Avoid issues, make sure the IPv4 you purchase has all IRR and BGP records removed.
Removing Internet Routing Registry (IRR) Objects
Working through the Internet Routing Registry can be complicated. We have worked closely with the source registries over the years to develop a better method to properly clean up old route records. To get assistance from our team, please email info@brandergroup.net or contact us
If you prefer to try to tackle this project on your own, please follow the directions to remove all routing objects, announcements and BGP records for your IPv4 block
Open up IRR Explorer, and search the IPv4 block you want to transfer: http://irrexplorer.nlnog.net/search. You will likely see several listings on this page. If your entire IPv4 block is listed, including what you want to transfer out, you will want to clean up the records.
The columns will have several listed source registries that are hosting routing records. Some examples of source registries are: arin, radb, level3 and nttcom.
Removing Legacy Route Objects
If the message under the advice column says Not seen in BGP, but (legacy?) route-objects exist, consider clean-up , do the following:
- Open up http://www.irr.net/docs/list.html
- Select the respective source registry(s), there may be several listings in one row.
- Email each available address and ask them to remove the IPv4 route Object. Also call them next day to ensure they received your request
- The route object will be in https://www.radb.net/query?
- If there are multiple entries, you will have to look at source in the radb entry to determine which source registry to email the specific route object
- route:
- descr:
- origin:
- mnt-by:
- changed:
- source:
- If no route object exists in radb.net, just email the source registry asking them to remove any route objects for the entire IPv4 block.
Also in email the record listed in RADB https://www.radb.net/query?
- Email the listed email address located under the specific record
- Ask them to remove the entire IPv4 route object from their script. Include the entire route object
- route:
- descr:
- origin:
- mnt-by:
- changed:
- source:
If the message under the advice column says Multiple route-object exist with different origins, do the following:
- make sure both ASNs in the column under the source registry are active. If you are multi-homed, this is fine.
- If not, follow the steps above to remove the object for the ASN that shouldn’t be there
Removing BGP Announcements
In IRR Explorer, if it says Prefix in DFZ, but no route-object with correct origin anywhere or Looks good: BGP origin consistent with AS in route-objects
- Reach out to your upstream provider and ask them to stop announcing it. You will see their ASN listed next to the record.
- You can look up the contact details for the upstream provider here
- bgp.he.net
- input AS# into search
- in the tabs, click on Whois in the far right
