Quick Guide to Requesting
Resources from ARIN
1. Review “Qualifying for Resources” below to verify you qualify
for the requested resources.
2. Read the applicable policies in ARIN’s Number Resource
Policy Manual (NRPM) at [Link]
policy/nrpm/. The relevant NRPM section for each resource is
listed below.
3. Create an ARIN Online account at [Link] by
clicking on the Log in link at the top of the page. On the
ARIN Account Manager page, click on the Create a user
account link.
4. Log in and select Create a new Point of Contact (POC) from
your Dashboard or link to a published Point of Contact (POC).
5. Click on Create a new Organization Identifier (Org ID) from
your Dashboard to request an Org ID if you don’t already
have one.
6. Click either IP Addresses or ASNs, then click Request from the
Account Manager navigation bar .
7. Click the Org ID you want to request resources for and
complete the appropriate request form.
8. An ARIN Customer Service Resource Analyst will contact you
via your ARIN Online ticket to verify you qualify for the
requested resource.
9. You can submit general questions or request assistance
using the Ask ARIN feature through ARIN Online. If you have
specific questions about your request, you should send them
through your Message Center on the request ticket.
Updated September 2023
Updated September 2023
Qualifying for Resources
This is an overview of the criteria that organizations need to meet to be eligible to receive
specific types of resources directly from ARIN, as outlined in the Number Resource Policy
Manual (NRPM). This document is intended to provide a quick-reference to eligibility
requirements, and is not an authoritative document. The NRPM is the only document of
record regarding Internet number resource policy at ARIN. To submit a request for any
Internet number resource from ARIN, the appropriate registration form must be completed
IPv4 Address Space – Initial Allocation (use ISP Network Request form)
Type of Resource Request Criteria to Receive Resources
ISP Initial allocation • All ISP organizations without direct
/24 minimum allocation assignments or allocations from ARIN qualify
NRPM 4.2.2 for an initial allocation of up to a /22, subject
to ARIN’s minimum allocation size.
ISPs renumbering out of their previous • All ISP organizations without direct
address space will be given a allocations, direct assignments,
reasonable amount of time to do so, re-allocations or reassignments
and any blocks they are returning will automatically qualify for a /24.
not count against their utilization. These organizations are exempt from
requirements of showing the efficient
utilization of previously held IPv4 space.
These organizations may qualify for a larger
than a /24 by documenting how the
requested allocation will be utilized within
the request size specified in [Link].
• ISPs holding re-allocations and/or
reassignments must show the efficient
utilization of their resources consistent with
the requirements in sections 4.2.3 and 4.2.4.
Multiple Discrete Networks • Demonstrate your organization is a single
NRPM 4.5 entity and not a consortium of smaller
independent entities
• Provide verification your organization has
two or more discretely routed networks
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
• Provide detailed records on how you’ve
allocated space to each discrete network,
including the date of each allocation
• Demonstrate 50% utilization of both your
last allocation and of all allocations (over-all)
OR demonstrate all free blocks are smaller
than ARIN’s minimum allocation
IPv4 Address Space – Additional Allocation (use ISP Network Request form)
Type of Resource Request Criteria to Receive Resources
ISP Additional Allocation • Demonstrate at least 50% of each of
NRPM 4.2.4 your allocations is efficiently used
• Demonstrate at least 80% of the sum of
all allocations is efficiently used
• Provide reassignment information for
all customer reassignments of eight or
more contiguous IP addresses via SWIP
or RWhois
• Provide reassignment information
in text or spreadsheet format for all
customer assignments less than eight
contiguous IP addresses
• List of CIDR prefixes/ranges assigned to
dynamic pools with service type (e.g.
DSL, wireless), city/region served, peak
utilization percentage, and number of
customers served for each pool
• List of IP addresses used for web hosting
along with at least one customer
domain name hosted on each IP address
• List of IP addresses/subnets assigned
to internal equipment/infrastructure
along with the corresponding hostname/
device name for each IP address/subnet
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
Third Party Internet Access IP addresses reassigned by an ISP to an
(TPIA) over Cable incumbent cable operator for use with Third
NRPM [Link] Party Internet Access (TPIA) will be counted
as fully used once they are assigned to
equipment by the underlying cable carrier
provided they meet the following
requirements:
• Provide reassignment information for the
addresses provisioned to each market
area and for any customers with eight or
more contiguous IP addresses via SWIP or
RWhois
• Initial assignments to each piece of
hardware represent the smallest subnet
reasonably required to deploy service to the
customer base served by the hardware.
• Additional assignments to each piece of
hardware are made only when all previous
assignments to that specific piece of
hardware are at least 80% used and
represent a three-month supply
• IP allocations issued through [Link] are
nontransferable via section 8.3 and section
8.4 for a period of 36 months. In the case of
a section 8.2 transfer, the IP allocation must
be utilized for the same purpose or
needs-based justification at a rate consistent
with intended use.
Updated September 2023
Updated September 2023
IPv4 Address Space – End-user Initial Assignment (use IPv4 End-user
Network Request form)
Type of Resource Request Criteria to Receive Resources
End-user Initial Assignments /24 • End-user organizations without direct
minimum assignment assignments or allocations from ARIN
NRPM 4.3 qualify for an initial assignment of
ARIN’s minimum assignment size
• Provide data demonstrating at least a
50% utilization rate of the requested
block within one year
IPv4 Address Space – End-user Additional Assignment (use IPv4 End-user
Network Request form)
Type of Resource Request Criteria to Receive Resources
End-user Additional Assignments • Provide data showing efficient utilization
/24 minimum assignment of at least 50% of each previous
NRPM 4.3.6 assignment
• Provide data showing at least 80% of
the sum of all assignments is efficiently
used
• Provide data demonstrating a 50%
utilization rate of the requested block
within 24 months
IPv6 Address Space - Allocation (use IPv6 ISP Request form)
Type of Resource Request Criteria to Receive Resources
Initial Allocation to LIRs • Have a previously justified IPv4 ISP
/32 minimum allocation allocation from ARIN or one of its
(/36 or /40 upon request) predecessor registries, or
NRPM 6.5.2 • Qualify for an IPv4 ISP allocation under
current policy, or intend to immediately
multi-home, or
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
• Provide a reasonable technical justification,
including a plan showing projected
assignments for one, two, and
five-year periods, with a minimum of
50 assignments within five years
IPv6 Multiple Discrete Networks • Be a single entity and not a consortium
/32 minimum allocation of smaller independent entities
(/36 or /40 upon request) • Have compelling criteria for
NRPM 6.11 creating discrete networks, such
as regulatory restrictions for
data transmission, geographic
distance and diversity between
networks, and autonomous multihomed
discrete networks
IPv6 Address Space - Allocation (use IPv6 ISP Request form)
Type of Resource Request Criteria to Receive Resources
ISP Additional Allocation • Demonstrate at least 75% utilization of
NRPM 6.5.3 your IPv6 allocations from ARIN, or
• Demonstrate at least 90% utilization
of any single serving site within your
network, or
• Have allocated more than 90% of your
total address space to serving sites,
with the block size allocated to each
serving site being justified based on
the criteria specified in section 6.5.2
• Complete renumbering if applicable
ISP Additional Allocation for • Provide a detailed plan for using the
Transitional Technology block to implement an IPv4 to IPv6
/32 minimum allocation transitional technology
/24 maximum allocation
NRPM [Link]
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
• Justification for transitional allocations
will be reviewed every three years and
reclaimed if they are no longer in use
for transitional purposes
IPv6 Multiple Discrete Networks • Be a single entity and not a consortium
/32 minimum allocation of smaller independent entities
NRPM 6.11 • Have compelling criteria for creating
discrete networks, such as regulatory
restrictions for data transmission,
geographic distance and diversity
between networks, and autonomous
multihomed discrete networks
• For each discrete network receiving
additional addresses, demonstrate that
network meets the standard IPv6 ISP
additional allocation requirements
IPv6 Address Space - Assignment (use IPv6 End-user Request form)
Type of Resource Request Criteria to Receive Resources
End-user Initial Assignment Organizations may justify an initial
/48 minimum assignment assignment for addressing devices directly
NRPM 6.5.8 attached to their own network
infrastructure, with an intent for the
addresses to begin operational use within
12 months, by meeting one of the following
criteria:
• Having a previously justified IPv4 end user
assignment from ARIN or one of its
predecessor registries, or;
• Currently being IPv6 Multihomed or
immediately becoming IPv6 Multihomed
and using an assigned valid global AS
number, or;
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
• By having a network that makes active use
of a minimum of 2000 IPv6 addresses within
12 months, or;
• By having a network that makes active use
of a minimum of 200 /64 subnets within 12
months, or;
• By having a contiguous network that has a
minimum of 13 active sites within 12
months, or;
• By providing a reasonable technical
justification indicating why IPv6 addresses
from an ISP or other LIR are unsuitable.
• Examples of justifications for why
addresses from an ISP or other LIR may be
unsuitable include, but are not limited to:
• An organization that operates
infrastructure critical to life safety or the
functioning of society can justify the need
for an assignment based on the fact that
renumbering would have a broader than
expected impact than simply the number of
hosts directly involved
• These would include: hospitals, fire
fighting, police, emergency response, power
or energy distribution, water or waste
treatment, traffic management and control,
etc.
• Regardless of the number of hosts directly
involved, an organization can justify the
need for an assignment if renumbering
would affect 2000 or more individuals either
internal or external to the organization.
Updated September 2023
Updated September 2023
Type of Resource Request Criteria to Receive Resources
• An organization with a network not
connected to the Internet can justify the
need for an assignment by documenting a
need for guaranteed uniqueness, beyond
the statistical uniqueness provided by
ULA (see RFC 4193).
• An organization with a network not
connected to the Internet, such as a VPN
overlay network, can justify the need
for an assignment if they require
authoritative delegation of reverse DNS.
End-user Additional Assignment • Show an overall 75% utilization
NRPM [Link] of all previous assignments.
Autonomous System Number (ASN)
(use ASN Request form)
Type of Resource Request Criteria to Receive Resources
Autonomous System Numbers (ASNs) Any organization may be issued a single
NRPM 5 Autonomous System Number (ASN) upon
request. Organizations that have space
issued under Multiple Discrete Networks
policy may be issued one ASN per discrete
network upon request.
Additional ASN requests should include
proof of the requestor’s need for a unique
routing policy, or other technical
justification for the need for more than one
ASN.
Updated September 2023