Cloudflare Docs
Edit this page on GitHub
Set theme to dark (⇧+D)

Best practices for IRR entries

An Internet Routing Registry (IRR) record is what notifies internet service providers (ISPs) of how you are allowing your resources to be used. It is necessary to keep your IRR entries up to date so that it is public information that Cloudflare has permission to advertise your prefix or prefixes and to ensure that your traffic can be properly routed on the internet.

The American Registry for Internet Numbers (ARIN) maintains an IRR that allows registrants of AS numbers and IP addresses to publish that information so that ISPs can make appropriate routing decisions. This helps ensure ISPs will recognize your routes as legitimate and enables them to ignore unauthorized routes published by someone else.

​​ Configure an IRR entry

You can add or update an IRR entry by following the directions within any of the recommended internet registries listed in the Internet Routing Registry.

If you own your own subnet, use the RIPE and APNIC routing registries. These registries allow you to verify subnet ownership.

If you lease your subnet, follow these guidelines:

  • When you do not need ownership verification, use the AFRINIC or NTT routing registry.
  • When you submit a route object via email, use the ARIN registry. Address blocks owned by others do not appear in the ARIN interface.

The recommended registries are AFRINIC, APNIC, ARIN, NTT, RADB, and RIPE.

Each routing registry has its own set of instructions to configure an IRR entry. Refer to the table below for more information.

​​ Verify an IRR entry

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 Cloudflare advertises for you.
  • Origin ASN: 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.

Add or update IRR entries when they meet any of these criteria:

  • 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.

You are strongly encouraged to verify IRR entries for the exact prefixes you will use to onboard with Cloudflare.

IRR entries for less specific prefixes are acceptable as long as you understand and accept the following risk: if you modify your IRR entries in the future (for example, by changing your ASN) and the IRR entry for the supernet no longer matches the prefix or origin mapping in your Magic Transit configuration, the prefix will have reduced reachability due to networks Cloudflare peers with automatically filtering the prefix. Having specific IRR entries helps minimize (but not entirely remove) this risk.

​​ IRR entry verification methods

To verify your prefix and ASN route, use the tools and methods outlined on the table below:

Data to verifyToolMethodOutput
Subnet prefix IP
for the ASN
IRR ExplorerSearch for the subnet prefix IP, for example, of ASN numbers, source (route registry), and any associated errors.
ASN for the
subnet prefix
IRR ExplorerSearch for the ASN, for example AS209242.List of prefixes, source, and any associated errors.
Your origin ASN
and routing data
WHOIS lookup

In a terminal, use this whois command, substituting your network prefix for network-prefix:

whois -h network-prefix

The host is the primary server for the Global IP network.

IRR route, origin, and source information.

​​ WHOIS output

The <IRR entry section> in the WHOIS output shows the correct IRR entry information for the specified network. In this example, the network prefix is, and the output includes the route, origin ASN, and route registry, which in this example is APNIC:

user@xxt32z conduit-qs-config % whois -h
<RPKI section>
descr: RPKI ROA for
remarks: This route object represents routing data retrieved from the RPKI
remarks: The original data can be found here:
remarks: This route object is the result of an automated RPKI-to-IRR conversion process.
remarks: maxLength 24
origin: AS13335
changed: [email protected] 20200913
source: RPKI # Trust Anchor: apnic
<IRR entry section>
origin: AS13335
descr: APNIC Research and Development
6 Cordelia St
last-modified: 2018-03-16T16:58:06Z
source: APNIC