Summary
- New entrants in the ARIN region face a proof-before-revenue problem: they need IPv4 evidence, routing credibility, customer commitments and financing confidence before the address capacity that would make those commitments bankable is available.
- Formally neutral scarcity rules can preserve inherited positions because incumbents possess legacy holdings, operating history, established registry records, cleaner procurement files and more administrative capacity than firms trying to enter after exhaustion.
- Transfers, leasing, CGNAT, cloud egress and the waiting list are necessary bridges, but each converts address scarcity into a different price: cash, delay, dependence, support burden, reputation risk or weaker customer SLA credibility.
- ARIN's strongest role is restrained and ledger-first: protect uniqueness, authority, record accuracy and anti-fraud discipline while making the evidentiary path legible enough that neutrality does not become a mechanism for conserving incumbency.
Neutrality can preserve the past
The most important feature of post-exhaustion IPv4 policy is not that addresses are expensive. It is that the moment of entry has moved. A firm that joined the Internet economy when IPv4 supply was still broadly available entered one institutional world. A firm that tries to join now enters another. The first built operational history while addresses were allocated at administrative terms. The second must build operational history while address scarcity is already priced into transfers, leases, upstream bargaining, customer contracts and financing conversations.
That difference can survive even if every current rule is written neutrally. A rule that asks every applicant to prove need favors the organization that already has customers. A rule that asks every buyer to document use favors the organization with a long assignment file. A rule that asks every network to maintain accurate contacts favors the organization with a policy staff, counsel or experienced consultants. A rule that asks every resource holder to stay current on fees favors the organization whose treasury function is mature enough to treat registry standing as routine. None of these effects proves bad faith. They show how neutral administration can interact with unequal starting positions.
ARIN's factual setting is clear. The free IPv4 pool reached zero on 24 September 2015, and ARIN's public material now presents the waiting list, transfer mechanisms and reserved pools as the remaining channels by which organizations may obtain IPv4 addresses from the registry environment. The Number Resource Policy Manual, listed by ARIN as version 2025.1 in March 2026, continues to organize number resources around registration, conservation, routability and stewardship. The waiting-list page describes eligibility limits, aggregate caps, one-request rules, fee standing requirements, removal from the list after receipt through specified channels, and a 60-month transfer restriction for waiting-list space outside permitted reorganization cases. These are not rhetorical claims. They are the institutional facts inside which entrants operate.
The economic question is different from the administrative fact. It is not whether scarcity controls are defensible in the abstract. Scarce public number resources cannot be distributed casually. Fraud must be checked. Duplicate claims must be avoided. Records must support routing, reverse DNS, abuse handling and public reliance. The question is who can comply cheaply. Incumbents generally comply with the evidence of operations already built. Entrants comply by projecting operations that depend on the very address capacity under review.
This is why new-entrant disadvantage is narrower than ordinary small-ISP difficulty. A small operator may face tower leases, construction risk, expensive backhaul, marketing problems and customer-support costs that have little to do with ARIN. New-entrant disadvantage, as a scarcity institution, concerns the asymmetry between historical proof and prospective proof. The incumbent's need looks like fact because the network exists. The entrant's need looks like intention because the network is still forming. A neutral reviewer will naturally find fact more comfortable than intention. A neutral bank will do the same. So will an enterprise buyer, an upstream provider, a public-sector procurement office and a data-centre landlord.
The institutional trap is that fairness can be measured at the counter while advantage is created before the counter. If two firms submit the same kind of request under the same written rules, the visible procedure may be equal. Yet one firm arrives with inherited address capital, customer history, routing reputation, bank references and staff who know how to answer questions. The other arrives with a plan, a sales pipeline and a funding gap. Treating these positions as equivalent may preserve inherited positions precisely because the rules are not openly discriminatory. Scarcity has shifted the burden from allocation quantity to proof capacity.
For ARIN, the implication is not that every new entrant should receive a subsidy or that the registry should become an industrial-policy office. The implication is that registry restraint must include distributional awareness. A restrained registry does not merely avoid favoritism. It also avoids needless evidentiary complexity that turns old incumbency into a private translator of the public rulebook. Neutrality is valuable only if the neutral path can be used by firms that do not already possess the proofs that neutrality asks them to show.
The proof-before-revenue trap
The central mechanism is proof before revenue. A new entrant needs addresses to sell service credibly, but it often needs credible demand to justify or finance addresses. This is not a philosophical puzzle. It appears in procurement files, lender conversations, transfer negotiations, customer trials and upstream acceptance. The entrant must demonstrate that its network will use public IPv4 responsibly before the customer base that would demonstrate responsible use has fully arrived.
Consider a regional access provider preparing to enter a neglected suburban, rural, island or small-city market. It may have financing discussions under way, local permits in progress, tower or fibre access arranged, a core design prepared, IPv6 included from the start and a list of businesses willing to consider service once the network is live. The founder can show commercial seriousness. What she may not be able to show is the kind of historical utilization file that an incumbent can produce with little effort. Her demand is real but contingent. Customers will not sign firm orders without confidence that service will work. Financing will not close without confidence that address supply and routing acceptance are stable. Address supply is hard to obtain without evidence that demand is more than speculative.
This is the entrant's circularity. Need is evaluated through evidence, and the best evidence is often produced by prior access to the scarce input. The incumbent avoids the circle because its past allocation created the conditions that now prove its present need. It can show invoices, assignments, subnet use, reverse-DNS patterns, abuse-contact history, customer migrations and route announcements. It may also show internal reallocation from old products to new ones. The entrant can show plans, letters of intent, construction schedules and forecasts. Those can be strong documents. They are still documents about a future state.
The problem is sharpened by the economics of timing. Before revenue, every delay is financed with equity, debt, supplier patience or personal risk. A large incumbent can treat additional IPv4 capacity as one procurement item among many. A new entrant may treat it as a condition of launch. If a transfer review takes longer than expected, a lender waits. If a lease negotiation stalls, an enterprise pilot slips. If an upstream wants clearer authority evidence, routing is delayed. If the waiting list is uncertain, the launch plan needs a paid bridge. The same calendar delay has different incidence.
Need-before-revenue evidence is also culturally difficult. Network operators and registry staff tend to value operational proof because networks are supposed to be real. That instinct is sound. A registry should not allocate scarce resources on the basis of vague ambition. Yet entry always begins with some ambition. The discipline should be to distinguish credible prospective demand from speculation, not to treat prospective demand as inferior merely because the applicant is new. Signed customer commitments, staged deployment plans, financing letters, public-sector award documents, engineering designs, IPv6 transition plans, NAT capacity models and upstream contracts can all be meaningful. They should not need to mimic an incumbent's historical archive in order to be believed.
The entrant's evidence costs are partly fixed. Learning the policy language, preparing diagrams, tracing ownership, confirming signatory authority, arranging letters of authorization, planning reverse DNS, preparing abuse contacts, explaining CGNAT, describing assignment practices and maintaining fee readiness take professional time. A national provider spreads that time across many transactions. A first-time entrant spends it before scale. The fixed nature of the burden makes it regressive even when the rule is formally equal.
The danger for ARIN is not that it checks need. The danger is that need review becomes an initiation rite into a scarcity market. A careful file is necessary. A file whose cost silently assumes prior experience is different. It turns the registry's evidentiary language into a moat around the firms that learned it earlier.
Transfer price is the entry tariff
The transfer market is the most direct expression of post-exhaustion scarcity. It moves already-issued IPv4 resources from holders to recipients through recognized policy channels. For many entrants, it is not optional. The waiting list is narrow, small and uncertain. Provider-assigned addresses may weaken independence. Leasing may be temporary. CGNAT may damage quality. If a network wants portable public IPv4 capacity that it can present to customers, lenders and upstreams, the market price of a transfer becomes the effective entry tariff.
The tariff is not only the price per address. It includes search cost, broker cost, diligence, legal review, escrow structure, reputation history, routing preparation, transfer eligibility, registry fees, renumbering, reverse-DNS setup and the working-capital cost of paying before revenue fully materializes. The headline purchase price may be the easiest number to understand and the least complete number in the entry model. A clean, appropriately sized block with credible seller authority and manageable reputation history is worth more than a cheaper block that consumes months of diligence or arrives with mail, abuse or routing complications.
Incumbents experience the same market differently. A holder with legacy space can delay purchases, time sales, use transfers strategically, or finance acquisitions with existing cash flows. It can compare the market price with the opportunity cost of internal conservation. It can decide whether to sell underused space, retain optionality, or shift customers among pools. The entrant cannot arbitrage its own past holdings because it has none. It buys at the market's current scarcity price while competing against firms whose historic address cost was far lower.
That is why transfer price is not merely a commercial inconvenience. It changes competitive selection. A new operator may have a better service concept, local knowledge, faster customer support or stronger incentives to serve overlooked areas. But if its first serious block of IPv4 must be acquired at a price that strains financing, the entrant's cost of capital rises before the first subscriber is connected. The incumbent's inherited address estate behaves like a subsidy without a budget line. It reduces the need for cash and makes the incumbent look safer to lenders.
Market access can still be fairer than discretion. A price, however painful, can be budgeted. A buyer can compare acquisition with lease, lease with upstream supply, upstream supply with NAT, and NAT with lost enterprise sales. Price converts scarcity into a number. Discretion converts scarcity into uncertainty. A healthy transfer market therefore matters to new entrants because it lets them buy certainty when waiting or negotiation with upstreams would be worse.
The problem is a hybrid regime that combines high prices with broad permission uncertainty. If the entrant must pay market rates and also persuade multiple institutions that its future use is sufficiently mature, the tariff includes both cash and delay. If the transfer record is hard for banks or customers to understand, the entrant pays again in credibility. If smaller blocks are relatively expensive or less attractive to sellers and brokers, the operator most likely to need a small start pays a worse effective price. If the block's history is obscure, the entrant pays for diligence that a repeated buyer or large incumbent can perform more cheaply.
ARIN cannot and should not set market prices. It can affect entry by making recognition predictable and narrowly focused on what a registry is best placed to verify: authority, uniqueness, accurate records, policy compliance, contact clarity, and the absence of unresolved disputes that would make recognition unreliable. The less the registry adds avoidable uncertainty, the more the transfer price remains a market price rather than a combined price of scarcity and institutional opacity.
The waiting list is a side door, not a growth model
ARIN's waiting list matters for entrants, but it should not be mistaken for the main story. It is a residual fairness instrument for returned, revoked or otherwise available IPv4 inventory. It can help a qualifying smaller organization obtain a modest block without paying transfer-market prices. It can provide an outside option in negotiation. It can signal that the registry is not abandoning the idea that some scarce public inventory should be distributed under public rules. Those are real functions.
They do not turn the list into an entry strategy. ARIN's waiting-list page states that organizations holding more than a /20 equivalent in aggregate, excluding specified special-use space, are not eligible to apply; the maximum aggregate an organization may qualify for at any one time is a /22; only one request may be on the list at a time; receipt of IPv4 space through the waiting list, an 8.3 specified recipient transfer, or an 8.4 inter-RIR transfer removes the organization from the list; and fulfillment depends on the size and quantity of address blocks ARIN receives back into inventory. These conditions make the list modest by design.
For an entrant, modesty has two meanings. It protects against capture because a large holder cannot use the list to obtain more residual supply while retaining a large estate. It also means the list cannot underwrite a business that requires predictable scale. A /22 may be very useful for a small hoster, WISP, municipal service, local enterprise network or Caribbean access provider. It is not a replacement for a larger transfer if the business model requires many public endpoints, clean customer pools or room for rapid growth. A /24 may unlock a phase. It does not remove the need for a longer address plan.
Waiting-list timing is a cost, but it is not the main cost in this article. The deeper issue is what the list teaches new entrants about institutional position. The entrant learns that public residual supply is small, eligibility is narrow, timing is uncertain, block size matters, accepting other IPv4 through specified routes can remove the request, and fee standing must be maintained even while the business waits. The list may be fair, but fairness does not eliminate the need to finance a bridge.
That bridge is where disadvantage returns. The entrant may lease while waiting. It may buy a small transfer and thereby lose list position. It may design around CGNAT and reserve public addresses for business accounts. It may use upstream or cloud egress. It may delay a product. Each choice has cost and each cost is incurred before the waiting-list outcome is certain. A large incumbent, by contrast, often treats the list as irrelevant. Its advantage is not that it can use the side door; it is that it does not need the side door.
The policy danger is symbolic overclaim. A residual queue can make scarcity look more equitable than it feels in the market. Because the list exists, observers may infer that smaller entrants have a practical path. Some do. Many still need market or supplier bridges. The correct evaluation is not whether the list is virtuous in isolation, but whether a new network can combine the list, transfers, leases, IPv6 and address sharing into a bankable route to operation.
ARIN's restraint should preserve the list's narrow purpose. It should not become an industrial-planning tool, a substitute for transfer liquidity, or a political excuse to ignore inherited address concentration. The list can mitigate scarcity at the margin. It cannot erase the past.
Administrative capacity is a competitive asset
In a scarcity regime, paperwork is not clerical. It is economic infrastructure. The organization that can prepare a clean file, answer questions quickly, maintain current contacts, coordinate counsel, satisfy fee requirements, document use, verify seller authority, produce customer evidence and keep transfer or waiting-list status moving has a competitive asset. It may not appear on the balance sheet, but it lowers the cost of obtaining and defending address capacity.
Administrative capacity is unevenly distributed. Incumbents have staff who have dealt with ARIN for years. They know what a Point of Contact record is supposed to show, how organization authority is maintained, how reverse DNS and routing security relate to customer commitments, how fee notices move through finance, and how transfer documentation should be sequenced. Large firms may also have counsel, brokers, consultants and internal policy specialists. They can turn registry interaction into a repeatable function.
A new entrant may have two engineers, a founder and a bookkeeper. The same people may be securing permits, installing equipment, negotiating transit, answering customer leads and preparing an address request. A clarification that takes a larger organization one afternoon may take the entrant two weeks because it depends on a customer letter, a bank confirmation, an upstream statement or a legal signature from someone already handling other formation tasks. This is not incompetence. It is the fixed cost of formalization landing on a small team.
The administrative disadvantage is especially important because public number-resource records are used by many counterparties. An upstream may ask for a letter of authorization or registry evidence before accepting a route. A data centre may want clear organization records. A public-sector buyer may require proof of stable Internet number resources before awarding a service contract. A lender may look for continuity in registration. A security-sensitive customer may ask about abuse response and reverse naming. Every such request turns ARIN-facing evidence into commercial evidence.
The entrant's challenge is not only to be compliant. It must make compliance readable to outsiders who are not registry experts. A bank officer may not understand the subtleties of NRPM 8.3 or 8.4. A procurement official may not know why a waiting-list block has transfer restrictions. A hospital, school district or municipal buyer may not distinguish provider-assigned space from portable space. They ask the practical question: will this supplier be able to maintain service? The incumbent answers with history. The entrant answers with a file.
This makes clarity a competition policy. Plain guidance, predictable status categories, stable public records, readable explanations of waiting-list consequences, understandable transfer requirements and clear public tools reduce the premium on prior experience. If an entrant can prepare correctly without hiring a specialist, the rule has become less regressive. If it must buy interpretation from the same market actors that profit from closing scarce-resource deals, the public rulebook has created private toll booths.
The test is practical. Could a serious entrant with competent engineers but no prior ARIN transaction history identify the right path, estimate the evidence burden, explain the result to a lender, and maintain status without insider translation? If not, neutrality is being filtered through administrative wealth.
Legacy holdings are institutional capital
Legacy and incumbent address holdings are often discussed as property, stewardship, market liquidity or record accuracy questions. For new entrants, they are more simply institutional capital. They let old organizations operate with a cushion that new organizations must buy, lease or simulate through sharing. They create commercial flexibility while appearing as ordinary historical fact.
An incumbent with inherited IPv4 space can reserve public addresses for customers whose value or risk justifies them. It can run denser NAT for low-margin users while preserving better address treatment for enterprise accounts. It can maintain mail, VPN, monitoring, payment, remote-access and hosting services with fewer translation compromises. It can stage migration slowly. It can absorb a failed product without immediately returning to the transfer market. It can treat address scarcity as portfolio management.
The entrant has fewer degrees of freedom. If it buys too much, capital is locked into an input before demand is proven. If it buys too little, customers may outgrow the design. If it leases, renewal and authority questions remain. If it relies on upstream space, independence is weakened. If it uses CGNAT heavily, support and reputation costs arrive early. If it waits, customers may choose the incumbent. These are not merely operational choices. They are the cost of not having inherited stock.
Historical stock also supports reputation. Addresses that have been routed for years by a stable organization, backed by known contacts and observed patterns, are easier for counterparties to trust. A new block transfer may be clean, but it must still be introduced into a new operating context. A leased block may be legitimate, but the customer may worry about continuity. An upstream assignment may work, but the entrant may struggle to present it as independent capacity. The incumbent's address estate is therefore both technical resource and credibility resource.
The institutional question is whether the public record treats legacy history as useful evidence without turning it into unearned superiority. Old records matter. They help prevent duplication, clarify authority, support security and make routing coordination possible. But old records are also a record of past access. A firm that lacks them may be new, not unserious. A registry that demands incumbent-style historical evidence from entrants risks confusing age with merit.
This distinction matters for debates about conservation. Conservation remains important because IPv4 is scarce and waste has social cost. But conservation applied mainly to future applicants protects the stock accumulated by the past. The incumbent can "conserve" within a large inherited estate and decide when to monetize or redeploy surplus. The entrant conserves by building a constrained architecture from the beginning. If policy rhetoric praises conservation without acknowledging inherited stock, it can sound impartial while leaving the largest distributional fact untouched.
ARIN does not need to punish legacy holders to recognize this. Many legacy and incumbent holders use their space productively. Some serve public institutions, universities, hospitals, businesses and critical networks. Some have slowly rationalized address plans or entered the market as sellers. The point is not moral blame. It is economic incidence. The old allocation era created capital-like advantages. A post-exhaustion registry should be careful not to make those advantages stronger through unnecessary proof burdens, slow recognition or unclear bridges for entrants.
The measured approach is ledger discipline plus entry legibility. Preserve accurate legacy records. Support clean transfers. Maintain authority checks. Avoid casual claims over resources that have complex histories. At the same time, make it easier for new organizations to build credible records through current operations, staged evidence and reliable public documentation. The past should be recorded. It should not become the entrance exam.
Reputation, history and SLA credibility
Customers rarely buy Internet service from a registry file, but registry evidence often sits behind the promise a provider makes. The promise may be an enterprise SLA, a hosting commitment, a public-sector contract, a security monitoring service, a disaster-recovery plan or a business broadband agreement with static addressing. In each case, the buyer asks whether the provider can keep service stable. IPv4 capacity is only one component, but it remains a visible proxy for operational maturity.
Incumbents benefit because continuity is credible even before it is explained. A long-running provider can point to existing prefixes, previous customers, established abuse contacts, reverse-DNS habits, route objects, RPKI experience, familiar upstreams and a service desk that has handled incidents. Even if the incumbent's service quality is mediocre, its continuity story is easy to understand. It has been there. It has addresses. It has history.
The entrant must convert design into trust. If it uses purchased portable space, it must explain that the transfer is recognized and the block is clean enough for the customer's use. If it leases space, it must explain authorization, renewal and operational control. If it uses upstream-assigned addresses, it must explain what happens if the upstream relationship changes. If it uses CGNAT, it must explain logging, port behavior, inbound-access limitations and exceptions. If it depends on cloud egress for some services, it must explain dependence on platform terms, geolocation, reputation and routing. Every explanation lengthens the sales cycle.
SLA credibility is therefore not only about engineering. It is about the customer's tolerance for institutional complexity. A small business may accept a cheaper connection behind NAT. A bank, clinic, law firm, industrial site, school district or government office may not. They may have allowlists, audit requirements, remote-access rules, third-party software restrictions, cyber-insurance questionnaires or vendor-risk forms that assume stable public addressing. The incumbent can answer many of these questions with routine documentation. The entrant may have to educate the buyer and carry the risk that education becomes doubt.
The reputation problem also includes address history. A newly acquired or leased block may carry geolocation errors, mail reputation problems, previous abuse listings or outdated contact data. A large operator has tools and staff to remediate these issues. A new entrant may discover them only when customers complain. The customer's conclusion may be harsh: the new provider is unreliable. The underlying cause may be address scarcity and imperfect history rather than poor network design, but the market rarely separates them.
This is why public records matter beyond the registry community. RDAP, Whois, reverse DNS, routing-security publications and recognizable organization authority help customers and intermediaries translate a new provider into an institution they can trust. The more reusable those public records are, the less the entrant must substitute personal persuasion for institutional proof. The record cannot create reputation by itself, but it can reduce the discount applied to the absence of history.
ARIN's restraint should therefore be paired with record usability. A ledger-first registry does not decide which customer deserves a public address, but it provides evidence that a legitimate operator can reuse. The better the evidence, the less customer trust is monopolized by incumbents. Conversely, if public records are confusing or slow to update, private reputation becomes more important. Private reputation is exactly where incumbents hold the advantage.
The practical risk over the next 12 to 24 months is that scarce IPv4 becomes a differentiator in enterprise and public-sector sales even when buyers do not name it directly. They may ask for stable service, clean security posture, predictable logging, vendor continuity and contract remedies. The entrant hears a broader question: can you prove that your public Internet identity is durable? In a post-exhaustion region, that proof is expensive.
Bankability starts with address certainty
Bankability is the financial translation of operational trust. A network project becomes bankable when a lender, investor, equipment vendor or anchor customer believes that the operator can turn capital expenditure into stable revenue. In the ARIN region, address certainty affects that belief. It does not replace demand, management, construction quality or pricing. It influences whether those other inputs are credible.
A lender financing a new access network may not care about IPv4 policy in detail. It cares whether the customer forecast is plausible, whether service can be delivered, whether supplier contracts are stable and whether an interruption would damage cash flow. If the network plan depends on public IPv4 capacity that is not yet acquired, leased or otherwise secured, the lender sees execution risk. If the plan depends on waiting-list timing, it sees uncertainty. If the plan depends on CGNAT, it may ask whether enterprise revenue is overstated. If the plan depends on leased addresses, it may ask about renewal and control. If the plan depends on upstream assignments, it may ask whether the entrant can switch suppliers.
The incumbent can present address capacity as part of the operating estate. It may not need to pledge addresses as collateral or even list them as a separate asset. Their value appears in lower execution risk. The entrant must often explain address capacity as a planned acquisition, a lease, a technical workaround or a policy-dependent future event. This raises the cost of capital because the uncertainty is loaded into interest rates, equity requirements, supplier credit, or the size of the first deployment.
Bankability also affects the transfer market itself. A buyer that can finance a larger clean block may reduce future uncertainty and avoid repeated transaction costs. A buyer that cannot finance enough capacity must return to the market more often, lease at higher effective rates, or design around shortage. Repeated small transactions can cost more per address and per staff hour. Scarcity therefore penalizes undercapitalization, and new entrants are often undercapitalized precisely because they have not yet built the revenue that address certainty would support.
Public-sector grants and development programs do not necessarily solve this. A broadband grant may fund construction but not fully account for public-address acquisition, transfer diligence, NAT logging or the cost of maintaining clean address reputation. A municipal or Caribbean infrastructure program may require service milestones that assume address availability without pricing the scarcity premium. If public money is released against deployment dates, the entrant may be forced into expensive bridging arrangements to avoid missing milestones.
ARIN cannot finance entrants. It can reduce needless uncertainty in the part of the financing file it controls. Clear evidence expectations, predictable recognition, timely public record updates, reliable fee and agreement instructions, and plain explanations of waiting-list consequences make it easier for an entrant to tell a bank what is secured and what is contingent. That does not lower the market price of IPv4. It lowers the institutional risk premium around the price.
The opposite posture turns the registry into an unintentional credit allocator. If small entrants cannot explain the path to address certainty, capital will prefer established operators. A bank may not say "ARIN risk" in the credit memo. It may simply lower the project size, require more equity, exclude certain revenue, demand an incumbent partnership or reject the application. The address system has then shaped market structure without a formal decision to do so.
This is one reason new-entrant disadvantage is a governance issue rather than just a commercial issue. A registry record is public infrastructure for private contracting. If it is legible, it supports competition. If it is opaque, it pushes finance toward those who already have a record.
Public-sector procurement amplifies incumbency
Public-sector procurement is one of the places where neutral requirements can most strongly preserve incumbency. A government agency, school district, hospital authority, emergency-service body or public university often buys communications services through formal tenders. These tenders may ask for previous contracts, continuity plans, cybersecurity controls, logging capacity, public addressing, service-level guarantees, references, insurance, financial strength and compliance with various standards. The requirements may be reasonable. Together they favor suppliers with operating history.
IPv4 scarcity enters these tenders indirectly. A buyer may not ask for "a legacy address estate." It may ask for static public addresses, reliable remote access, clean allowlisting, reverse DNS, audit-ready logs, continuity in routing, stable abuse contacts, lawful-response capability or a track record with similar public institutions. The incumbent can provide a familiar package. The entrant may be able to engineer an equally good or better service, but the proof is more complicated if address capacity is leased, newly transferred, upstream-provided or heavily shared.
This matters because public-sector contracts can be anchor revenue for entrants. A local broadband provider may need a school, clinic, municipal office or emergency-service network to make the first build economical. A Caribbean operator may rely on government and tourism-related institutional demand to justify capacity. A regional hoster may need public-sector credibility to persuade private clients. If procurement requirements discount non-incumbent address arrangements, entry is weakened at the moment when it could be most socially useful.
Procurement also has timing rigidity. A tender may have submission dates, implementation windows and penalty clauses. The waiting list cannot be aligned to those windows. A transfer may not close in time. A lease may require extra legal explanation. A CGNAT-heavy design may require exceptions. The incumbent's inherited stock lets it respond within the tender's clock. The entrant's address plan may be commercially sound but procedurally late.
The public-sector effect is not limited to government. Large enterprises behave similarly. They prefer suppliers that can pass vendor-risk reviews and answer address questions without novelty. A first-time entrant may find that the technical service is easier to build than the assurance file. Its disadvantage is not that buyers are irrational. Buyers rationally avoid unfamiliar continuity risk. Scarcity makes new entrants unfamiliar for longer.
There is a policy lesson here for ARIN, but it is modest. ARIN should not rewrite procurement rules or guarantee entrant contracts. It can make its public evidence easier to reuse in tenders. Clear organization records, reliable public status, explainable transfer recognition, straightforward route-security documentation and predictable contact data give entrants exhibits that procurement officers can understand. When official evidence is readable, public buyers can evaluate entrants on service quality rather than on folklore about who is "real."
The danger is that public-sector neutrality becomes a mirror of registry neutrality: same requirements, different burden. A tender that asks every bidder for identical continuity evidence may look fair. In a post-exhaustion address market, the firm with inherited IPv4 can satisfy that evidence at lower cost. The public buyer may then select the safer incumbent while believing it has merely enforced quality. That is how institutional incumbency reproduces itself without anyone voting for incumbency.
Bridges are necessary, but every bridge has a toll
New entrants do not simply wait for perfect address supply. They build bridges. They lease IPv4 space. They use upstream-assigned addresses. They deploy CGNAT. They use cloud egress for some workloads. They design IPv6-first services with translation at the edge. They buy a small block and stretch it. They reserve public addresses for customers most likely to require them. These bridges are practical, often unavoidable and sometimes efficient. They are not free.
Leasing can align cost with early revenue better than purchase. It can let a hoster launch, a broadband provider support business customers, or a regional operator bridge a growth period. But leasing exposes the entrant to renewal risk, lessor cooperation, reputation history, authorization evidence and customer questions about control. If a lender or public-sector buyer treats leased address capacity as less durable, the entrant still pays a credibility discount. If the lessor's record or routing arrangements are hard to explain, the discount grows.
Upstream-assigned addresses can be efficient for initial deployment. They may avoid acquisition cost and simplify routing in a provider-dependent model. But they weaken portability. A new entrant that uses an upstream's address space may find it harder to change transit providers, multi-home cleanly, or persuade customers that service continuity is independent of one supplier. The upstream becomes a shadow allocator. It may have no intention of excluding entrants, yet its own scarcity, risk tolerance and commercial incentives shape the entrant's address capacity. If the upstream is also a competitor, the independence problem is obvious.
CGNAT converts address scarcity into support cost. Translation equipment, logging, abuse response, port management, troubleshooting, customer education and exception handling all require money and staff. Some applications work poorly. Some customers notice only that the new provider has more problems than the incumbent. The entrant can build a high-quality CGNAT architecture, but quality costs arrive before scale. The incumbent may already have the address estate or specialized team that makes sharing less visible.
Cloud and managed egress can solve specific reachability problems, especially for application services, remote access or edge hosting. They can also move dependence to platforms with their own pricing, reputation, geolocation and policy constraints. A provider that enters the market to offer local control may begin by outsourcing parts of its public Internet identity. That may be rational, but it weakens the autonomy story the entrant is trying to sell.
IPv6-first design is necessary and strategically correct. It reduces long-run pressure on IPv4, supports modern deployment and aligns with the Internet's eventual direction. It does not remove the entry disadvantage while customers, devices, counterparties, security tools and legacy software still require IPv4 reachability. An incumbent can use IPv6 transition as gradual optimization. A new entrant may need to explain why it is both modern enough to use IPv6 and still dependent enough on IPv4 to buy, lease or share scarce addresses.
The combined effect is that every bridge has a toll: cash, delay, dependence, operational complexity, credibility discount or customer friction. The policy error is to cite the existence of bridges as proof that entry is fine. Bridges prove that operators are adaptive. They do not prove that the competitive field is level. In many cases the entrant's bridge is the incumbent's optional optimization. That is the asymmetry.
ARIN's role is to make legitimate bridges legible where they touch the registry layer. It should not supervise every lease or customer arrangement. But it can help ensure that authorization, public records, contacts, route-security eligibility and transfer recognition are understandable. When a bridge is verifiable, counterparties can price it rationally. When it is murky, they apply fear, and fear favors incumbents.
Caribbean and regional small-network pressure
The ARIN region is not just the continental United States and Canada. ARIN's published region list includes many Caribbean and North Atlantic jurisdictions, including Anguilla, Antigua and Barbuda, Bahamas, Barbados, Bermuda, Cayman Islands, Dominica, Grenada, Guadeloupe, Jamaica, Martinique, Montserrat, Puerto Rico, Saint Barthelemy, Saint Kitts and Nevis, Saint Lucia, Saint Martin, Saint Pierre and Miquelon, Saint Vincent and the Grenadines, Turks and Caicos Islands, the British Virgin Islands and the U.S. Virgin Islands, alongside the United States and Canada. This geography matters because address scarcity does not hit all subregions with the same market depth.
A small Caribbean operator may face thinner local capital markets, higher equipment import costs, expensive backhaul, hurricane and disaster-recovery requirements, tourism-season demand spikes, public-sector dependence, limited local specialist support and fewer nearby buyers or sellers of IPv4 resources. It may need public IPv4 for hotels, banks, government offices, medical services, remote workers, maritime and aviation services, or local hosting that improves resilience. Its address need may be modest in global terms and still decisive for local competition.
The transfer market may be less comfortable for such an operator than for a mainland buyer with repeated transactions. Brokers may focus on larger deals. Legal templates may assume U.S. or Canadian counterparties. Financing may be denominated in hard currency while revenue is local. A block's geolocation history may matter more when customers depend on regional content rules or fraud controls. A small island operator may not have multiple upstream choices, which makes provider-assigned space a weaker substitute. If it leases, it may face questions about jurisdiction, continuity and reputation that a larger mainland operator can absorb more easily.
Public-sector procurement can be especially important in these markets. Government offices, schools, hospitals, utilities, ports, airports and emergency services may be anchor customers. They may also have strict continuity needs because connectivity failure carries visible social cost. A new entrant that cannot present stable address capacity may lose the anchor contract and with it the economics of broader deployment. The incumbent then retains the market not solely through better service but through inherited credibility.
Waiting-list relief can matter more at this scale because a /24 or /22 may support a meaningful phase of deployment. Yet the same timing uncertainty and eligibility conditions apply. A returned block does not arrive because a hurricane season, government tender or tourism buildout needs it. If the operator must bridge with leasing or upstream space, the bridge may be more expensive relative to revenue than it would be for a larger mainland network.
ARIN need not create separate political economies for each island or subregion. It can preserve a single regional ledger while designing guidance and public evidence for organizations that do not have large policy staffs. Examples, plain-language explanations, predictable request categories, transparent timing caveats and reusable public records are more valuable in thin markets because there are fewer private interpreters. In large markets, complexity can be outsourced. In small markets, complexity can decide whether entry happens at all.
The Caribbean dimension also tests the moral language of neutrality. If neutrality means the same procedure administered consistently, it is necessary. If neutrality means indifference to unequal capacity to use the procedure, it preserves the strongest starting positions. A regional registry should understand both meanings.
Registry restraint is not indifference
ARIN's proper posture in this problem is restraint, not activism. The registry should not decide which entrant has the best business model, which community needs a competitor, which cloud-edge plan is innovative, or which public-sector tender deserves more address capacity. It should not turn number resources into a discretionary development fund. It should not punish incumbents for holding resources that are legitimately registered and used. It should not make price regulation out of scarcity anxiety.
But restraint is not indifference. A restrained registry protects the functions that only it can perform and avoids adding unnecessary burdens around them. It preserves uniqueness. It verifies authority. It keeps records accurate. It supports public registration, reverse DNS and routing-security functions. It recognizes transfers under clear rules. It maintains anti-fraud discipline. It explains waiting-list limits honestly. It keeps fee and agreement requirements readable. It gives applicants and recipients enough information to plan without requiring private access to institutional memory.
This kind of restraint helps entrants because it narrows uncertainty. The entrant can accept that IPv4 is scarce and expensive. It can decide whether to buy, lease, share, wait, use upstream space or redesign. What it cannot easily absorb is a moving institutional target. If evidence expectations are unclear, recognition timing uncertain, public records hard to interpret, or bridges difficult to verify, the entrant's business plan carries risks that an incumbent's plan does not.
Registry restraint also protects ARIN from overclaiming fairness. If ARIN says, implicitly or explicitly, that neutral rules are sufficient because everyone is treated the same, it may miss the way inherited address capital shapes the market. If it says scarcity is purely a market problem, it may ignore how registry evidence affects bankability and customer trust. If it says the waiting list solves small-network access, it may understate the bridge costs that arrive before or after a modest allocation. A restrained institution can be candid about these limits without promising to solve them all.
The institutional danger is mission creep in both directions. One form of mission creep is gatekeeping: expanding need review, suspicion and discretionary interpretation until the registry becomes a quasi-licensing authority for address-enabled business models. That would hurt entrants because permission uncertainty favors incumbents. The opposite form is abdication: treating all post-exhaustion outcomes as private market matters and ignoring the public evidence functions that make markets usable. That would also hurt entrants because weak public records force counterparties to rely on private reputation.
The middle path is hard but coherent. ARIN should keep policy narrow enough to be predictable, strong enough to prevent fraud and duplicate claims, and transparent enough that a first-time entrant can use it. It should measure avoidable friction. It should publish and maintain practical guidance. It should not conflate anti-speculation discipline with hostility to commercial address movement. It should not treat leases, cloud bridges or CGNAT as either moral failures or universal solutions. It should not let conservation rhetoric obscure the fact that conservation falls differently on firms born before and after exhaustion.
This is the Economist-style lesson: institutions need not be villainous to produce regressive outcomes. They need only apply rules designed for scarcity to actors with unequal histories. The answer is not moral theatre. It is disciplined administration, better information and humility about what neutrality can and cannot do.
What to watch over the next 12 to 24 months
The next two years will not decide whether IPv4 scarcity exists. That has been decided. They will show whether ARIN-region scarcity hardens into a durable incumbency premium or remains navigable for credible entrants. The distinction will appear in small operational signals rather than one dramatic policy event.
The first signal is transfer accessibility for smaller buyers. If small and first-time recipients can find appropriate blocks, close transactions, satisfy recognition requirements and explain the result to lenders without excessive specialist dependence, the market can function as a bridge. If suitable blocks become harder to obtain, smaller transactions carry worse effective pricing, or recognition uncertainty persists, transfer price becomes a stronger entry tariff. Public transfer data can show movement, but the more important evidence may come from buyer experience: how long deals take, how often small buyers abandon them, and how often reputation cleanup becomes the hidden cost.
The second signal is waiting-list relevance without overuse. A list that distributes modest space predictably, explains matching limits and maintains clear status can support entry at the margin. A list that applicants misunderstand, rely on too heavily, or use mainly as a symbolic hope may mask deeper market dependence. The important question is not how many addresses the list distributes in isolation. It is whether applicants can make rational business decisions around the list's limits.
The third signal is bridge credibility. Leasing, upstream supply, CGNAT, cloud egress and IPv6-first deployment will remain part of entry strategy. The issue is whether counterparties treat these bridges as manageable or as reasons to discount entrants. If public-sector tenders, banks, insurers and enterprise buyers become more demanding about address continuity, entrants will need better reusable evidence. If the registry layer remains clear, they can provide it. If not, private reputation will fill the gap.
The fourth signal is administrative burden. ARIN can monitor whether first-time requestors and smaller organizations require repeated clarification, miss fee or agreement steps, misunderstand waiting-list consequences, or struggle to identify the correct route between request, transfer, lease-related evidence and routing-security setup. High clarification rates are not only applicant mistakes. They may indicate that the public path is not as legible as experienced participants think.
The fifth signal is Caribbean and small-market participation. If operators in smaller ARIN jurisdictions face the same formal process but disproportionately rely on upstream assignments, avoid portable space, lose public-sector tenders or stay out of transfer markets, the region's neutrality is preserving a geographic asymmetry. This would not necessarily require a separate policy. It would require better evidence about how costs fall across the region.
ARIN's legitimacy will depend less on making IPv4 cheap than on making scarcity administrable. An entrant can survive high prices if it can price them. It can survive modest allocations if it understands them. It can survive proof requirements if the evidence path matches the life cycle of a new business. It struggles when all three are uncertain at once.
The real risk is inherited neutrality
The phrase "new-entrant disadvantage" can sound like a complaint that latecomers deserve special treatment. That is not the argument. The argument is that a post-exhaustion address economy should not mistake inherited advantage for neutral outcome. Firms that entered earlier received opportunities that latecomers cannot recreate. They built customer bases, reputation, staff knowledge and address estates under different scarcity conditions. Current rules operate on top of that distribution.
Some of the resulting advantage is unavoidable. History cannot be unwound. IPv4 cannot be made abundant by administrative generosity. A registry cannot ignore fraud, waste or record accuracy because an entrant has a promising plan. Nor should it force legacy holders to surrender legitimate resources merely to create a cleaner story about equality. Institutional economics is not a demand for fantasy.
It is a demand for honesty about incidence. Need-before-revenue evidence falls hardest on firms without revenue. Transfer prices are most burdensome for firms without inherited stock. Waiting-list delay is most costly for firms that need a launch date. Administrative complexity is most expensive for teams without specialists. Reputation requirements favor firms with history. Bankability favors firms whose address certainty is already embedded in operations. Public-sector procurement favors suppliers whose continuity story is familiar. Caribbean and small-region operators face thinner markets for expertise, finance and substitute supply. Neutrality that ignores these facts conserves the old distribution.
The strongest answer is not preferential treatment. It is a registry environment in which the entrant's legitimate proof can be different from the incumbent's proof without being weaker. Prospective evidence should be disciplined but usable. Transfer recognition should be predictable. Waiting-list limits should be clear. Public records should be reusable. Bridge arrangements should be verifiable where they touch the public ledger. Guidance should be written for first-time users, not only for the policy class. Anti-fraud controls should target fraud, not novelty. Conservation should reduce waste without treating historical surplus as invisible.
For incumbents, this approach is not a threat. A market with credible entrants disciplines service quality and pricing. Accurate records protect all holders. Predictable transfers improve liquidity. Clear guidance reduces disputes. A registry trusted as a restrained ledger is more legitimate than one suspected of being either a gatekeeper or a bystander. The public Internet benefits when new operators can become real competitors without gaming scarcity or begging for exceptions.
For entrants, the message is equally sober. IPv4 scarcity will remain a cost. The business plan must include transfer price, lease risk, CGNAT quality, IPv6 deployment, address reputation, customer education and administrative work from the beginning. The old allocation world will not return. But a scarcity market can still be contestable if the public institutions around it are precise, legible and restrained.
ARIN sits at that boundary. It cannot decide the economics of every network in North America and the Caribbean. It can decide whether its part of the system turns newness into suspicion or into a documented, auditable path to operation. In a mature post-exhaustion regime, that is the difference between neutral administration and inherited neutrality.