ARIN's 5% RSP Fee Increase for 2027: What Actually Changes for Legacy Holders

A client called me the week ARIN posted the notice, certain his bill was about to jump. He had the headline exactly right and the conclusion exactly wrong. He holds a pre-2010 /20 under a Legacy Registration Services Agreement, he had read "ARIN Fee Increase Approved for 2027," and he had drawn the obvious line straight to his own invoice. The headline was accurate. His invoice is not going up. The 5% increase ARIN's Board of Trustees approved on 19 April lands on the Registration Services Plan, the fee program that active registrants pay. His legacy cap does not move.

That gap between an accurate headline and a wrong conclusion is where most of the confusion lives, so it is worth being precise. On 19 April the Board approved a 5% increase to RSP fees for 2027, in conformance with the RSP fee schedule, and ARIN published the notice on 12 May 2026. The stated reason is narrow and unglamorous: align operating costs with revenues while holding tight cost-control targets through 2030. There is no new policy, no community debate reopened, no reclassification of who pays what. It is the same escalator that produced a 5% rise for 2026, approved a year earlier on 27 April 2025.

This piece is for the people who actually have to budget against that number. I lead IPv4-leasing support at a marketplace that brokers and manages these resources, so I read these notices the way a holder does: anniversary date first, contract type second. Below is what the increase touches, what it pointedly does not, and the one date on your own account that decides when it bites.

The increase hits RSP fees, not the legacy cap

The single most important distinction in this announcement is the one the headline erases. ARIN runs two parallel fee realities, and the 5% applies to only one of them.

Active registrants are organizations holding allocations and assignments under a current Registration Services Agreement. They pay under the Registration Services Plan, and that is the program the 5% adjusts. Legacy holders under a Legacy Registration Services Agreement signed before 1 January 2024 sit under a different rule entirely: their total annual fees are capped at $250, regardless of how many legacy IPv4 resources they hold. A holder with a single /24 and a holder with a dozen legacy blocks both pay the same $250 ceiling. The 2027 increase does not touch that ceiling, raise it, or recalculate it against block count.

There is a claim circulating that I have had to talk clients down from, so let me state plainly where it fails. There is no mechanism by which "automated systems" reclassify your legacy holdings and blow past the cap based on how fragmented your inventory is. The cap is flat by design. ARIN's own language is "$250 annually, regardless of the number of IPv4 legacy resources held." If your agreement predates 1 January 2024 and stays in force, the number of blocks you hold is irrelevant to the cap. The risk that does exist is real and far more boring, and I cover it below.

The date that decides when you pay more

The 5% is not a calendar-year event. ARIN's term of coverage is one year, renewing on the last day of your organization's anniversary month rather than on 1 January. That detail is what turns a single board vote into a staggered rollout across the whole registry.

Work through one invoice and it becomes concrete. An invoice due 30 June 2026 covers service from 30 June 2026 through 29 June 2027. The 2027 rate does not apply to that bill; it applies to the renewal that begins the next cycle. So an organization whose anniversary falls early in the year sees the higher RSP fee months before one whose renewal lands in late autumn. If you are forecasting, the only date that matters is your own anniversary month. The calendar year tells you nothing.

The practical failure mode I see is people reading a fee schedule they downloaded last year. Reliance on a static local copy is how you budget against a stale number. The schedule lives in ARIN Online; pull it fresh before you model anything.

Why a flat legacy cap exists at all

It is fair to ask why ARIN protects legacy holders this aggressively while raising fees on everyone else. The answer is governance rather than generosity, and it is the part of the story worth defending.

ARIN recovers its costs; it does not run for profit. As a non-profit established in 1997, its mandate is to match operating costs to revenue through a community-driven, bottom-up policy process, the same process that sets the cap and the escalator both. The legacy cap is a deliberate cross-subsidy. Holders of address space distributed before the modern contractual framework existed are charged a nominal $250, and the cost of actually administering those resources is carried by the active-registrant fees that the 5% adjusts. You can read the annual increase as the price active holders pay to keep legacy space inside the registry system rather than drifting out of it entirely.

That structure has a tradeoff, and it is not the fake "reclassification" risk. The real tension is rigidity. A consensus-driven fee schedule is predictable, which is exactly why it cannot flex when a holder's own revenue contracts. The 5% is non-discretionary; it arrives on schedule whether your year was good or bad.

For a large carrier that is a rounding error. For a small entity running on a thin operational budget, a fixed annual escalator on a non-negotiable line item is the kind of cost that has to be modeled years out instead of absorbed by surprise. The same predictability that lets you plan for it precisely is what leaves you no room to defer it.

The one legacy risk that is actually real

If the cap is flat and the increase misses you, where is the exposure? It sits at the boundary of your protected status, and it has nothing to do with automation recalculating your inventory.

The $250 cap covers your legacy holdings under the pre-2024 agreement. It does not cover everything you might do *to* those holdings. A transfer, certain modifications, or bringing new space in under a current RSA are governed by their own fee terms, and those sit outside the legacy ceiling. The exposure is not that your existing cap silently inflates, because it cannot. It is that an action you take, a transfer you initiate or a new allocation you request, is billed under RSP terms that the 5% does touch. The line to watch is the line between what you already hold under the legacy agreement and anything new or transacted.

Before your next cycle, run this short audit against your own paperwork:

1. Confirm your LRSA execution date is before 1 January 2024. That date anchors your protected status; if it predates the cutoff and the agreement is in force, the cap holds.
2. Match the base annual fee to the legacy resources the agreement names. The resources billed under that fee should be the same legacy resources your LRSA covers, no more and no fewer.
3. Flag every line item billed separately from that base fee. A transfer, a new assignment, an RSA-governed object: each is where RSP pricing, and therefore the 5%, can reach you.

Nothing here requires panic. It requires reading your own invoice against your own agreement once a year.