Current Fee Schedule FAQ
Changes to the Fee Schedule
What changes took effect with the most recent version of the Fee Schedule?
- Transitioning End Users from annual per-resource maintenance fees to the RSP (Registration Services Plan) Fee Schedule.
- Transitioning Legacy resource holders from annual per-resource maintenance fees to the RSP Fee Schedule while maintaining an annual fee cap (which will increase $25 per year).
- Providing a temporary IPv6 fee waiver for organizations in the 3X-Small category that desire a larger address block.
- Implementing a $50 fee for OrgCreate and a $100 fee for OrgRecovery transactions.
- Increasing the transfer processing fee to $500.
Why did the Fee Schedule change in 2022?
The Fee Schedule was amended, following a community consultation, in order to recover costs in a fair and equitable manner via appropriate fees to maintain adequate funds for the long-term stability of the organization. In 2022, ARIN will transition all customers to the RSP fee schedule based on total IPv4 and IPv6 resources held. This change will ensure costs are distributed in an equitable manner by eliminating the current fee differentiation between ISP and end user organizations.
What resources are available if we have additional questions?
Please see the following links for more information. If you have additional questions, please contact 2022Fees@arin.net or submit via Ask ARIN, while logged into your ARIN Online account.
Consultation on ARIN Fees:
New ARIN Fee Schedule Announcement:
2022 Fee Schedule:
ARIN Fee Calculator:
Determining your fees
How do I determine my fees if my organization has multiple resources under one Org ID?
ARIN Online features a fee calculator for ARIN resource holders wishing to view an estimate of annual fees.
How are my fees determined?
ARIN determines fees per Org ID. Fees are determined by the service category corresponding to the cumulative size of IPv4 or IPv6. If an organization holds both IPv4 and IPv6 resources, the fee is based on the larger dollar value.
Invoices now contain a description of the resources that your organization’s fees are based in, using a base count of /24s for IPv4 and /48s for IPv6. The table below shows how those equivalents match up with the fee categories as described within the Fee Schedule.
|Service Category||Fee||Range of /24s||Range of /48s|
|3X-Small||$250||1||1 to 256|
|2X-Small||$500||2 to 4||257 to 4096|
|X-Small||$1,000||5 to 16||4097 to 65536|
|Small||$2,000||17 to 64||65537 to 1,048,576|
|Medium||$4,000||65 to 256||1,048,577 to 16,777,216|
|Large||$8,000||257 to 1,024||16,777,217 to 268,435,456|
|X-Large||$16,000||1,025 to 4,096||268,435,457+|
|2X-Large||$32,000||4,097 to 16,384|
|3X-Large||$64,000||16,385 to 65,536|
|4X-Large||$128,000||65,537 to 262,144|
What do you mean by “cumulative total?”
The current fee schedule is based on the service category corresponding to the total amount of ARIN allocated IP address space to an organization, covered under an ARIN Registration Services Agreement (RSA). For example, if an organization has both a /32 of IPv6 address space (X-small service category) and a /17 of IPv4 address space (medium service category), that organization will be in the medium service category as this is the larger of the two and invoiced accordingly. For another example, if you have a /20 and a /21 issued by ARIN under RSA, and a /18 of legacy address space that is not covered under any agreement, your annual fees are calculated solely on the space under an RSA and falls under the small Service Category of the fee schedule.
Understanding Your Invoice
Recently, ARIN revised our invoice design for our customers. Changes include updated payment information and itemization for all resource types and corresponding fees and values.
Resource Holdings Detail
To assist customers with the management of their resources, invoices now contain cumulative totals of held IP resources using the baselines of /24s for IPv4 and /48s for IPv6.
Legacy RSA Changes
Invoices now show what a Legacy Resource holder organization’s fee would be without the Legacy RSA Fee Cap, and then what their annual fee is with the fee cap. Example included below.
Where do I find more information on the billing process?
Information about how billing works and the resource revocation, returns, and reinstatement process is available on the ARIN website.
How do I determine the term dates of my annual invoice?
The term of coverage is one year, renewing annually on the last day of each organization’s anniversary month. For example, for an invoice due 30 June 2016, the period of coverage would be 30 June 2016 - 29 June 2017.
Can I pay the renewal fees for multiple years?
No, the annual fee may fluctuate from year to year. Each year the annual invoice is calculated by ARIN-issued IPv4, IPv6 address and ASNs to an organization by cumulative total of resources under contract.
Is each resource held under a single Org ID billed under a separate invoice?
No, ARIN generates a single invoice per Org ID. If an organization holds multiple resources (ASN, IPv4, and/or IPv6), the invoice details the resource type, quantities, and amount for the annual fee.
Managing Your Fees
If I am an ISP, can I return my IPv6 /32 for a /48 to lower my annual fees?
This is not possible under the current policy “Initial Allocation to LIRs,” NRPM 22.214.171.124.b, as it states that the smallest block an ISP may be allocated is a /36 or /40. Partial returns of any IPv6 allocation that results in less than a /36 of holding are not permitted (NRPM 126.96.36.199.g). So the smallest block your organization can reduce to at this time is a /36, which is in the 2X-Small category.
How can I tell if returning IPv6 addresses (or a portion) will reduce my fees?
You will need to look at the Fee Schedule in the Service Category for both IPv4 and IPv6 to determine if returning IPv6 addresses will reduce your fees. Per the current fee schedule, ARIN calculates annual fees based on the larger of your IP address holdings.
For example, if your cumulative (total) IPv4 allocations are greater than a /22 IPv4 allocation (2X-Small) and you have a /32 IPv6 allocation (X-Small), your corresponding Service Category is X-Small, the larger of the two service categories. Returning your /32 for a /36 would reduce your IPv6 Service Category to “2X-Small,” and you will be invoiced according to the fees associated with the 2X-Small Service Category.