Jump to:
- Step 1 - Requirements
- Step 2 - Completing the Template
- Step 3 - Submittal of Template and Auto Response
- Step 4 - Review Process
- Step 5 - Request Approval
- Step 6 - Fees
- Step 7 - Allocation
- Managing Allocation Records
Relevant Links
Guidelines - Requesting Additional IPv4 Allocations from ARIN
This is an overview of how to request and manage an additional allocation of IPv4 address space after receiving an initial allocation from ARIN.
Obtaining an Additional Allocation of IPv4 Address Space from ARIN
Step 1 - Requirements
Review ARIN's IPv4 policies to ensure your request meets the additional IPv4 allocation requirements. Requesting resources from ARIN indicates you have read and agree to abide by these policies.
All additional IPv4 allocation requests must be sent from the Admin or Tech Point of Contact (POC) associated with the organization's Org ID. Requests are submitted using the ARIN ISP Network Request template.
To modify contact and/or organization information, please see ARIN's Guidelines for Managing Organization and Contact Identifiers.
As described in ARIN's IPv4 policies, organizations that have efficiently utilized at least 80% of their most recent allocation from ARIN, and are able to show efficient utilization of all previous allocations, can request an additional direct allocation of IPv4 address space. ISPs that have residential cable subscribers must show that they have reassigned at least 80% of their current address space, with a 50 to 80% utilization rate, in order to request additional addresses. Organizations requesting additional space under the Multiple Discrete Networks policy must demonstrate utilization greater than 50% of both the last block allocated and the aggregate sum of all blocks allocated from ARIN, OR demonstrate all unallocated blocks of addresses are smaller than ARIN's current minimum allocation size.
Reassignment Information
IPv4 allocations are based on an ISP's utilization history, projected three-month requirement, and other information ARIN deems necessary. Utilization history is based on the reassignment information supplied to ARIN through SWIP or RWhois, information supplied through the request template, and information gathered by ARIN during the request process. Information on the requirements and procedures for reporting reassignment information is available in the Guidelines for Reporting Reassignment Information.
Immediate Need
To qualify under the Immediate Need policy, your organization must provide extensive documentation to demonstrate the requested IP addresses will be used within 30 days. ARIN’s minimum allocation under the Immediate Need policy is a /22 (if multi-homed) or a /20 (if single-homed). ARIN’s maximum allocation under the Immediate Need policy is a /16. These cases are exceptional and must meet stringent requirements. Requests under this policy must still meet the requirements for general IPv4 allocations.
Twelve-month Supply
After your organization has had an IP allocation directly from ARIN for one year, you may choose to request a twelve-month supply of IP addresses.
Step 2 - Completing the Template
When completing the ISP Network Request Template, your organization must establish justification for the request of additional space. Justification information includes:
- a description of your organization's connectivity to the Internet, including any peering points, exchange points, and ISPs providing connectivity.
- detailed information as to how previous network allocations have been utilized. Verification of utilization is supplied to ARIN in the form of reassignment information. (See "Guidelines for Reporting Reassignment Information.")
- your organization’s projected addressing needs over the next 3-, 6-, and 12-month periods, in /24 units.
- a description of the products and services your organization provides.
When requesting additional IP address space for IP-based web hosting, supply (for informational purposes only) technical justification for this practice.
Instructions for completing and submitting the template are provided at the bottom of the document. To ensure prompt and accurate processing of your ISP Network Request Template, follow these instructions exactly. Any errors found may result in the template being returned for correction.
Step 3 - Submittal of Template and Auto Response
Upon successfully submitting the template, ARIN verifies its receipt of the request and issues a ticket number via e-mail to the individual who submitted the request. Based on the volume of requests, this may take up to 60 minutes.
Step 4 - Review Process
ARIN reviews and responds to a resource request within three (3) business days.
The response may include a request for additional information. For each question and response cycle, ARIN responds within three (3) business days. If ARIN does not receive a response within ninety (90) days, the ticket is considered closed and the request must be resubmitted. A response from ARIN requesting additional documentation or information does not imply a request will be denied; it simply means that additional information is needed to evaluate the request.
For questions about requests, communicate via e-mail to hostmaster@arin.net or call ARIN's Registration Services Help Desk at +1.703.227.0660. When contacting the Help Desk, have appropriate ticket numbers and other request documentation readily available, and have access to the ARIN website. In follow-up communication, supply the name of the ARIN Help Desk Resource Analyst that provided previous assistance. Click here for additional guidance on calling the Help Desk.
Step 5 - Request Approval
ARIN notifies your organization, via e-mail to the individual who submitted the request, whether the request was approved or not. The approval is good for ninety (90) days. If your organization does not follow up on the approval within that time, you must resubmit the request.
If a request is rejected and you feel that it has the proper justification for receiving the requested resource, you may contact ARIN to further explain its position.
Step 6- Fees
There is no fee for registering an additional allocation of IPv4 address space. However, when an additional IPv4 allocation moves an organization into a larger size fee category, ARIN issues an invoice for the new fee two months prior to the next annual renewal fee due date. For specifics on annual renewal fees, see the ARIN Fee Schedule. Additional fee and payment information is available in the Billing section.
The approval of a request can be dependent on the billing status of the Org ID in question. Outstanding fees due to ARIN must be paid before additional resources are allocated.
Step 7 - Allocation
ARIN completes the allocation of the additional IP address block to the organization the day of ARIN's written approval of the request.
Managing Allocation Records
Organization and Contact Identifiers
To ensure efficient and accurate processing, promptly update Org ID and POC records after any change. Additional information about Org IDs and POCs is available in ARIN's Guidelines for Organizations and Contact Identifiers.
Maintaining IN-ADDRs
ARIN has requirements regarding the responsibility of organizations in maintaining all IN-ADDR.ARPA domain records for their customers. For specific regarding this policy, see the Maintaining IN-ADDRs section of the NRPM.
Reassigning Address Space to Customers
As outlined in ARIN's IPv4 Policy, organizations must ensure that their customers meet certain utilization efficiency requirements. As IP addresses are allocated to organizations in contiguous blocks, these blocks should remain intact and fragmentation of blocks is discouraged.
If a customer moves to another service provider or otherwise terminates a contract with an upstream organization, ARIN recommends that the customer return the network addresses to the upstream organization and renumber into the new provider's address space. The original upstream organization should allow sufficient time for the renumbering process to be completed before requiring the address space to be returned.
ARIN must review and approve reassignments of a /18 or greater by “extra-large” organizations and reassignments of a /19 or greater for all other organizations. Specifics, including what information needs to be included in the template, are available in the Reassigning Address Space to Customers section of the NRPM.
Providing Reassignment Information
Guidelines for the Reporting of Reassignment Information outlines requirements and procedures ISPs must follow in reporting reassignment information to ARIN.
Modifying or Returning an IPv4 Allocation
There are two types of changes that can be made to an IPv4 allocation record.
Modification
The Network Modification (NET-Mod) template can be used to change the POC handle associated with a resource allocation or to modify a network name. Modifications are submitted by the Administrative or Technical POC for the appropriate Org ID, or the Technical POC for the resource.
To change POCs associated with a resource allocation, the POCs must already exist. If the POCs are not currently registered in the ARIN database, submit a POC template before submitting the NET-Mod template.
Return
The Network Modification template can also be used to return unused allocations to ARIN. Returns of an allocation can only be submitted by the Administrative POC.
Transfers of IPv4 Allocations
Transfers of IPv4 allocations are handled similarly to the transfer of any ARIN resource. Specific guidelines for this process are provided in ARIN's Guidelines for Transferring Internet Number Resources document.