Jump to:

Relevant Links

Guidelines - Requesting an IPv4 or IPv6 Micro-allocation

This is an overview of how to request and manage a micro-allocation of IP address space from ARIN. ARIN provides micro-allocations of IPv4 and IPv6 addresses to:

Critical internet infrastructure networks include core DNS service providers (e.g. ICANN-sanctioned roots, gTLD and ccTLD operators) as well as the RIRs and IANA.

ARIN makes micro-allocations no longer than a /24 using IPv4 or a /48 using IPv6. These blocks of address space may not be subdelegated outside an organization. ARIN provides a list of all micro-allocations it has granted to apprise the network operator community which addresses should not be filtered.

Obtaining a Micro-allocation

Step 1 - Requirements

Review ARIN's IPv4 micro-allocation policy or IPv6 micro-allocation policy to ensure your request meets the requirements. Exchange point operators may also request address space under other policies. Requesting resources from ARIN indicates you have read and agree to abide by these policies.

Requirements for critical internet infrastructure networks:

Qualifying networks include core DNS networks (ICANN-sanctioned root and TLD operators), RIRs, and ICANN.

Requirements for Public Exchange Point Operators:

A public exchange point operator provides a physical infrastructure allowing participants to exchange Internet traffic between their autonomous systems by means of mutual peering. Public exchange point operators must provide justification for the IP addresses, including: connection policy, location, participants (minimum of two total), ASN, and contact information.

Requirements for non-routed IPv6 core addressing:

Organizations that currently hold IPv6 allocations may request a block of IPv6 addresses (typically a /48) to address core network devices, independent of any addressing topology present on the network's edge. This block must not be routed externally from the AS in which it is configured. The organization must provide ARIN with technical justification indicating why this block is required.

To request a micro-allocation, your organization must first have established Point of Contact (POC) handles and an Organization Identifier (Org ID) with ARIN. Additional information about creating and managing POCs and Org IDs is available in ARIN's Guidelines for Managing Organization and Contact Identifiers.

Step 2 - Completing the Template

An organization can request a micro-allocation from ARIN through four different templates: the IPv4 ISP Network Request Template; the IPv4 End-User Network Request Template; the IPv6 Network Request Template; and the IPv6 End-user Request Template. All micro-allocation requests must be sent from the Admin or Tech Point of Contact (POC) associated with the organization's Org ID.

To denote that your request is for a micro-allocation, your template must include a micro-allocation sized prefix in the "Prefix Length Requested" field and include both a notation that this is a request for a micro-allocation and any information pertinent to the justification of the request in the "Additional Information" field of the template.

Instructions for completing and submitting the template are provided at the bottom of the document. To ensure prompt and accurate processing of your organization's micro-allocation request, 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- Fee Payment and Registration Services Agreement

Fees for micro-allocations are based on the size categories outlined in the ARIN Fee Schedule. To summarize:

  • ARIN does not charge organizations an initial registration fee for the approved micro-allocation if they have previously received a direct allocation of address space from ARIN. However, the micro-allocation is included in the allocated address space they are billed for on an annual basis.
  • ARIN charges an initial fee under the "X-Small/Micro-allocation" size billing category to end-user organizations, meaning those approved to receive a micro-allocation that have not received a direct allocation from ARIN. After receiving approval confirmation and a ticket number, your organization must submit an End-user Billing Account Form to remit payment.

    Organizations are then billed annually for a maintenance fee that covers all IPv4 and IPv6 assignments, ASNs, and transfers that are associated with each Org ID.

ARIN does not accept purchase orders as the equivalent of payment and payment information is not accepted by phone. 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.

Submission of Signed Registration Services Agreement (RSA)

All applicants requesting resources from ARIN are required to sign the Registration Services Agreement (RSA). The RSA must be signed and returned before ARIN allocates resources. The RSA cannot be altered or modified. If the organization already has a signed RSA on file with ARIN, a new one is not needed unless the request for resources will be issued under a new Org ID. Organizations may fax a signed, but otherwise unaltered, RSA to +1.703.227.0671. ARIN requests that the organization also forward two (2) signed originals via postal mail to:

ARIN
Attention: Financial Services Department
3635 Concorde Parkway, Suite 200
Chantilly, VA 20151

Submission of Payment

When completing ARIN's online billing forms, organizations may choose between two payment options:

Immediate online payment by credit card (American Express, Discover, MasterCard, and Visa)

If payment is by credit card, an automatic receipt is e-mailed to the organization, along with instructions on how to download the Registration Services Agreement (RSA).

Receive an invoice for payment by check or wire transfer

For organizations choosing to receive an invoice, ARIN sends an invoice within three (3) business days and instruction on how to download the Registration Services Agreement (RSA). For instructions to send payment by wire transfer, call +1.703.227.9886 or e-mail billing@arin.net.  For wire instructions by e-mail, include the ARIN ticket or invoice number, the organization name, and Org ID. For payments by check, send payment to:

American Registry for Internet Numbers
P. O. Box 79010
Baltimore, Maryland  21279-0010

Step 7- Granting of Micro-allocation

For end-users, ARIN grants the micro-allocation within two (2) business days of ARIN's receipt of the registration fee and a signed RSA. For ISPs, ARIN grants the micro-allocation immediately upon written approval from ARIN.

Receipt of a micro-allocation does not qualify organizations for ARIN membership. Only organizations that receive and pay for a direct allocation of IP address space from ARIN are automatically accorded membership.

As membership is open to all interested parties, any organization or individual may become a member of ARIN by completing a Membership Application Form and paying an annual membership fee.

Managing a Micro-allocation record

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 Managing Organization and Contact Identifiers.

Annual Fees and Exemptions

For end-users receiving micro-allocations, ARIN assesses a single consolidated annual maintenance fee to each Org ID for certain resources registered to it. This single fee covers all ASNs, end-user assignments, and transfers registered with ARIN per Org ID. This fee is due on the anniversary date of the organization's first resource registration associated with the Org ID.

ISPs that are current ARIN subscription holders and receive a micro-allocation are not charged the annual maintenance fee. However, the micro-allocation is included in the allocated address space they are billed for on an annual basis.

Additional information about ARIN's fees is available on the Fee Schedule and in the Billing section.

Modifying or Returning a Micro-allocation

There are two types of changes that can be made to a micro-allocation record:

Modification

The IPv4 Network Modification (Net-Mod) template and the IPv6 Network Modification (IPv6-NET-Mod) template can be used to change the POC handle associated with a micro-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.

If you wish to change POCs associated with a micro-allocation, the POCs must already exist. If the POCs are not currently registered in the ARIN database, submit a POC template prior to submitting the Net-Mod template.

Return

The templates referenced above can also be used to return unused micro-allocations to ARIN. Returns of a micro-allocation can only be submitted by the Administrative POC.

Transfers of Micro-allocations

Transfers of micro-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.