Field Value
Author BTW Research
Published 2026-07-01
Primary category arin
Categories governance; rir-watchdog; arin
SEO title ARIN and the economics of small operator dependency
SEO description A research analysis of why small North American networks carry disproportionate risk when ARIN registry administration becomes slow, politicized, or opaque.
Focus keyword ARIN small operator dependency
Primary domain Governance
Content type Research
Topic small operator dependency
Subject ARIN
Region North America
Time horizon 12-24 months
Impact HIGH
Confidence B / 0.88

The registry as a dependency market

The American Registry for Internet Numbers is usually described in a language of technical stewardship: a non-profit registry, a neutral record keeper for Internet number resources, a forum where policy is made by an open community rather than by a state regulator or a private monopolist. That description is useful, but it is incomplete. In the North American Internet economy ARIN is also a dependency market. A small broadband provider in rural Canada, a fixed-wireless operator in the United States, a Caribbean hosting firm, a managed-services company trying to multihome, or a small cloud operator adding a new facility can function only if its IPv4 addresses, IPv6 addresses and autonomous system numbers are recognized, transferable, documented and routable. The resource is technical; the bottleneck is institutional.

That distinction changes the analysis. If a registry is viewed only as a ledger, delay looks like poor service. If it is viewed as a dependency market, delay becomes a form of capital cost. A slow decision can force a buyer to keep money tied up in escrow, postpone a customer deployment, accept more carrier-grade NAT, lease addresses as a bridge, renegotiate an upstream contract, or carry legal uncertainty into a financing round. A politicized rule process is not merely unpleasant. It gives the advantage to firms that can afford policy staff, travel budgets, counsel and repeated participation. An opaque registry is not merely inconvenient. It prevents the smallest networks from pricing the transaction risk attached to their next block of addresses.

This is why ARIN is a strong test case. The region it serves includes the United States, Canada, many Caribbean states and territories, and several North Atlantic islands, as ARIN's own region page records. It contains a large stock of legacy IPv4 resources, a mature IPv4 transfer market, a member-governed institution, a comparatively sophisticated broker ecosystem, and a sharp divide between early holders that received address space before scarcity and entrants that now have to buy or justify every increment. The result is neither an ordinary public utility nor an ordinary asset market. It is a hybrid institution in which private transactions require public validation and public rules shape private prices.

The central risk for small operators over the next 12 to 24 months is not a dramatic breakdown of ARIN. It is a slower and more plausible problem: the accumulation of frictions that are tolerable for large networks and strategically damaging for small ones. Waiting-list rules, transfer documentation, fee changes, legacy-resource treatment, routing-security services, membership rights and appeals all have economic consequences. Each can be defended in isolation. Together they form a dependency stack. The marginal cost of that stack is highest for the operator with one engineer, limited working capital and customers waiting for service.

ARIN's public documents provide the exhibits for this analysis. Its IPv4 guidance says the free pool reached depletion on 24 September 2015 and points applicants toward waiting-list space, specified-recipient transfers, reserved pools for special cases and IPv6 deployment. Its transfer guidance sets out a regime of source and recipient requests, documentation, fees, signed agreements and, for many transfers, operational-need review. Its bylaws distinguish voting General Members from Service Members without election rights. Its fee schedule establishes recurring and transaction charges that look small next to hyperscale budgets but meaningful beside the cash flow of a local access provider. Its legacy-resource guidance records that early allocations were made under different conditions and that some services depend on a Registration Services Agreement or Legacy Registration Services Agreement. These materials should not be treated as ARIN's final narrative about itself. They are evidence of the institutional design that small operators must navigate.

The question is not whether a registry needs rules. It does. IP addresses must remain unique. Registration records must be reliable. Fraudulent transfers and stale corporate claims would damage every legitimate network. Routing security depends on a chain of recognition. Scarce resources should not move to shell entities with no operational use. The question is whether the rule system recognizes the asymmetric cost of uncertainty. In an ordinary market, a buyer can agree a price, inspect the asset, close the contract and sue if title fails. In the IPv4 market the buyer must also satisfy registry policy, wait for administrative review, manage agreement status, pay registry fees, update operational records and, in some cases, coordinate across registries. That is a rational control regime for globally unique identifiers. It is also a regime in which small networks are buying not just addresses but institutional certainty.

Scarcity turned administration into market design

North America entered IPv4 scarcity with a distributional history that still matters. Early Internet address allocations were made when the network was a research, government and enterprise system rather than a universal access utility. ARIN's legacy-resource page notes that many early number resources were allocated without a formal legal agreement with ARIN, that ARIN was formed in December 1997 to administer many previously assigned resources, and that its Board decided to provide registration services for legacy holders without requiring all original holders to sign a services agreement or pay ordinary service fees. That continuity bargain helped preserve the registry. It also produced a lasting divide between early holders and later entrants.

For a small network created after exhaustion, IPv4 is not an administrative entitlement. It is a scarce production input. A /24 may be the minimum commercially useful block for multihoming and basic Internet presence. A /23 or /22 may be needed to support growth, business customers, public services or a modest hosting platform without excessive NAT complexity. Larger blocks are out of reach for many small firms unless they borrow, lease, acquire another company or accept years of gradual accumulation. IPv6 reduces the long-term pressure but does not remove the near-term dependence. Customers, payment systems, anti-abuse tools, enterprise firewalls, embedded devices, geolocation databases and ordinary operational practice still often assume reliable IPv4 reachability.

The post-exhaustion mechanics are not hidden. ARIN's IPv4 material says that, outside narrow reserved pools such as micro-allocations and IPv6-transition allocations, applicants generally look to the IPv4 waiting list or to specified-recipient transfers under the Number Resource Policy Manual. The waiting list operates only when addresses return to inventory through returns, revocations, IANA distributions or other reissued space. Its status page, as observed for this report on 1 July 2026, described episodic distributions rather than continuous supply: the last distribution had been completed on 2 April 2026 and the next was expected on or about 1 July 2026. That is rationing, not a supply channel that a young firm can build into a bankable expansion plan.

Rationing changes entry economics. In an abundant regime, a registry checks whether a request is justified and issues space. In a rationed regime, it checks whether a request is justified and places the applicant in a queue whose value depends on future returns, block sizes and the sequence of other requests. ARIN's waiting-list rules try to reduce gaming: a maximum /22 request, one request at a time, ineligibility for organizations holding more than a /20 equivalent, removal if an applicant declines an available block, and a 60-month restriction on transferring waitlist-issued space except in merger or reorganization cases. These rules have an anti-arbitrage logic. They also mean a small operator cannot treat the waiting list as dependable supply. It is a contingent claim on uncertain future inventory.

The transfer market fills part of the gap but does not escape the registry. ARIN's transfer framework allows transfers through mergers and reorganizations, specified-recipient transactions inside the ARIN region, and inter-RIR transfers where the relevant registries have compatible policies. For a specified transfer, source and recipient submit ticketed requests; ARIN links the requests after review; the parties coordinate directly; and ARIN does not disclose the other party's ticket information. The minimum IPv4 transfer size is generally a /24. Recipients must satisfy policy requirements, sign an agreement where needed, pay applicable fees and, for many transactions, document operational use. Larger requests require evidence that a defined share of the requested space will be used within the policy horizon. The private contract is therefore only one part of the transaction. The asset becomes usable through registry recognition.

This creates a North American paradox. ARIN's region has one of the deepest IPv4 markets in the world, an experienced broker community and many legacy holders with transferable inventory. It also has small networks forced to transact in a market that rewards documentation capacity, administrative sophistication and legal endurance. A cable incumbent or cloud platform can treat a transfer as a routine procurement project. It can assign counsel, respond to registry questions, hold inventory and absorb slippage. A local network may have a founder, a network engineer, a part-time finance function and an upstream contract that expires before a transfer completes. Scarcity turns institutional time into money. Institutional time is cheaper for large firms.

The same logic applies to information. A large buyer can pay for diligence, reputation screening, escrow support and legal review. It can price whether a block has stale contact history, reputation damage, routing complications or corporate-authority questions. A small buyer may rely on a broker, a seller's assertions and a limited reading of registry documentation. Registry approval is essential, but it does not guarantee that a block will be free of commercial baggage. It does not clean every reputation feed, correct every geolocation database, or make every upstream accept a route without further work. The registry is the legitimacy layer; the market still contains quality variation. The smaller the buyer, the harder it is to distinguish clean registration from usable supply.

Why delay is regressive

Administrative delay is often described as if each applicant experiences it in the same way. That is false. Delay is regressive. The operator with ample address inventory can wait. The operator already serving customers behind carrier-grade NAT, trying to turn up a data center, or attempting to win an enterprise customer cannot. When registry review, seller documentation, corporate-authority checks, inter-RIR coordination or agreement execution stretches from days into weeks, the cost falls hardest on the party whose business plan depends on the next block.

ARIN's transfer guidance makes an important distinction. After approval, once a signed Registration Services Agreement and all applicable fees have been received, resources are to be transferred within two business days. That final commitment is valuable. But it describes the last administrative step, not the full economic transaction. Before that point come account access, authority verification for the relevant points of contact, source validation, recipient need review, ticket linkage, fee invoicing, agreement status, possible inter-RIR coordination and, where legacy or corporate-history issues exist, evidence that the current holder can transfer the block. The registry update may be quick after approval. The uncertainty before approval is where small operators carry the cost.

The cost is not theoretical. IPv4 prices vary by block size, reputation, timing and market conditions, but market-participant commentary remains useful as an order-of-magnitude exhibit. IPXO's 2026 market discussion, which should be treated as a broker-side view rather than an independent index, describes typical sale ranges of roughly $11 to $32 per IPv4 address in 2026 and monthly lease rates in the tens of cents per address. At those levels, a /24 can be a meaningful purchase for a small firm and a /22 can represent a capital decision rather than an operating detail. Add brokerage, legal review, registry charges, financing cost and staff time, and the transaction becomes one of the larger discretionary decisions a small network will make.

Delay affects bargaining power as much as accounting. Sellers of clean blocks know that buyers under time pressure have limited alternatives. A buyer that has committed to a facility, promised a customer deployment or exhausted its internal inventory cannot easily walk away from a delayed transaction. The seller may not control registry timing, but the seller benefits from the buyer's lack of substitutes. If the buyer abandons the deal, it must search again, repeat diligence, renegotiate escrow and possibly lose a commercial window. The registry does not set the private price; still, registry uncertainty is capitalized into private bargaining.

Large firms can arbitrage uncertainty. They can hold spare inventory, buy larger blocks ahead of need, lease temporarily, split demand across multiple transactions, or acquire entities for their resources. They can absorb a failed transaction as a portfolio event. Small firms buy closer to need, in smaller blocks and with less redundancy. ARIN's fee schedule illustrates the asymmetry at a modest scale. A 3X-Small annual registration category for a /24 or smaller and a 2X-Small category for larger than /24 up to /22 are not crushing as published charges. Transfer processing fees and recipient fees are not, by themselves, likely to bankrupt a real operator. Yet fixed and semi-fixed costs loom larger when the transaction is small. A $500 fee means little in a /14 deal; it matters more in a /24 deal surrounded by escrow, diligence and staff time.

The most damaging cost is planning uncertainty. A small operator can sometimes borrow to buy addresses; it cannot borrow certainty. It cannot know with confidence whether a seller's authority records will satisfy review, whether a legacy holder's corporate history will be clean, whether an inter-RIR counterpart will align on timing, whether a waiting-list distribution will match an acceptable size, or whether documentation of future need will be judged sufficient. ARIN's waiting-list rules state that the chronological list is not necessarily the order in which requests will be filled, because fulfillment depends on the order, size and quantity of address blocks entering inventory. That may be administratively unavoidable. It is also the opposite of bankable predictability.

The result is a quiet transfer of risk. The small network may lease addresses while waiting, accept worse terms from an upstream, delay IPv6 work because staff are handling IPv4 paperwork, or buy a smaller block and pay later in network complexity. In each case the registry decision may be reasonable and the market counterparty may be acting lawfully. The structural outcome is still regressive: the thinner the operator's cushion, the more institutional uncertainty shapes its competitive position.

Transfers: private price, public validation

IPv4 transfer markets are often described as private markets wrapped in registry compliance. That understates the registry's role. ARIN does not merely record a transfer after two parties reach agreement. It recognizes the source, validates the recipient, checks eligibility, requires agreement status and applies policy. It therefore acts as a market validator. The market price expresses scarcity; registry approval expresses legitimacy.

This validator function is indispensable. If IP address transfers could be completed by private contract alone, the result would be duplicate claims, routing disputes, broken reverse DNS, abuse conflicts and a general erosion of trust. The value of a registry lies in making a unique claim socially legible to the rest of the Internet. The economic problem is that social legibility can become administrative leverage. The party that most needs legitimacy must accept the timing, standards and discretion of the institution that grants it.

ARIN's Number Resource Policy Manual gives this regime its formal shape. Section 8.3 permits transfers between specified recipients inside the region, subject to conditions on the source and recipient. The source must be the current registered holder, the resource must not be under dispute, recent-receipt and reserved-pool restrictions may apply, and a transferring source may face a 36-month bar from applying to the IPv4 waiting list. The recipient must satisfy Section 8.5 requirements and, where applicable, is removed from the waiting list when a transfer supplies the needed space. Section 8.4 permits inter-RIR transfers only where the registries involved have compatible policies. These rules reduce speculation and protect registration integrity. They also make the private bargain dependent on several public judgments.

For a large buyer, the need demonstration is an internal professional exercise. It can provide utilization reports, customer projections, product forecasts, facility plans and legal documents. It can respond to follow-up questions without derailing operations. For a small buyer, the same evidence burden can resemble a fundraising process. The firm must translate messy and uncertain demand into a formal plan: how many addresses will be used, by whom, on what timetable, under what network design, and with what proof from past utilization. If the business is new, rural, seasonal, grant-dependent or island-based, the evidence can be harder to present in the neat form a mature incumbent can supply.

Needs assessment is therefore both a stewardship tool and a market-entry filter. It prevents a shell buyer from acquiring scarce addresses merely to resell them. It also forces a real entrant to prove the future in a format that favors firms with stable histories. A requirement that a recipient document use of at least half the requested block within 24 months may sound moderate. For a small network, 24 months can contain most of its strategic risk. Demand may be credible but conditional. A local authority may award a contract only after address availability is confirmed. A tower lease may depend on permits. A hospitality customer may need proof of routable service before signing. The operator is asked to prove demand that may depend on obtaining the resource.

Transfers are also operational transitions, not just changes of record. ARIN's transfer guidance tells source organizations to review RPKI route origin authorizations, IRR objects and reverse DNS delegations. It notes that transferred resources covered by an ARIN RPKI certificate are removed from the source certificate and that a recipient with an ARIN certificate will have it renewed to include the transferred resources. This is good technical hygiene. It also means a small operator is not simply buying addresses. It is coordinating registration, routing security, route filters, reverse DNS, abuse contacts, geolocation correction and customer communication. A large network may have teams for this. A small network may have one engineer changing configurations at night.

Inter-RIR transfers add another layer. The North American market can attract blocks from outside the region or move blocks to buyers elsewhere, but inter-RIR transfer depends on compatible policy and coordination between registries. A small North American buyer considering an out-of-region source must understand not only ARIN's rules but also the counterparty registry's requirements, timelines and documentation culture. This can improve liquidity, but it increases transaction complexity. The buyer may pay a broker to reduce the uncertainty; the broker then becomes part of the dependency stack.

The economic point is not that ARIN should approve transfers mechanically. A registry that ignored authority, fraud, utilization and eligibility would damage trust in every registered block. The point is that every review standard has a distributional effect. A predictable and transparent standard filters fraud with limited collateral damage. A slow or opaque standard filters fraud while also filtering small entrants. The difference matters. In a scarce market, uncertainty is not a neutral administrative by-product. It is a cost allocated to those least able to bear it.

Legacy certainty and the balance-sheet divide

Legacy IPv4 resources are one of the main reasons the ARIN region is economically distinctive. Early holders often received large allocations before a mature contractual regime existed. Some of those resources remain in organizations that use them. Some are held by firms with excess inventory. Some are attached to corporate histories that have become complicated through mergers, dissolutions, name changes and asset sales. Some are attractive transfer candidates precisely because they were obtained before address scarcity gave them market value.

ARIN's legacy-resource page presents this history as a continuity problem. ARIN administers many resources assigned before it existed, provides certain services for legacy resources, and offers a Legacy Registration Services Agreement as a way to establish clearer rights and services. That is sensible from an institutional perspective. But from the market side, legacy status introduces certainty questions. Is the current seller clearly entitled to transfer? Are records current? Does the block have agreement coverage sufficient for the recipient's desired services? What fees and caps apply? How will routing-security services be handled? What happens if corporate documentation is incomplete?

These questions matter disproportionately to small buyers. A sophisticated acquirer can hire counsel to reconstruct corporate history, insist on representations, demand escrow protections and walk away if the paperwork is uncertain. A small buyer may know only that a block is available at an affordable price. If the seller's title story is weak, the buyer may lose time, fees and commercial opportunity. If the block transfers but brings unresolved reputation or operational issues, the buyer inherits a problem that registry approval alone does not solve.

Legacy certainty also affects supply. If legacy holders see registration agreements, fee exposure or documentation burdens as uncertain, some may keep resources off the market. Scarcity then worsens for buyers. If the process is clear, more idle or underused space may become available through legitimate transactions. A registry that improves legacy clarity is not merely tidying historical records; it is improving market liquidity. In a market where small buyers often need modest blocks, even incremental supply can matter.

The divide between legacy holders and post-exhaustion entrants is also a balance-sheet divide. Early holders may possess address assets with low historical cost and high current value. Later entrants must buy or justify resources at scarcity prices. A firm that received a large block in an earlier era can monetize, lease, route or reserve it. A new entrant has to persuade a seller, a lender and the registry. The same technical identifier therefore sits on different sides of the balance sheet depending on when the organization entered the Internet economy.

This is not an argument for confiscation or for rewriting settled expectations. Stability of registration is itself a public good. But it is an argument for recognizing that legacy-resource policy is not a narrow administrative matter. It affects transfer supply, price discovery, routing security, fee fairness and market access. If legacy treatment is ambiguous, the ambiguity is priced into the market. Large participants can manage that price. Small participants mostly pay it.

ARIN's challenge is to make legacy modernization feel less like a political concession and more like a market-clearing necessity. Clean records, understandable agreements, clear service eligibility and predictable treatment of corporate-history problems all reduce the risk premium attached to legacy supply. They also protect buyers from inheriting brittle claims. For small operators, the best legacy policy is not one that maximizes registry leverage over old holders or preserves every historical privilege untouched. It is one that makes legitimate resources transferable, secure and usable with as little uncertainty as possible.

Member power and the cost of attention

ARIN's governance model rests on participation. Members elect trustees and Advisory Council members. Policy discussions occur in public forums and meetings. The Policy Development Process emphasizes community input, technical soundness and fairness. These are important safeguards. They reduce the danger that a registry becomes a closed bureaucracy. But participation is not free. The cost of attention is itself a political economy.

ARIN's bylaws distinguish between General Members, which may vote if in good standing and properly represented, and Service Members, which do not have election rights. That distinction is a formal governance fact, not an accusation. Yet it shows that influence depends on institutional status, administrative compliance and sustained engagement. Even among voting members, practical power is uneven. A large network can assign staff to follow policy threads, attend meetings, prepare comments, run candidates and build coalitions. A small operator's policy staff may be the same person responding to outages, ordering radios, negotiating a tower lease and answering customer calls.

Open participation can therefore coexist with under-representation. If a policy proposal affects transfer restrictions, waitlist eligibility, documentation standards or fee categories, the operators most affected may be the least present. Their absence should not be read as consent. It may mean the meeting conflicted with an outage, travel was unaffordable, the policy text was too dense, or the operator did not know the proposal would affect its next transaction. A process can be open in form and skewed in practice.

Scarcity increases the stakes of this attention gap. Before exhaustion, policy debate was partly about responsible allocation and technical coordination. After exhaustion, it is also about rents. Waiting-list rules affect who can obtain scarce returned space. Transfer rules affect liquidity and price. Needs assessment affects entry. Fee structures affect who funds the institution. Legacy treatment affects the value and marketability of historical holdings. Routing-security requirements affect operational burden. Even technical wording can redistribute value. The people who show up are more likely to shape those redistributions.

This does not imply a conspiracy of incumbents. Most policy participants may be acting in good faith, and many large networks have an interest in a healthy registry. The problem is structural. In a membership institution, organized attention has power. Small firms have less attention to spend. That is enough to create bias unless the institution deliberately translates policy choices into effects on thinly staffed operators.

Good governance under scarcity should therefore include distributional notes. A policy proposal that changes transfer eligibility should explain how it affects a new entrant seeking a /24, a rural provider seeking a /22, a small organization below /20, a legacy holder considering an agreement, and a buyer without previous ARIN resources. A fee proposal should show common small-operator paths, not only aggregate revenue sufficiency. An election process should publish participation patterns by size where privacy permits. A public meeting should provide short, plain-language summaries for those who cannot follow every thread. These measures do not privilege small networks. They make the cost of attention visible.

The danger is that member power becomes self-confirming. If small operators participate less, policy evolves around the preferences of those present. As rules become more complex, small operators participate even less. They then rely more on brokers and intermediaries. The market begins to treat institutional navigation as a private service, and the registry appears open while practical access depends on paid expertise. A registry that wants legitimacy after exhaustion must break that loop.

Ledger or gatekeeper

The cleanest conceptual distinction in registry economics is between a ledger and a gatekeeper. A ledger records who holds what, keeps data accurate, supports operational services and makes uniqueness credible. A gatekeeper decides who may enter, under what conditions, and how quickly the right becomes usable. ARIN is both. The tension between the two roles is the source of much small-operator dependency.

As a ledger, ARIN creates value by being boring. Accurate registration, clear points of contact, reliable reverse DNS, useful Whois and RDAP data, routing-security services, auditable policies and stable operations all reduce transaction costs. When the ledger is trusted, networks can route, filter, certify and troubleshoot with less friction. The best ledger is predictable enough that it disappears into operational routine.

As a gatekeeper, ARIN creates value by saying no. It refuses unsupported claims, blocks ineligible transfers, protects waiting-list integrity, detects weak authority, requires agreements and applies policy. Those refusals protect the ledger. Without them, fraud and duplicate claims would erode confidence. But saying no, or saying nothing for too long, also has economic consequences. It can prevent a real network from entering a market, force it into leasing, or strengthen a seller's hand.

The ledger role benefits from transparency. The gatekeeper role often invokes discretion and confidentiality. Transfer parties may not want commercial details exposed. Fraud review may involve sensitive information. Corporate authority documents may be private. Yet secrecy that is justified at the case level can become damaging at the system level. Small operators do not need to know another buyer's documents. They need to know typical timing, reasons for delay, common rejection patterns, evidence examples and escalation paths. System-level transparency can coexist with case-level confidentiality.

The danger is that ARIN's public materials remain stronger as descriptions of rules than as tools for pricing uncertainty. A page can list transfer requirements and still leave a small buyer unsure how long review will take, what evidence is normally sufficient, how often legacy history causes delay, or which costs are non-refundable. Disclosure is not the same as market transparency. A registry that shapes a scarce market needs transparency designed for economic decisions, not only for institutional self-description.

The ledger-versus-gatekeeper distinction also matters for routing security. RPKI and related services make the registry more operationally central. A transfer is not complete in commercial terms if the recipient has registration but struggles to establish route origin authorizations, update filters or correct stale operational data. As routing security becomes a baseline expectation, the registry's gatekeeping of certificate eligibility and resource association becomes more consequential. Small operators need this process to be fast and comprehensible because their customers experience routing problems as service failures, not as administrative nuance.

ARIN cannot and should not become a passive notary. The Internet needs a trusted registry. But the more the registry acts as a gatekeeper in a scarce market, the more it must be judged by the economic effects of its discretion. The test is not whether every individual decision can be defended. The test is whether the system as a whole lets legitimate small networks obtain and secure resources without treating institutional navigation as a competitive moat.

Post-exhaustion incentives inside the institution

Exhaustion changes a registry's incentives even if its formal mission remains stable. Before exhaustion, the central problem is allocation discipline: issue resources efficiently, prevent waste, preserve aggregation and maintain accurate records. After exhaustion, the registry still does those things, but it also validates private transfers, manages returned inventory, administers waiting-list rationing and mediates disputes over scarce assets. Its direct supply shrinks while its market-shaping authority grows.

This shift encourages caution. A registry that approves too easily may be accused of enabling speculation, fraud or hoarding. A registry that approves too slowly imposes costs that are dispersed across applicants and often invisible to the public. The reputational downside of a bad approval is concentrated and embarrassing; the downside of excessive caution is diffused. Institutional economics would predict a bias toward visible-error avoidance unless service-level discipline counteracts it. This is not a claim about motive. It is a claim about incentives.

ARIN has good reasons to be cautious. IPv4 addresses are valuable enough to attract fraud. Corporate records can be stale. Shell entities can be used to obscure control. Blocks with weak authority can be transferred into disputes that harm later buyers. A lax registry would damage small operators as well as large ones because trust in ARIN-administered resources would fall. The issue is not whether caution is legitimate. It is whether caution is paired with timing commitments, clear evidence standards and proportional review.

Post-exhaustion also turns policy into rent allocation. A 60-month restriction on transferring waiting-list space discourages arbitrage but reduces liquidity for an operator that later restructures. A 36-month restriction on a transferring source returning to the waiting list discourages churn but may affect a small firm selling assets to survive. A /22 waitlist cap spreads returned space more broadly but may not match the growth path of some legitimate providers. Needs assessment reduces speculation but can favor firms with historical utilization. Fee categories fund operations but shift costs among holders. Scarcity gives each rule a shadow price.

The institution's funding model adds another layer. ARIN recovers the cost of registry operations through fees charged to registry customers. That is normal for a membership organization. But cost recovery can conflict with distributional fairness at the margin. Legacy caps, annual increase limits, transfer charges, support levels and service categories determine who carries the cost of trust. A fee change can be fiscally prudent and still burdensome for the smallest networks. A transaction fee can be modest in aggregate and still raise the per-address cost of a /24 transfer. The economic question is always marginal: whose next decision changes because of this cost?

The next 12 to 24 months are likely to make these incentives more visible. ARIN has adopted a new fee schedule effective 1 January 2027. IPv4 demand remains supported by slow IPv6 substitution, broadband expansion, cloud and hosting growth, fraud controls, customer expectations and the operational value of routable scarcity. RPKI and routing-security expectations continue to rise. Legacy holders face choices about agreements and monetization. None of these developments requires crisis to matter. They make ARIN a more important economic actor precisely when small operators have the least slack.

The policy risk is that ARIN mistakes institutional stability for market health. A stable registry can still impose high small-operator transaction costs. Meetings may run, tickets may close, elections may occur and transfers may complete while entry becomes more expensive and more dependent on intermediaries. The relevant question is therefore not whether ARIN is functioning. It is whether the functions that matter to small operators are predictable enough to support competition.

The Caribbean and rural edge

The ARIN region is often mentally reduced to the United States and Canada. That misses a fragile edge of the region. ARIN also serves many Caribbean and North Atlantic markets, including small island states and territories with concentrated economies, exposure to natural disasters and high dependence on resilient communications infrastructure. A registry policy that looks modest from the perspective of a continental carrier may be more consequential for an island operator with fewer counterparties, higher transit costs and smaller administrative staff.

The economics of a small island operator differ from those of a national cable company or a cloud platform. Equipment lead times can be longer. International connectivity can be expensive. Customers may be concentrated in tourism, finance, government, education or diaspora services. A storm can destroy facilities and make rapid restoration urgent. A block that looks small in absolute terms may carry significant local resilience value. If a transfer stalls or legacy documentation proves unclear, the effect is not merely a delayed commercial expansion. It can affect redundancy, service continuity and the ability to serve customers after disruption.

Rural North American operators face a parallel problem. Fixed-wireless providers, small fiber builders, tribal networks, municipal networks and local ISPs often grow in areas where incumbents underinvest. They may depend on public grants, local partnerships or private debt. Their address needs are not enormous, but they are time-sensitive. A grant milestone, tower turn-up, school district contract or customer migration can require public IPv4 resources even where IPv6 is being deployed, because devices, applications and support systems still assume IPv4. If registry uncertainty pushes the operator toward heavier NAT, the cost appears later in support calls, customer complaints and engineering complexity.

These edge cases reveal the limits of pure conservation thinking. Conservation matters because IPv4 is scarce and unique. But the social value of a small block varies by use. A /24 used to improve rural connectivity or island resilience may have more public value than a larger block sitting idle in a corporate inventory. A registry cannot easily allocate by social value without politicizing its decisions. It can, however, acknowledge that procedural frictions have unequal public consequences. It can make small-block access more predictable, publish better data and ensure that anti-speculation rules do not accidentally burden the networks most likely to expand access.

The rural and island edge also exposes the weakness of raw participation metrics. Small operators in these markets may not attend policy meetings or run candidates, not because they are indifferent but because time is scarce. The same person who would comment on a policy proposal may be restoring service, dealing with customs paperwork, responding to a storm or preparing a grant report. Remote participation helps, but only if the process is designed for people who cannot follow every discussion in real time. Summaries, small-operator impact notes and targeted consultations would make formal openness more economically meaningful.

ARIN's role as a regional institution is therefore broader than maintaining a database. It is the trust layer for a continental and island-rich communications economy. If that trust layer works best for organizations with dedicated policy capacity, it will under-serve the edge. If it measures performance only by aggregate service levels, it may miss the operator for whom a single delayed /24 is a strategic setback. The region's diversity should be treated as a design constraint, not a map footnote.

Official narratives as exhibits, not conclusions

ARIN, ICANN and the Number Resource Organization produce extensive public material about stewardship, open participation and global coordination. Those materials are useful evidence. They should not be treated as the final frame for analysis. An institution's self-description tells us how it understands its role, how it wants legitimacy to be understood and what procedures it has chosen to document. It does not tell us how costs are distributed among users.

The classic registry-legitimacy claim rests on openness, neutrality, technical competence and community support. ICANN's ICP-2 criteria, accepted in 2001, emphasize open and transparent policy procedures, impartial treatment, documented policies, technical capability, financial stability and auditable records. These remain relevant as a benchmark for recognition. They are less complete as a measure of post-exhaustion transaction costs in a mature IPv4 market. A registry can satisfy the recognition logic and still impose disproportionate burdens on small networks.

The same is true of community policy language. ARIN's policy process emphasizes fairness, technical soundness and community support. But "community support" is an ambiguous economic signal when participation is costly. The community includes incumbents with inventory, entrants seeking addresses, brokers, hosting firms, cloud platforms, access providers, enterprises, academics, civil-society participants and legacy holders. A consensus among active participants may not represent the preferences of operators too busy or too under-resourced to participate. Fairness requires attention to the silent cost of non-participation.

Neutrality also needs economic interpretation. A fixed documentation requirement applied to every applicant is procedurally neutral. It is not economically equal if one applicant has counsel and another does not. A public meeting open to all is procedurally open. It is not equally usable for a network whose engineer cannot leave the network unattended. A transfer fee applied identically to every transaction is clear. It has a different per-address effect on a /24 buyer than on a large-block buyer. The question is not whether ARIN treats applicants according to stated rules. The question is whether the stated rules impose avoidable marginal burdens on the smallest legitimate participants.

This is why analysis must focus on incentives rather than slogans. ARIN has incentives to preserve trust, avoid fraud, maintain records, recover costs, protect confidentiality, follow community-developed policy and avoid litigation. Small operators have incentives to obtain usable resources quickly, minimize cash outlay, satisfy customers and avoid dependence on lessors or upstreams. Large operators have incentives to preserve optionality, influence rules and manage inventory strategically. Legacy holders have incentives to preserve rights and monetize scarcity. Brokers have incentives to increase liquidity and transaction volume. Outcomes emerge from these incentives, not from public language alone.

The practical question is simple: when ARIN's documented commitments meet IPv4 scarcity, who pays for the gap between the ideal process and the lived transaction? The answer is rarely the largest participant. It is usually the operator whose next block, next ASN, next certificate or next transfer determines whether it can compete.

Accountability that can be measured

Elections are necessary but insufficient for accountability. Members can vote, candidates can stand, policy can be discussed and Board decisions can be reviewed. But the risks facing small operators often arise below the level of election politics. They involve ticket timing, documentation burden, fee clarity, transfer handoff, waiting-list predictability, agreement status, routing-security updates and appeal costs. A small operator cannot efficiently solve a delayed transfer by voting once a year.

Operational accountability requires service metrics. How long does an 8.3 transfer take from first complete submission to approval, by block size and source type? What share of delays comes from source authority, recipient need, unpaid fees, agreement execution, inter-RIR coordination, unclear documents or staff evaluation? How often are small transfers abandoned after fees are paid? How many waiting-list offers are declined and why? How many approved requests are removed because a transfer satisfied the need before a distribution? How often do legacy-resource transfers require corporate-history reconstruction? These questions can be answered in aggregate without disclosing confidential transaction details. They are the registry equivalent of latency, packet loss and error codes.

Financial accountability requires small-operator modeling. A fee schedule should not be assessed only by aggregate revenue sufficiency. It should show the all-in path for common scenarios: a first ASN and /24; a /23 transfer by a small hosting firm; a move from /24 to /22 for a fixed-wireless provider; acquisition of a legacy block; a Caribbean data-center deployment; a merger of two small providers; and a transfer that changes membership status. The point is not that every fee should be lower. It is that the Board, members and affected users should see where the marginal burden falls.

Policy accountability requires readable impact notes. A proposal that changes transfer restrictions, waiting-list eligibility or needs assessment should explain the effect on organizations below /20, first-time requesters, holders of a single direct allocation, legacy holders not under agreement and entrants without previous ARIN allocations. This is distributional analysis, not special pleading. In a scarce market, every rule has an economic incidence. The incidence should be visible before adoption, not discovered by applicants afterward.

Appeal and reconsideration mechanisms must also be proportional. A right to appeal is weak if exercising it costs more than the block is worth or consumes the entire commercial window. Small operators need written reasons, predictable escalation, neutral review and examples of correctable defects. A denial may be substantively correct, but a black-box denial teaches the applicant little and makes the next transaction riskier. Good accountability reduces both wrong decisions and the fear that correct decisions are arbitrary.

Data publication should be more durable and more structured. Human-readable pages are useful but not enough for market participants and researchers who need to track timing, waiting-list health, transfer volumes, fee changes and service eligibility. Machine-readable historical data would make it easier to detect deteriorating performance, seasonal bottlenecks and small-block access problems. A registry administering critical identifiers should expect to be monitored.

Accountability finally requires humility about exit. ARIN is not a normal vendor. A network cannot easily switch regional registry for resources that belong in the ARIN region, and a buyer cannot make registry recognition irrelevant by contract. Where exit is impossible, transparency must do more work. Small operators depend on ARIN more than they depend on most suppliers because the registry's recognition is not substitutable. That dependency creates a higher duty of explanation.

What a small-operator standard would require

A small-operator standard would not mean special favors, weaker anti-fraud controls or politicized allocation. It would mean testing every major registry rule against the circumstances of an operator with limited staff, limited capital, real customers and no legacy inventory. Such a standard would ask whether the operator can understand the requirement, price the risk, gather the evidence, bear the fee, wait the expected time and contest an error without losing the commercial opportunity the resource was meant to support.

The first element is time certainty. ARIN should publish expected processing ranges by transaction type, block size, source type and inter-RIR status, along with explanations for cases that leave the standard path. Time certainty is not a promise of approval. It is a promise that silence will not become a hidden tax. When a case is delayed, the applicant should know whether the delay is waiting on the source, the recipient, fees, agreements, another registry, legal review or staff evaluation.

The second element is evidence clarity. ARIN already describes requirements, but small operators need examples that resemble their actual situations. A new broadband entrant, a small cloud provider, a Caribbean data center, a rural fixed-wireless operator, a managed-services provider and a small merger case should each have a public evidence guide. Such guides can be anonymized and non-binding. They should distinguish mandatory evidence from helpful evidence, anti-fraud checks from business-plan review, and utilization proof from speculative forecasts.

The third element is transaction observability. Applicants should be able to see where their case sits without breaching confidentiality. A status taxonomy would reduce panic, repeated support contact and broker dependence. It would also discipline the institution by making bottlenecks visible. The current distinction between final transfer speed and pre-approval uncertainty is too large to leave unmeasured.

The fourth element is fee-path transparency. A small operator should be able to model all registry charges before beginning a common transaction. If a fee is non-refundable, that risk should be prominent. If outstanding fees by either party can block completion, the buyer should know early. If membership status changes after a transfer, that consequence should be modeled. If the 2027 fee schedule changes the economics of small categories, the effect should be shown through examples, not only tables.

The fifth element is governance translation. Policy proposals and Board decisions should include a small-operator impact statement addressing cost, timing, documentation, voting rights, routing-security access and legacy implications where relevant. This would not give small operators a veto. It would make open governance usable for participants who cannot spend their lives in policy discussions.

The sixth element is legacy modernization. ARIN should make it easier for legitimate legacy supply to become clean, transferable and secure without creating avoidable uncertainty for buyers. Clear agreement choices, transparent fee effects, predictable handling of corporate-history issues and fast service eligibility after transfer would improve liquidity and reduce risk premiums. Legacy clarity is a small-buyer issue as much as a legacy-holder issue.

The seventh element is proportional review. A small transfer should not require a level of process better suited to a strategic acquisition unless there is a concrete risk signal. Anti-fraud controls can be strong and still risk-based. The goal is not to make small transfers casual. It is to prevent the fixed cost of caution from overwhelming the value of legitimate small-block transactions.

Such a standard would strengthen ARIN rather than weaken it. The institution's legitimacy depends not only on avoiding fraud and preserving records but on being seen as a fair dependency manager for the whole region. If small networks can navigate the system without specialized intermediaries, confidence rises. If they cannot, the market will increasingly treat institutional navigation as a private advantage.

Watchpoints for the next 12 to 24 months

The first watchpoint is fee transition. ARIN has adopted a new fee schedule effective 1 January 2027. The critical issue is not simply whether fees rise. It is how fee changes interact with small-block economics, legacy caps, transfer processing, routing-security access and membership rights. A schedule that is moderate in aggregate can still shift the marginal cost of participation for the smallest networks. The public record should show common paths, not only categories.

The second watchpoint is full-cycle transfer timing. ARIN should be evaluated not only on the speed of the final update after approval but on the entire path from first complete submission to usable resource. Inter-RIR transfers deserve separate attention because coordination across registries can introduce variable delay. Public data should distinguish applicant delay, source delay, fee delay, agreement delay, another-registry delay, legal review and staff evaluation. Without that distinction the market cannot know whether friction is caused by weak applicants, seller defects, policy complexity or institutional capacity.

The third watchpoint is waiting-list health. Useful indicators would include approved requests by size, the age of the oldest unfilled requests, the number and size of blocks returned or revoked, the number of declined offers, the number of requests removed because transfers supplied the need, and the degree of mismatch between returned inventory and approved demand. A waiting list under scarcity is a rationing institution. Rationing institutions need auditability.

The fourth watchpoint is legacy-resource certainty. Market liquidity depends on whether legacy holders can bring resources into transfer and routing-security services without excessive ambiguity. Buyers need to know how agreement choices affect services, how pre-2024 and post-2024 fee treatment affects behavior, and how corporate-history issues are resolved. If legacy uncertainty keeps supply off the market, small buyers pay more. If legacy supply moves with weak clarity, small buyers inherit risk.

The fifth watchpoint is member-power concentration. ARIN should track election turnout, meeting participation, policy-comment diversity and candidate engagement by member size where privacy permits. The absence of small operators from a debate should not be taken as proof that the debate has no small-operator impact. Organized attention is a scarce input; governance design should not pretend otherwise.

The sixth watchpoint is routing-security transition. As RPKI and related services become routine expectations, the registry's handling of certificates, route origin authorizations, IRR data and reverse DNS becomes more central to commercial usability. Small operators need fast and clear pathways to secure transferred resources. A transfer that is legally recognized but operationally awkward is not a complete success.

The seventh watchpoint is political temperature. Registry politics becomes dangerous when debates stop being about clear operational criteria and become contests over institutional control, regional identity or rent preservation. ARIN's governance environment is more stable than some other registry settings, but stability should not be confused with immunity. Scarcity creates rents, rents attract politics, and politics imposes its highest cost on those least able to influence the outcome.

Conclusion: the small-network test

ARIN is a useful test case because it is stable enough for its frictions to matter. A failing registry would create obvious risks. A functioning registry with uneven transaction costs creates subtler ones. North America's small operators do not need ARIN to collapse to be harmed. They need only a system in which waiting is unpredictable, transfer approval is hard to price, legacy-resource certainty is uneven, member power rewards organized attention, and routing-security modernization adds another administrative layer.

The evidence is concrete. The free pool is exhausted. The waiting list is limited, conditional and dependent on returned inventory. Transfers require registry approval, documentation, fees, agreement status and sometimes inter-RIR coordination. Legacy resources carry distinct histories and service questions. General Members have election rights that Service Members do not. Public materials are extensive, but they are not always optimized for transaction planning. IPv4 prices remain high enough that delay and uncertainty have real financing consequences. These facts do not require an anti-ARIN conclusion. They define the environment in which ARIN's accountability should be assessed.

The institutional lesson is that dependency risk rises when an essential input moves from abundance to rationing. In abundance, a registry can be mostly administrative. In scarcity, it becomes a market-shaping institution. Its rules influence prices, entry, competition and resilience. The smaller the operator, the less it can diversify away from those rules. A large network can hold inventory, influence policy, hire counsel and wait. A small network buys near need, learns by doing and absorbs mistakes directly.

The right standard is therefore not whether ARIN can explain its rules. It usually can. The standard is whether a legitimate small operator can use those rules without disproportionate risk. If the answer is uncertain, the remedy is not deregulation. It is sharper transparency, faster and more observable processing, better evidence paths for small networks, fee-impact modeling, legacy clarity and governance practices that recognize the cost of attention. Scarcity cannot be repealed, but institutional uncertainty can be reduced. Over the next 12 to 24 months, ARIN's treatment of small-operator dependency will show whether the North American registry model can adapt from allocation stewardship to scarcity governance without entrenching the advantages of incumbency.