Verify IRR entries
Verify your Internet Routing Registry (IRR) entries to ensure that the IP prefixes Cloudflare advertises for you match the correct autonomous system numbers (ASNs).
Each IRR entry record must include the following information:
- Route: each IP prefix that Cloudflare advertises for you.
- Origin AS: your ASN, or if you do not have your own ASN, the Cloudflare ASN (AS209242).
- Source: the name of the routing registry—for example, AFRINIC, APNIC, ARIN, RADB, RIPE, or NTT.
- The entry is missing.
- The entry is incomplete or inaccurate—for example, when the route object does not show the correct origin.
- The entry is complete but requires updating—for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit.
IRR entry verification methods
To verify your prefix and ASN route, use the tools and methods outlined in this table:
WHOIS output example
<IRR entry section> in the WHOIS output shows the correct IRR entry information for the specified network. In this example, the network prefix is 188.8.131.52/24, and the output includes the route, origin ASN, and route registry, which in this example is APNIC:
user@xxt32z conduit-qs-config % whois -h rr.ntt.net 184.108.40.206/24route: 220.127.116.11/24<RPKI section>descr: RPKI ROA for 18.104.22.168/24remarks: This route object represents routing data retrieved from the RPKIremarks: The original data can be found here: https://rpki.gin.ntt.net/r/AS13335/22.214.171.124/24remarks: This route object is the result of an automated RPKI-to-IRR conversion process.remarks: maxLength 24origin: AS13335mnt-by: MAINT-NTTCOM-RPKIchanged: firstname.lastname@example.org 20200913source: RPKI # Trust Anchor: apnic <IRR entry section>route: 126.96.36.199/24origin: AS13335descr: APNIC Research and Development 6 Cordelia Stmnt-by: MAINT-AU-APNIC-GM85-APlast-modified: 2018-03-16T16:58:06Zsource: APNIC