Summary

  • A bankruptcy-remote special-purpose vehicle can hold specified IPv4 addresses, leases, receivables and reserves apart from a sponsor's operating liabilities. It can narrow the reasons for its own insolvency and make cash-flow priorities more legible. It cannot guarantee that the relevant Regional Internet Registry will maintain the account, accept a successor, approve a transfer or preserve every related service.
  • Cogent's 2024 and 2025 IPv4 note transactions provide direct public evidence of the distinction. A special-purpose, bankruptcy-remote subsidiary issued two series with $380.4 million of disclosed principal in total, backed by IPv4 addresses and associated commercial assets. The structure proves that isolation is financeable; it does not provide a public test of recovery after registry refusal, issuer insolvency or a contested transfer.
  • Registration is not routing, but it is not decorative. Current ARIN, RIPE NCC and APNIC materials make identity, account status, agreements, fees, policy eligibility and authoritative record updates part of transfer completion. RPKI, Internet Routing Registry entities, reverse DNS and live announcements then create separate operational dependencies.
  • The central risk is institutional concentration. For a given recognised resource and transfer path, the parties normally cannot choose a second authoritative registrar if the incumbent delays, closes an account, disputes authority or becomes unavailable. An SPV may be remote from its parent while remaining fully dependent on this one service route.
  • Credit documents should therefore treat registry continuity as a service-risk problem, not merely as a representation about ownership. The protections are verified chain evidence, independent account contacts, event receipts, exportable records, substitution rights, cash reserves, tested servicing, recipient readiness and a defined migration path if an accredited alternative becomes available.
  • Number Resource Society can contribute a portable evidence and service profile, common event semantics and interoperability tests. It should not certify title, reverse an RIR decision, guarantee a note, rank creditors or present an untested alternative registration service as already authoritative.

The separation works on one axis

The attraction of an IPv4 special-purpose vehicle is easy to see. A corporate group may own or control a large address portfolio while also operating networks, employing staff, signing leases, borrowing for unrelated acquisitions and facing ordinary commercial claims. If investors lend directly to the operating parent, their recovery depends on that entire balance sheet. If selected addresses, customer leases, receivables and cash controls are placed in a limited-purpose issuer, the investors can analyse a narrower pool.

That separation can be real. The issuer can maintain its own books and bank accounts, incur only permitted liabilities, observe entity formalities, grant security over its assets and direct collections through controlled accounts. Its constitutional documents and financing covenants can restrict mergers, additional debt, asset dispositions and voluntary insolvency action. The parent can provide servicing under a documented agreement instead of treating the portfolio as indistinguishable from the rest of the business. Cash can follow a waterfall that pays operating expenses, reserves, interest and principal in an agreed order.

Public financing agreements filed with the United States Securities and Exchange Commission show these as recurring features of bankruptcy-remote entities across asset classes. They commonly require separateness, limited purpose, distinct records and independent decision-making for specified insolvency actions. Those examples explain the architecture; they do not establish that every protection appears in the same form in an IPv4 transaction or that a court must always refuse substantive consolidation.

The word remote is often heard as immune. It means something narrower. The structure is designed to reduce the probability that an affiliate's failure will pull the issuer or its assets into the affiliate's case, and to reduce the probability that the issuer will fail for reasons unrelated to the financed pool. It does not repeal insolvency law. If the issuer itself becomes a debtor, the legal interests it holds can enter its estate and enforcement can encounter the applicable stay.

Under the United States Bankruptcy Code, section 541 broadly identifies the debtor's legal or equitable interests as estate property, while section 362 stays many collection and enforcement acts. Other jurisdictions supply different procedures but the same practical warning: an entity boundary manages insolvency exposure; it does not abolish it.

Nor does the boundary change the identity of an external service provider. A warehouse can be owned by an SPV while remaining dependent on a land registry, utilities and access rights. Aircraft can sit in a bankruptcy-remote vehicle while requiring aviation records and maintenance. IPv4 addresses add an unusual combination: the relevant registry maintains the authoritative allocation record within the established Internet Numbers Registry System, but routing is performed by networks through a separate inter-domain system.

The financier needs both administrative recognition and operational usefulness, even though no one institution delivers the whole package.

That is the axis the SPV does not separate. It can isolate sponsor credit risk. It cannot privately replicate the authoritative registration path on which a recognised transfer, account maintenance and some security services depend.

Cogent demonstrates the structure, not the escape

Cogent Communications supplies the clearest public example of IPv4 assets inside a bankruptcy-remote financing. Its filings state that Cogent IPv4 LLC, described as a special-purpose, bankruptcy-remote, indirect wholly owned subsidiary, issued $206.0 million of 7.924% secured IPv4 address revenue notes in May 2024. In April 2025 the same issuer issued $174.4 million of 6.646% notes. The disclosed principal of the two series is therefore $380.4 million. The anticipated repayment dates were May 2029 and April 2030, while the filings also disclosed much later legal final maturities.

The collateral description is as important as the amounts. Cogent reported that specified IPv4 addresses, customer IPv4 address leases, customer receivables and related assets were contributed to the issuer and included in the collateral. This was not a note secured by a bare list of prefixes. It was a structured pool joining number resources to contracts and cash flows.

The public documents reveal further protections. Interest is scheduled monthly. Principal can become due earlier through rapid-amortisation, mandatory-prepayment or acceleration events. The 2025 issuance placed a portion of proceeds in a segregated prefunding account, with release conditioned on leverage and debt-service coverage tests. The issuer's guarantor pledged the equity interests in the issuer. Cogent also disclosed amendments allowing address dispositions and substitutions subject to a pro forma leverage threshold and other requirements.

These facts support a strong but bounded conclusion. Institutional investors were willing to finance an IPv4 revenue structure through a bankruptcy-remote issuer, and the parties used reserves, ratios, controlled accounts, associated leases and replacement flexibility rather than relying on a simple assertion that an address block could always be sold. The transaction makes bankruptcy remoteness commercially concrete.

The filings do not establish an equally strong conclusion about registry independence. They do not publish every prefix, complete registry correspondence, all legal opinions, each transfer receipt or the recovery analysis for a registry dispute. The private offering memoranda are not reproduced in full through the cited public materials. No disclosed default has provided a public test of how an indenture trustee would cause a non-cooperative transfer, maintain RPKI authority, replace a service agreement or respond to conflicting claimant instructions.

The two coupons are also not the price of registry risk. They belong to one issuer, two dates, a particular collateral pool and complete financing structures. Differences between them may reflect market rates, leverage, coverage, maturity, asset composition, negotiation and other variables. There is no public global population of comparable IPv4 securitisations from which to isolate a registry-risk spread.

Cogent therefore demonstrates the escape from sponsor concentration, not an escape from the registry. The contribution can place assets and cash flow behind a distinct legal boundary. The registry still decides whether its own authoritative record and services recognise the issuer, a successor, a purchaser or a replacement prefix under the rules that apply at the relevant time.

An IPv4 portfolio has four separations to prove

A financing presentation may show a clean organisational chart: parent, holding company, issuer, trustee and investors. The harder chart is functional. It must separate four questions that are often compressed into the word control.

The first is legal and organisational control. Which entity entered the acquisition agreement? Which entity granted the security interest? Are the addresses and leases scheduled correctly? Were corporate approvals obtained? Does the issuer have the contractual capacity to hold, lease, sell and replace the relevant interests? Could an affiliate or creditor claim that the contribution was ineffective or avoidable? These questions are answered through documents, governing law and, in a dispute, courts.

The second is authoritative registration. Which organisation is shown in the relevant registry account and public data? What agreement applies? Who is authorised to submit a request? Is the source the current recognised holder? Are fees current? Is a transfer lock, dispute or policy restriction present? What event constitutes completion? These questions are answered initially through the RIR's own records, agreements and procedures.

The third is operational authority. Which autonomous system may originate the prefix? What Route Origin Authorizations cover it? Which Internet Routing Registry entities, reverse-DNS delegations and route filters affect use? Which network possesses the credentials and relationships required to change them? The answers are distributed across operators, repositories and service providers. RFC 7020 explicitly places actual route announcement and its manner outside the scope of the Internet Numbers Registry System.

The fourth is commercial performance. Which lessees are entitled to use which addresses? Who collects the revenue? What happens at expiry or default? Are customers concentrated? Does a reputation service, geolocation vendor or receiving network treat parts of the space adversely? The answers lie in contracts, telemetry and third-party systems, many of which are private.

An SPV can improve the first and fourth separations. It can place legal interests, contracts and collections in one vehicle. It can require the servicer to reconcile leases to prefixes. It can grant investors access to records and restrict leakage to affiliates. Yet the second and third remain institutionally distributed. The issuer cannot amend an RIR database by internal resolution, and the RIR cannot make every network originate or accept a route.

This map prevents two opposite errors. One error says the registry record is everything, so the SPV has no meaningful asset beyond permission from the RIR. The other says the registry record is mere administration, so a sale agreement and security filing are enough. The economic position depends on both the private legal chain and the external recognition chain. Routing and cash flow then determine whether that recognised position is useful.

Bankruptcy remoteness protects one boundary. A resilient transaction must prove all four.

The authoritative registration path remains a choke point

RFC 7020 describes a hierarchical Internet Numbers Registry System rooted in the IANA function and served regionally by the RIRs. Its core goals include uniqueness and accurate registration information. That hierarchy avoids competing authoritative allocations of the same address. The very property that protects uniqueness also concentrates administrative dependency.

For a given resource, parties cannot ordinarily shop a pending registration change among several equivalent authoritative providers. They follow the path associated with the source and recipient regions. An inter-RIR transfer may require coordination by two institutions, but that adds a second required actor rather than creating a substitute for either one. A commercial contract can allocate delay costs; it cannot make a private database authoritative to the established system by declaration.

Current ARIN materials illustrate the dependency. A specified or inter-RIR source must satisfy policy and account requirements. A transfer request uses an authorised account contact. The processing fee is non-refundable and does not guarantee approval. Even after approval, ARIN describes a sequence involving a signed Registration Services Agreement, applicable fees and any required inter-RIR coordination before the resources are transferred. If the current registrant no longer exists in an outbound inter-RIR case, ARIN requires the requesting organisation to complete the merger-and-acquisition path first.

RIPE NCC policy uses different language but reaches the same functional point. A legitimate holder may transfer complete or partial blocks that satisfy the rules. The original holder remains responsible until completion. The transfer is completed when the RIPE NCC updates the registration records. Its current procedure expressly addresses mergers, acquisitions, bankruptcy, liquidation, suspension of payments and insolvency proceedings, requiring official evidence and a request from an authorised person or legal successor. That is a service interface to insolvency, not a promise to accept any instruction from any creditor.

APNIC's current conditions likewise make account and policy facts material. An initial recipient may need membership and payment before completion. Associated entities can be deleted in outbound transfers. When completion occurs, the source no longer has rights to the transferred resources under the APNIC process and the resources are registered to the recipient. Historical resources and merger-related transfers have their own conditions.

These procedures are not interchangeable. A portfolio containing resources in several regions may face different agreements, restriction periods, recipient tests, documentary standards, entity cleanup and completion semantics. Legacy status can add another distinction. The SPV's internal statement that it owns one global portfolio does not erase the regional matrix.

Calling this a choke point does not imply bad faith by registry staff. Authoritative uniqueness requires disciplined authentication and dispute handling. A registry should not act on an unauthenticated email merely because investors are impatient. The governance issue is the absence of service substitution if the authoritative provider performs poorly, changes conditions unexpectedly, suffers institutional failure or cannot resolve a contested chain within the financing timetable.

The risk is therefore monopoly service risk in a functional, not rhetorical, sense. The parties depend on one recognised path for a particular administrative act. Without portability, diligence can reduce the probability of failure but cannot remove the concentration.

Bankruptcy creates two clocks

An insolvency involving an IPv4 portfolio starts at least two clocks. The legal clock is controlled by statute, court orders, officeholders, creditor rights and the debtor's case. The registry clock is controlled by authentication, policy, account evidence, agreements and record updates. A transaction succeeds only when the clocks are reconciled.

Consider sponsor distress where the address issuer remains solvent. The financing structure is meant to preserve the issuer's separate existence and keep collections flowing. But registry contacts may still be employees of the distressed sponsor. Shared identity systems may be disabled. A parent administrator may challenge an earlier contribution. The servicer may stop paying fees or responding to abuse reports. The issuer can be legally separate and operationally stranded.

Now consider issuer distress. If the issuer becomes a debtor, investors cannot assume that the bankruptcy-remote label permits immediate self-help. The automatic stay or its local equivalent may constrain enforcement. The trustee may need relief, consent or a court-approved sale. A purchaser may require clean authority evidence. The RIR may ask whether the submitter is the registered holder, an authorised officer, a legal successor, a receiver or another officeholder recognised by the relevant procedure. The court and registry are answering different questions, but both answers may be necessary.

A third scenario is a registry-side interruption while the issuer performs. The account may be locked after a disputed change. A service agreement may be threatened because of fees or inaccurate records. The institution may experience operational or governance failure. A policy change may alter a recipient condition. The cash-flow vehicle has not defaulted, yet its exit option and perhaps its access to RPKI or related services have weakened.

A fourth scenario is contested substitution. The indenture permits the issuer to replace an address block, but the replacement is registered elsewhere, subject to another agreement or tied to a different corporate entity. The credit test may show equal address count and acceptable leverage. The registry test may still fail because the transfer path, source status or recipient evidence is incomplete. Contractual eligibility cannot make administrative completion happen.

These clocks create sequencing risk. A court can approve a disposition before the registry has completed its review. A registry can update a record before lease notices, route authorisations and cash settlement are reconciled. A financing can satisfy a leverage ratio while the operational cutover remains unsafe. The parties should therefore define several timestamps instead of one closing date: legal authority obtained, registry request accepted, agreement executed, authoritative record updated, routing authority reconciled, customer cutover accepted and proceeds released.

The Borders and Nortel transactions from 2011 predate the requested period but remain instructive historical context. Their public materials show why a court-approved sale and ARIN recognition were treated as distinct conditions. The modern SPV does not eliminate that distinction. It makes the evidence and cash around it more organised.

Two clocks do not require one institution to dominate the other. Courts should decide legal rights and insolvency relief. Registries should authenticate and maintain accurate records under published rules. The financing must bridge them with evidence, conditions, reserves and time. Pretending one clock automatically starts the other is the avoidable risk.

Separateness covenants cannot bind a registry

The standard tools of bankruptcy remoteness are still valuable. Their weakness appears only when they are asked to do a job for which they were not designed.

A limited-purpose covenant reduces the issuer's exposure to unrelated business. A debt restriction reduces competing claims. Separate books and accounts make the collateral and collections easier to identify. Arm's-length servicing clarifies what the parent does for the issuer. An independent manager or director can make a voluntary filing harder to initiate casually. Non-petition language can restrict specified transaction parties from commencing an insolvency case for a period. True-sale and non-consolidation analysis can address the movement of assets from sponsor to issuer.

None of these provisions is signed by the registry merely because it appears in an indenture. They do not require the RIR to recognise the collateral trustee as an account contact. They do not waive transfer policy, fees, recipient conditions, documentary review or dispute procedures. They do not preserve a resource certificate if the underlying registry relationship changes. They do not force a public registration record to follow a private sale before the institution completes its own process.

Even a carefully drafted power of attorney has a boundary. It may authorise an agent to act for the issuer under private law. The registry can still require authentication through its account, proof that the power remains effective, evidence of the issuer's status, or an order identifying the officeholder. If the document conflicts with an agreement or policy, the result may depend on governing law and the exact facts. A lender should not discover this boundary for the first time after default.

The same is true of a security interest. Under a secured-transactions regime, attachment and perfection can determine rights between debtor, secured party and competing claimants. They do not necessarily require an external service provider to perform for the secured party. The commercial remedy must be connected to the provider's recognised procedure. That connection may be cooperation by the issuer, a qualified successor, a court-approved sale, a receiver, or another authenticated route. It is not created by labelling the registry an account debtor when its actual role is different.

Contracts can nevertheless price the external dependency. The issuer can warrant present facts: its registered status, account access, agreements, fees, known disputes, disclosed contacts and absence of unauthorised dispositions. It can covenant to maintain those facts, provide notices, preserve evidence and cooperate with a permitted transfer. It can agree to replace a block or deposit cash if a defined registry impairment continues beyond a cure period. A servicer can be replaced if it fails to maintain records or submit requests.

The drafting should avoid a circular promise. If the issuer warrants that every future registry transfer will be approved, the warranty is either false comfort or a disguised guarantee of an event outside its control. If it promises only to use commercially reasonable efforts, investors may have no measurable trigger. The better form specifies deliverables and event states: current authority certificate, accepted request, requested supplemental evidence, executed agreement, fees paid, dispute notice, completed record update, appeal lodged, replacement delivered.

Bankruptcy remoteness is strongest when its covenants preserve the issuer's ability to respond to external events. It is weakest when the label is offered as proof that those events cannot occur.

A registry-risk ledger makes concentration visible

The financing should maintain a registry-risk ledger beside the collateral schedule. The schedule says what the issuer claims to hold. The ledger says which external events preserve or interrupt realisation.

Dependency Evidence before funding Adverse event First protection What remains outside the SPV
Recognised holder Current registry record, agreement, entity documents and acquisition chain Holder mismatch or competing claimant Correct record, suspend new dispositions, preserve dispute evidence Registry authentication and final record decision
Account continuity Independent authorised contacts, current fees and tested recovery Sponsor employee departure, credential lock or unpaid fee Alternate contact, servicer replacement, controlled fee reserve Registry account-recovery process
Transfer eligibility Current policy analysis, source status and recipient readiness Restriction, ineligible recipient or inter-RIR incompatibility Change recipient, wait, substitute or prepay Current policies of each required RIR
Insolvency recognition Legal-successor map, court-order form and local counsel analysis Parent, issuer or holder enters proceedings Obtain order or officeholder evidence; seek stay relief where needed Court timetable and registry review
Routing authority Expected origins, ROAs, route objects and credential map Invalid route, stale authorisation or conflicting announcement Reissue authority, quarantine affected space, use replacement Network acceptance and relying-party policy
Revenue continuity Prefix-to-lease map, collection account and customer notices Servicer failure or customer termination Backup servicer, cash trap, customer migration Customer behaviour and service demand
Disposition liquidity Buyer list, transfer-path analysis and lot design Failed sale, delay or discounted bid Hold, split where lawful, substitute or amortise Market depth and buyer funding
Provider continuity Exported evidence, signed receipts and migration test Registry outage, institutional failure or prolonged unavailability Preserve state, invoke continuity process, migrate if recognised path exists Availability of an accepted alternative provider

This ledger prevents double counting. A sponsor bankruptcy is not automatically a registry failure. A registry hold is not automatically a loss of routing. An invalid route is not proof that the issuer lacks legal authority. A lease default is not proof that the address has no resale value. Each event affects a different cash-flow probability, cure cost and time horizon.

It also makes concentration measurable without inventing a global failure rate. A portfolio can disclose the proportion of its own addresses dependent on each RIR, the proportion with independent account contacts, the proportion with verified acquisition chains, the number of unresolved tickets, and the time since each continuity test. Those are portfolio denominators known to the issuer. They should not be presented as statistics for the entire IPv4 market.

Stress tests can then be explicit. What happens if one registry accepts no transfer request for thirty days? What if the sponsor's identity provider is unavailable? What if an inter-RIR recipient loses eligibility after signing? What if a resource certificate is reissued and the previous ROA disappears? What if the buyer will not fund until registration changes but the registry will not complete until a recipient agreement and fee are delivered? The model should show cash reserve, debt-service coverage and substitution capacity under each sequence.

A single status such as registry compliant is too coarse. It can be true on the reporting date while the authorised contact is a departing employee, a legal-name mismatch is unresolved, and the proposed recipient path has never been tested. The ledger should expose those conditions before they become an insolvency event.

For investors, this is more useful than a legal conclusion without operational evidence. For registries, it reduces emergency pressure. A well-maintained issuer arrives with authenticated records, a clear successor and an exact request instead of asking staff to reconstruct years of corporate history during a default.

Portability is a service design, not a slogan

Portability is often used loosely to mean that IPv4 addresses can be sold. That is only transaction portability. The harder requirement is service portability: the ability to carry an authenticated registration state, its evidence and its continuing administrative services to another qualified provider without loss of uniqueness or an opportunistic rewrite of history.

In the current system, a completed inter-RIR transfer can move a resource from one regional registry to another under compatible policies. That is useful but it is not a general failover mechanism. It depends on source and recipient eligibility, bilateral coordination and an intended transfer to a qualifying recipient. It does not necessarily allow the same holder to select a replacement registrar simply because service quality deteriorates or an institution becomes unavailable.

A credible portability design begins with a canonical state package. It identifies the prefix, recognised organisation, legal-entity identifiers where appropriate, relevant agreement, acquisition or succession basis, active restrictions, dispute state, effective dates, authorised contacts and the latest completed administrative event. Sensitive supporting documents can remain access-controlled, while hashes, signatures and provenance show that they have not been substituted after distress.

The second element is event semantics. Submitted, authenticated, eligible, approved, agreement executed, fee settled, record updated, suspended, disputed and reversed must mean different things. A timestamped receipt should identify the issuing service and the exact resource set. The receiving service should not have to interpret an informal email subject line to decide whether a transfer was complete.

The third element is continuity. Authorised contacts must not depend exclusively on the sponsor. Evidence exports should be tested and readable without the incumbent's private interface. A qualified backup servicer should know how to maintain leases, fees, abuse contacts, RPKI transitions and customer notices. Credentials themselves need not be broadly copied; recovery authority and handoff procedures need to be independently verifiable.

The fourth element is institutional acceptance. Two private databases claiming the same /16 would destroy the uniqueness that registration exists to protect. A receiving provider must be recognised under a governance framework that prevents duplicate authority, imports the prior event history, respects unresolved disputes and publishes an auditable cutover. Portability cannot be achieved by encouraging creditors to route around an adverse decision with a friendlier record keeper.

The fifth element is exit discipline. Migration must not erase obligations, fees, sanctions restrictions, a court order or a documented competing claim. The incumbent needs a bounded opportunity to identify an unresolved condition. The recipient needs a duty to preserve it. A neutral escalation process should distinguish a genuine conflict from an institution's refusal to release a healthy account.

Finally, portability needs periodic testing. A paper right that has never exported a complete state package is not credit protection. The issuer should run a dry handoff, verify signatures, reconcile resource coverage, test contact authority and document the time required. The test can stop before any authoritative change; its purpose is to expose missing dependencies.

This design does not make the registry irrelevant. It makes the registration service replaceable under controlled conditions while preserving the registry system's uniqueness and accuracy goals. That is the same structural logic the SPV applies to a servicer: preserve the asset and its history, but do not make one operating institution impossible to replace.

The insolvency playbook must reach the network

An IPv4 SPV can survive a legal separation and still lose value through a poor technical handoff. The insolvency playbook must therefore continue beyond the registry record.

At the first sign of sponsor distress, the trustee or backup servicer should verify account contacts, current fees, registration records and the prefix schedule. It should preserve copies of agreements, prior transfer receipts and corporate authority documents. This is evidence preservation, not an attempt to seize operational credentials prematurely.

The next check is the lease and route map. Every customer contract should resolve to exact prefixes. Expected origin ASNs, active announcements, ROAs, route objects and reverse-DNS delegations should be recorded with timestamps. The map must distinguish issuer authority from customer operation. A lessee may originate the space legitimately without being the registered holder; a registered issuer may hold the resource while another network performs all routing work.

If the servicer fails, the backup must know which actions preserve value and which create a new incident. Deleting a ROA before the replacement is ready can make valid customer routes appear invalid to networks applying route-origin validation. Leaving an old broad ROA indefinitely can authorise an origin that no longer serves the portfolio. ARIN's current transfer best-practices material advises source and recipient organisations to review or recreate ROAs, Internet Routing Registry entities and reverse DNS around completion. APNIC notes that associated entities are deleted in specified outbound transfers.

Those are not clerical footnotes; they are cutover dependencies.

Customer communication also matters. A lease may continue through sponsor restructuring, terminate on a change of control, or require consent for assignment. The issuer should not announce that addresses are unavailable merely because the parent filed for protection. Nor should it promise uninterrupted use before confirming that routing, DNS and payment instructions remain valid.

If a sale becomes necessary, the data room should show more than a registry screenshot. The buyer needs the legal chain, registry path, lease encumbrances, historical origins, current RPKI state, known reputation issues, geolocation dependencies and the exact sequence for release of funds. A bankruptcy sale order can authorise a disposition; the buyer still needs an operationally usable resource.

The playbook should end with reconciliation. The authoritative registration record, issuer schedule, trustee collateral report, RPKI objects, route announcements, reverse DNS, customer contracts and cash accounts must describe the same post-event position. Exceptions should be dated and owned. A completed registration update with stale customer routes is not continuity. A working route with unresolved successor authority is not a completed disposition.

This operational discipline gives bankruptcy remoteness economic meaning. It prevents a legally preserved issuer from becoming a shell around records no customer can safely use.

NRS can make the dependency portable without becoming the judge

Number Resource Society has a positive role precisely because the weakness is not only legal doctrine. It is the lack of a common, portable service record across credit, registry and network institutions.

NRS can publish an open registration-continuity profile. The profile would define the minimum state package for a financed resource: prefix coverage, recognised organisation, evidence class, agreement class, contacts, transfer restrictions, dispute state, effective dates, expected routing-authority handoff and provenance. It would specify which fields are public, which are shared only with authorised transaction parties, and which remain with counsel or a trustee.

It can define signed event receipts and validation rules. A recipient system could verify that the resource set in a court-approved sale matches the set in the registration history; that no /24 is omitted or duplicated; that the transfer event follows the latest recognised holder event; and that an unresolved restriction remains visible. Common software tests would reduce bespoke interpretation without deciding the underlying legal dispute.

NRS can convene portability exercises. RIRs, alternate registration-service operators, trustees, insolvency practitioners, lenders and network operators could test export, verification and controlled import against synthetic or consented data. The exercise should measure completeness, conflicting-state detection, recovery time and route-authority handoff. Results should identify the exact participating systems and cases rather than imply global coverage.

It can also define a continuity covenant that financing parties may adopt voluntarily. The covenant would require periodic evidence export, independent contacts, tested servicing, notice of material registry events and cooperation with an accredited migration process. Competition among lenders and issuers would determine whether the covenant is valuable and how it affects price.

The limits are essential. NRS should not certify that an SPV owns a resource, that a contribution is a true sale, that a lien is perfected or that a court must grant stay relief. It should not direct an RIR to disregard a dispute. It should not promise investors that a backup provider is authoritative before the relevant institutions recognise that provider. It should not publish private lease, identity or insolvency materials merely to display transparency.

NRS's public descriptions of a holder-focused mission and concern with portability support this direction as first-party institutional evidence. They do not demonstrate that the proposed profile, exercises or migration framework are deployed. Credibility would come from an open specification, independent implementations, adversarial testing, clear governance and public reporting of failures as well as successes.

Properly bounded, NRS does not replace registries or courts. It makes the handoff between them less fragile. Its contribution is to ensure that a solvent resource vehicle is not trapped because the facts needed for continuity cannot leave one service provider in a verifiable form.

What can be measured without inventing certainty

No public dataset gives the global number of IPv4 SPVs, the address volume they hold, the frequency of sponsor bankruptcy, the rate of substantive consolidation, the number of registry-related covenant breaches or the recovery after a failed transfer. The Cogent notes are a prominent disclosed example, not a market census.

No public source isolates the amount of the Cogent coupon attributable to registry concentration. The notes combine address value, lease revenue, receivables, leverage, reserves, maturity, market rates, documentation and issuer-specific risk. Comparing the 2024 and 2025 series does not solve the attribution problem.

RIR transfer logs describe completed administrative events. They generally do not expose the financing structure, failed requests, private negotiation, disputed evidence, court cost, service interruption or realised loss. A completed row cannot show how close a transaction came to failure. An absent row cannot prove that no commercial arrangement occurred.

The measurable starting point is therefore portfolio-specific. An issuer can report the number and address count of scheduled prefixes by RIR; the share with current agreements and independent contacts; the share with complete acquisition chains; unresolved account or transfer events; the age of the last evidence export; the time needed in a controlled continuity test; the amount of cash reserve; substitution capacity; customer concentration; and route-authority exceptions.

Even those metrics require definitions. One transfer may contain many prefixes. One /16 may be leased in smaller blocks. A test that validates a document archive is different from a test that obtains recipient pre-approval. A registry response time should separate time waiting on the applicant from time under institutional review. Address count, prefix count, case count and revenue exposure must not be used interchangeably.

The absence of global denominators does not justify silence. It requires labelled evidence. Cogent supports feasibility. RIR documents support the existence of external conditions. The Bankruptcy Code supports the legal effects of an actual filing in its jurisdiction. RFCs support the distinction between registration and routing. NRS materials support a stated institutional direction. None supports a universal failure probability.

This discipline is particularly important when promoting portability. A prototype export, one bilateral test or one cooperative migration should not be advertised as elimination of registry risk. The meaningful evidence would be repeated, independently observed handoffs under defined adverse conditions, with conflicts preserved and no duplicate authoritative claims.

Remote from the sponsor is only half the design

The SPV answers an important credit question: can investors analyse and protect a pool of IPv4 resources, leases, receivables and reserves without taking the whole sponsor's operating risk? Cogent's disclosed financings show that the answer can be yes.

The structure does not answer a second question: can the pool maintain and realise its registration position if the one required service path becomes unavailable, contested or slow? Under current arrangements, the answer is conditional. The issuer must satisfy the relevant registry's procedures, and a private covenant cannot appoint another authoritative provider.

That dependency should not be hidden behind property language or institutional deference. It should be documented. The financing needs separate evidence for legal contribution, authoritative registration, operational authority and commercial cash flow. It needs two-clock closing mechanics for insolvency and registry events. It needs contacts independent of the sponsor, objective event receipts, reserves, substitution, backup servicing and a network-level cutover plan.

Most importantly, it needs a credible route to service portability. Portability must carry authenticated history and unresolved disputes, preserve uniqueness, protect sensitive evidence and prevent duplicate authority. It cannot mean choosing whichever registrar gives the creditor the preferred answer.

NRS can help build that route through an open continuity profile, signed event semantics, conformance tests and multi-institution exercises. Its authority should end where courts, registries, operators and credit committees begin. Evidence portability is a public-good function; title adjudication and note guarantees are not.

Bankruptcy remoteness reduces correlated failure inside a corporate group. Registry portability reduces concentrated failure outside it. The first without the second is still useful, but investors should know what remains exposed.

An IPv4 issuer can be legally separate, financially ring-fenced and operationally disciplined. Until its registration service and evidence can move through a recognised, tested process, it is still dependent on one external gate for a decisive part of value.

That is not a reason to reject the SPV. It is the reason to finish its design.

Sources