The useful way to think about legal risk at LACNIC is not to imagine the registry suddenly going dark. That is the dramatic failure, and probably the less likely one. The more important risk is quieter. The registry service is still online. RDAP still answers. Reverse DNS still resolves. Route origin attestations are still being served. Members can still log in, open tickets and pay invoices. Yet a legal dispute has begun to change the price of relying on the record. A contested corporate sale leaves uncertainty over who can sign a transfer request. A court order freezes one resource block but is worded broadly enough to make staff cautious about related services. A bank asks for additional information before processing a cross-border payment. A board or executive authority dispute leaves counterparties wondering who can instruct counsel, renew a vendor contract or approve emergency expenditure. A creditor, liquidator, regulator or government office asks the registry to do something that is lawful in one sense but operationally dangerous in another.
In that setting the registry has not failed in the simple technical sense. Its servers may be healthy. Its staff may be competent. Its legal department may be active. The risk is that the market begins to treat the registry record as conditional on institutional calm. Counterparties stop asking only what the ledger says today. They ask whether the institution behind the ledger can keep recognising holders, authenticating changes, maintaining reverse DNS, preserving RPKI, processing transfers, collecting fees, paying staff, renewing contracts, holding bank accounts, keeping credentials under control and communicating with members while legal stress unfolds. The ledger remains valuable because it is expected to continue. Once that expectation weakens, a premium appears before any court has issued a final judgment.
That is the economics of court and continuity risk. A court is not merely a venue in which one party wins and another loses. It can also become a channel through which uncertainty about legal authority is converted into uncertainty about registry operations. A provisional order can preserve a disputed right or delay a transaction. A dispute about who controls a company can slow a routine account update. A payment freeze can make a renewal feel strategic. A bank-account problem can make payroll, insurance, vendor support or legal defence harder. A court-appointed administrator can keep a network alive, but only if the registry knows how to recognise that authority. A governance quarrel can make ordinary actions appear political. A narrow legal dispute can become a broad operational risk if the institution has no firewall between the claim and the service.
LACNIC is a useful case because it is neither a state nor an ordinary vendor. It is a non-governmental regional internet registry established in Uruguay in 2002, serving Latin America and parts of the Caribbean. It manages IPv4 addresses, IPv6 prefixes, autonomous system numbers and reverse-DNS delegations for a region of large continental economies, small island networks, public-sector bodies, universities, carriers, hosting firms, cloud providers, local access networks, cross-border corporate groups and family-owned internet service providers. Public descriptions place its service community at more than 13,000 network operators across 33 territories. Those details do not prove that LACNIC is in trouble. They define the terrain on which legal continuity matters.
Every regional internet registry needs a legal home. Without a legal person there is no ordinary way to hire staff, hold reserves, sign service contracts, rent offices, buy insurance, open bank accounts, defend claims, enter membership agreements or answer lawful orders. The legal shell is not decorative. It is the vessel through which the registry utility is operated. Yet the regional dependence on LACNIC is broader than the jurisdiction that gives it legal personality. A member in Brazil, Mexico, Argentina, Colombia, Chile, Jamaica, Trinidad and Tobago, Barbados, Belize, Haiti or a smaller island economy may rely on a record maintained by an Uruguayan legal body. A dispute may involve corporate documents in one country, payment in a second, customers in a third, registry policy in a fourth, and service consequences across many more.
The danger is not ordinary legal accountability. Courts are necessary. Members must be able to challenge decisions. Resource holders must be able to protect rights. Employees and vendors must be able to enforce contracts. Creditors must be able to assert claims. Governments and public authorities must be able to pursue lawful requests. A registry above law would be more dangerous than a registry exposed to law. The danger is pathological continuity risk: a design in which a legal dispute over one claim, account, resource, payment, office or contract can contaminate unrelated registry services because the institution has not separated the ledger from the quarrel. Courts do not threaten the internet merely by existing. The threat appears when the registry lacks a service-continuity firewall strong enough to preserve lawful accountability without turning live infrastructure into collateral.
For LACNIC, the continuity question should therefore be framed as an economic question as much as a constitutional one. What discount does a buyer demand for a block that might be caught in a legal hold? What delay does a bank price when registry recognition depends on documents from two jurisdictions and an order from a third? What premium does an insurer charge when critical authority is informal rather than written? What cost does a small Caribbean provider bear when payment friction can spill into account standing, transfer eligibility, reverse DNS or RPKI? What does a broker require in escrow when a court-order handling process is hard to predict? These are not abstract anxieties. They are the private prices of institutional ambiguity.
The central claim is narrow. LACNIC's legal exposure should be managed as a continuity premium on the registry ledger. The lower the premium, the cheaper it is for the region's networks to rely on records, transfers and security services. The higher the premium, the more every transaction must pay for uncertainty about the institution that records it.
The legal shell beneath a regional utility
The language of internet governance can make registries sound as if they float above ordinary institutional constraints. They do not. LACNIC's authority is regional, technical and contractual, but its body is legally grounded. It needs governing documents, a board, management, member relationships, bank accounts, employment arrangements, office leases, service contracts, insurance, outside counsel, audit routines and recognised authority to act. The fact that its ledger serves many countries does not make the legal body disappear. It makes the legal body more important, because a narrow institutional failure can impose costs across borders.
The registry function is not self-executing. A public registration response may look like data, but behind it are staff decisions, authenticated access, internal controls, security procedures, service-level arrangements, budget approvals, legal advice, vendor contracts and member verification. Reverse DNS depends on delegation, zone operation and continuity of authority. RPKI depends on certification systems, repositories, manifests, revocation information, signing practice and trust relationships. Transfers depend on policy, documentation, recognised signatures, need assessment where applicable, and coordination between registries. Billing depends on currency, banking, invoicing, sanctions screening, public procurement and dispute handling. The ledger is technical at the surface and institutional underneath.
That institutional underside is where legal stress enters. A dispute does not need to touch a router to affect the registry economy. It can touch authority to sign. It can touch a bank account that pays staff or vendors. It can touch the validity of a board decision. It can touch a service agreement. It can touch the standing of a member's representative. It can touch whether a successor company has inherited resources. It can touch whether an order from a local court should be implemented, narrowed, challenged or translated into an action by an Uruguayan association serving a regional utility function. The network may remain up while the economic quality of the record declines.
The legal home gives LACNIC stability in one sense. Uruguay supplies a formal setting for incorporation, contracts, employment, banking and courts. That is valuable. A registry with no clear legal home would be harder to trust, not easier. But legal home is not the same as legal legibility. Members should be able to understand who can bind the institution, who can approve emergency action, who controls bank authority, what happens when an office is disputed, how court orders are classified, how records are preserved, how payment interruption is contained, and which services continue during a legal hold. The point is not that every member should become an expert in Uruguayan law. The point is that regional dependence should not require private guesses about institutional continuity.
LACNIC's role is also narrower than some rhetoric suggests. It is not the region's telecom regulator. It is not a court. It is not a development bank. It is not a political union. It is a registry utility with surrounding policy, education, security and community functions. Its highest institutional value is reliability: uniqueness of number resources, accurate records, authenticated changes, public contactability, reverse resolution, resource certification, transfer recognition, auditability and continuity through stress. The more those functions depend on the good order of the legal shell, the more the legal shell must be made boring.
A boring legal shell is not one without disputes. It is one whose disputes do not threaten unrelated services. A member can sue without turning every transfer into a hostage. A resource holder can contest a sale without disabling the last verified operational state. A board seat can be contested without making staff unsure whether to pay ordinary invoices. A creditor can assert a claim without freezing the whole region's registry record. A court can restrain a specific resource without unintentionally disrupting RPKI or reverse DNS for unrelated holders. That is the standard a non-state regional utility should pursue.
How legal stress enters the ledger
Legal stress has many doors. It is a mistake to look only for headline litigation against the registry itself. In the registry economy, smaller events can matter because they intersect with recognition. The registry is a recordkeeper, but it is also a gate through which corporate authority, payment status, security attestations and transfer finality must pass.
Member disputes are the first door. A company may split. Shareholders may fight over control. A former executive may retain access to registry contacts. A parent may sell a subsidiary but leave number resources out of the asset schedule. A local provider may reorganise after a death in a family-owned firm. A public body may move network functions from one ministry to another. A cooperative may elect a new board whose authority is challenged. The registry must decide who can update contacts, create route-origin attestations, change reverse DNS or request a transfer. If the answer is unclear, the resource becomes less liquid even if the network keeps operating.
Board and executive authority disputes are the second door. A registry can have functioning servers and still face uncertainty over who may instruct counsel, approve budgets, hire senior staff, accept a settlement, renew a critical contract or issue member communications. The economic problem is not that every governance dispute will break operations. It is that counterparties may not know which layer has authority in a shock. If authority is informal, personality-based or buried in custom, the premium rises.
Interim orders are the third door. Courts use provisional relief to preserve a position before final rights are decided. Such orders can be sensible. They can prevent a contested transfer, protect a creditor, preserve evidence or stop an unauthorised corporate act. But in a registry setting the thing to be preserved must be precise. Freezing a transfer is not the same as disabling reverse DNS. Preserving a record is not the same as suspending publication services. Blocking a disputed authority change is not the same as cutting off the last verified operational state. Interim relief can protect the ledger or weaponise it, depending on implementation.
Debt and payment claims are the fourth door. A member may owe fees. The registry may owe a vendor. A claimant may attach funds. A bank may delay settlement because of compliance checks. A foreign-currency payment may be slow. A correspondent bank may ask why money is being paid for intangible network resources. A small operator may be late not because it refuses to pay but because currency controls, procurement rules, hurricane recovery, intermediary fees or banking documentation make payment difficult. If payment states are treated crudely, routine finance becomes continuity risk.
Employment and contract disputes are the fifth door. Staff knowledge, system access and vendor agreements matter. A dispute involving key personnel, outsourced operations, data-centre services, security support, software providers or legal counsel can affect resilience even without touching a member record. A registry that depends on a few undocumented practices or individuals is more exposed than one whose controls, access rights and continuity duties are written, tested and auditable.
Resource-holder litigation is the sixth door. A buyer and seller may fight after a transfer. A lessor and lessee may fight over delegated use. A creditor may claim that an IPv4 block belongs in an estate. A customer may allege that the holder no longer controls the resources it is selling or leasing. A court may order parties not to alter the status quo. The registry is then asked to translate legal uncertainty into registry action. If it has only two tools, normal service or full freeze, the costs will be excessive.
Insolvency, succession and restructuring are the seventh door. A distressed company may still operate a network and serve customers. Its resources may support going-concern value. An administrator, receiver or liquidator may have lawful authority to preserve operations or sell assets. A registry that treats formal distress as abandonment may destroy value. A registry that accepts any claimant without verification invites fraud. The right answer is continuity under verified authority, with stronger scrutiny for control changes.
Government pressure is the eighth door. Courts, telecommunications regulators, law-enforcement bodies, finance authorities or political offices may ask for action affecting an operator. Some requests may be lawful and precise. Others may be informal, overbroad or outside a number registry's role. In a region with uneven state capacity, the registry must obey applicable law without becoming a private extension of every official pressure point. Compliance must be narrow enough to preserve the service and explicit enough to be explained later.
Each door produces the same economic question: can LACNIC contain the legal issue to the resource, account, service or authority actually affected, while preserving the ledger and unrelated services?
The price appears before judgment
In ordinary legal analysis, risk often means the probability of losing a case. In registry economics that is too late. The price appears before final judgment. A buyer does not wait for every appeal to close before adjusting an offer. A bank does not ignore a notice because it is provisional. A broker does not treat a disputed authority letter as neutral. A small operator does not assume that a three-month delay is harmless. Markets price uncertainty as soon as it changes expected finality.
IPv4 scarcity makes this visible. LACNIC's IPv4 waitlist was created on 19 August 2020, when the last available IPv4 block was assigned. Public waitlist material indicates that a late request may face a wait measured in many years and can receive at most 1,024 IPv4 addresses from recovered space, subject to conditions such as IPv6 resource status and quarantine of recovered blocks. However necessary IPv6 deployment is, that queue is not an ordinary supply channel for a network needing capacity now. The marginal IPv4 address comes from transfer, lease, acquisition, restructuring, old inventory or engineering around scarcity. Registry recognition has become part of capital movement.
LACNIC's transfer rules show how legal risk becomes price. IPv4 transfers may occur inside the region and across registry boundaries. The minimum transferable block is a /24. A recipient inside the region must justify IPv4 resources under the applicable policies. The registry or corresponding registry verifies the holder and checks whether resources are involved in a dispute. In intra-regional cases the parties submit a signed legal document supporting the transfer. In inter-regional cases documentation must satisfy coordination between registries. Once the transfer is complete, LACNIC modifies the resource information. Transfer-log, holding-period and eligibility rules then shape future mobility.
Every step has a legal-continuity shadow. Holder verification can reveal a board dispute. A dispute check can freeze a sale. A signed document can be challenged by a shareholder, public administrator or creditor. A recipient review can become uncertain if the buyer's corporate authority is under litigation. Inter-regional coordination can be delayed by inconsistent legal standards. A service agreement can raise a payment or contract issue. RPKI and reverse DNS can lag if operational continuity is not planned as part of transfer execution. The block is the same sequence of addresses. Its economic value changes with the cost of making recognition final.
The premium appears in transaction terms. Escrow may require longer hold periods. Buyers may demand broader indemnities. Sellers may accept lower prices. Brokers may charge for navigating uncertainty. Counsel may ask for corporate opinions from more jurisdictions. Banks may ask for additional documentary support. Lenders may decline to value address holdings as part of working capacity. Lessees may demand warranties about route-origin attestations, reverse-DNS continuity and account standing. Customers may ask whether a provider can maintain address use through restructuring.
Large organisations can absorb some of this friction. They have counsel, treasury departments, previous transfer experience, multiple address pools and time. Small operators cannot. For a small Caribbean network, a /24 or /23 may be a serious balance-sheet item. A delay may affect equipment finance, disaster resilience, a hotel group, payment services, public customers or a local hosting business. A single engineer may be managing outages, billing, peering and registry documentation. A legal hold that is manageable for a multinational buyer can be existential for a small seller.
This is why continuity risk is not an exotic legal topic. It is a small-operator cost problem. The registry cannot make every member equally sophisticated or equally well served by banks, lawyers and public administration. It can make legal-continuity states visible enough that small members are not forced to buy private knowledge at monopoly prices.
Accountability without operational hostage-taking
There is a temptation in registry politics to treat courts as enemies of continuity. That is the wrong lesson. Courts, arbitration and independent review are part of continuity because they prevent the registry from acting as recordkeeper, claimant, judge and executioner in serious disputes. Legal accountability is not pathology. It is a guardrail against concentrated private power over scarce resources.
The pathological case is different. It occurs when ordinary accountability lacks an operational firewall. A member sues over one block and the registry freezes unrelated services. A court order preserves a disputed transfer but staff disable routine reverse-DNS maintenance. A payment claim leads to a broad account hold that contaminates RPKI or contact accuracy. A board dispute pauses routine service because emergency authority is not defined. A lawsuit against a resource holder leaves customers unable to understand whether the last verified operational state will continue. Litigation then becomes a lever over the live network rather than a means for resolving legal claims.
The difference between legitimate accountability and pathological continuity risk is the difference between narrow remedies and broad contamination. A narrow remedy says that a particular transfer will not proceed until authority is clarified. A broad contamination says that the entire account is unreliable, all services are suspect and ordinary security maintenance is dangerous. A narrow remedy says that a court has required preservation of records. A broad contamination says that staff cannot safely answer member requests. A narrow remedy says that a bank payment needs additional evidence. A broad contamination says that account standing, transfer eligibility and publication services are all at risk.
This distinction should be written into registry practice rather than improvised. Legal demands should be classified by scope, authority, affected resource, urgency, confidentiality, service effect and review date. The registry should ask what the least disruptive lawful action is. It should preserve evidence. It should maintain the last verified operational state unless a specific duty requires change. It should separate record preservation from service interruption, transfer restraint from security maintenance, billing enforcement from routing-security continuity, and authority review from public-data disappearance.
That approach does not make LACNIC weak. It makes it harder to abuse. A registry that applies every legal concern broadly invites pressure: a litigant learns that a small claim can produce a large freeze, and a government office learns that informal pressure can generate operational effects. A registry that applies legal concerns narrowly reduces the prize. Courts still get compliance. Claimants still get preservation. But the blast radius is controlled.
The same logic applies to communication. Silence during legal stress creates rumour. Overbroad statements create fear. A mature registry should communicate what can be said: which service is affected, which service is not affected, whether transfers continue, whether RPKI and reverse DNS continue, what members must do, what cannot be disclosed, and when the next update will come. Members need operational facts more than institutional reassurance. The sentence "this dispute is contained" is valuable only if members know what containment means.
A regional market does not pay one price for ambiguity
LACNIC's region gives the issue its texture. Latin America and the Caribbean are not a single legal or financial environment. The region includes large economies whose domestic scale gives them gravity; small island states and territories where banking, procurement and natural-disaster exposure can make routine administration difficult; public-sector networks whose authority may depend on government transitions; family-owned providers whose documents may not be as tidy as those of listed companies; and cross-border corporate groups whose operating assets and legal entities may not align neatly with registry accounts. The same registry rule can be experienced very differently across that range.
Large-country gravity matters. A dispute involving a major operator, a large address holder, a state-owned entity, a bank with regional reach or a large corporate group can affect expectations beyond the immediate account. Smaller members may watch how the registry treats the powerful and infer how they would be treated under stress. If legal-order handling appears discretionary, scale becomes a source of fear. If the rules are narrow and auditable, scale becomes less threatening.
Small islands matter for the opposite reason. A block of addresses that looks modest in a continental market may be a critical working asset for an island provider, public network, disaster-recovery service, hotel group, payment intermediary or local hosting firm. A payment delay may reflect correspondent-bank friction rather than unwillingness to pay. A corporate document may take longer to obtain. A storm, banking outage or government backlog may affect compliance. The registry should not lower integrity standards, but it should distinguish risk from inconvenience. Otherwise small jurisdictions pay more for the same ambiguity.
Uneven state capacity matters because not every court, regulator or public office will understand number-resource operations. Some authorities will issue precise orders. Others may use language better suited to tangible property, domain names, telecom licences or corporate shares. Some agencies will have experienced technical counsel. Others will not. The registry cannot educate every court from the beginning in every case, but it can maintain standard explanations of what registry actions do: what a transfer freeze means, what reverse DNS does, what RPKI changes may affect, what RDAP publication means, what contact maintenance preserves, and how a narrow order can protect legal rights without harming unrelated services.
Currency and payment friction matter because account standing is an operational threshold. A member's payment may cross banks, currencies, public approvals and compliance checks before reaching the registry. A fee dispute can become a continuity risk if the registry treats late payment as a single category rather than differentiating between refusal, administrative delay, bank failure, procurement hold, sanctions screening, invoice disagreement, disaster disruption and documented hardship. A strict fee policy can still be proportionate. The point is to prevent billing from accidentally becoming a switch for security, reverse resolution or record accuracy.
Multilingual governance matters too. LACNIC operates in a region where Spanish, Portuguese and English are practical governance languages, with French, Dutch, Creole and Indigenous-language contexts present in public life and local administration. Legal documents, corporate records and member communications do not arrive in one linguistic form. Translation delay, misunderstanding or uneven access to legal vocabulary can affect dispute handling. A continuity firewall should therefore include language discipline: clear notices, plain operational explanations, consistent terms for legal states, and enough linguistic capacity that a member's market is not penalised for being outside the dominant administrative language of a particular case.
These conditions do not make LACNIC uniquely fragile. They make hidden friction unequal. A legal rule that looks neutral from the centre can become expensive at the edge. The registry cannot repair every banking constraint, court backlog, procurement difficulty or corporate-document gap in the region. It can avoid adding avoidable uncertainty where those conditions meet the ledger.
The continuity firewall
The central institutional tool should be a service-continuity firewall. The phrase is less grand than it sounds. It means that legal, payment, governance and authority problems should not move as one undifferentiated block through the registry. The registry should define which services continue, pause or change during different legal states: disputed transfer, contested authority, late payment, court order, member insolvency, account compromise, suspected fraud, sanctions issue, government request, merger, closure, inter-regional transfer and board or executive disruption. The default should be preservation of the last verified operational state, with interruption requiring a specific legal, security or record-integrity reason.
The firewall begins with the ledger. The registry record must remain accurate, visible where policy requires visibility, and protected from unauthorised alteration. But preserving the ledger does not always mean freezing every action. A contact update may be allowed while a transfer is restrained. An abuse mailbox may need correction while ownership is disputed. Reverse DNS may need to continue while corporate control is litigated. RPKI may need to preserve the last legitimate routing-security state while a court decides who may sell a block. Transfers may need a hold while ordinary publication and account access continue. Billing may need enforcement without disabling unrelated safety functions.
RPKI deserves particular care. Route origin attestations are security signals with operational consequences. A change, revocation or failure to maintain them can affect reachability and filtering decisions beyond the parties to a dispute. Legal stress should therefore distinguish between creating new assertions, maintaining existing ones, revoking compromised ones and freezing a contested authority change. If a resource holder is under litigation but the last verified network is still operating, abruptly weakening routing-security state may harm customers and counterparties without helping a court decide the underlying issue. Conversely, if credentials are compromised or authority is fraudulent, preserving the wrong state can also be harmful. The answer is not automatic preservation; it is rule-bound preservation under verified authority.
Reverse DNS is similar. It is often treated as a supporting service rather than a scarce asset, but it can matter for mail reputation, network management, customer operations, compliance and service identity. A transfer hold does not necessarily require disabling reverse-DNS maintenance. A payment dispute does not necessarily justify stale reverse delegation. An insolvency proceeding may need reverse DNS to continue while a business is sold or reorganised. The firewall should specify when reverse DNS is maintained, when it is locked, who may request updates and how changes are logged during legal stress.
Transfers need the clearest segmentation. A disputed transfer should be paused, not transformed into general suspicion of the holder's unrelated resources. A court order should identify the affected block, account or transaction where possible. If the order is broad, LACNIC should seek clarification or implement the narrowest action consistent with legal duty. The registry should separate the transfer queue from security maintenance, publication services, billing state and contact accuracy. It should record the reason for the hold, the next review date, the evidence needed, and the services unaffected.
Billing requires its own firewall. Fees are necessary. A member-funded registry cannot allow indefinite non-payment. But debt collection should not casually become operational hostage-taking. Notice, cure periods, payment-state categories, partial restrictions and escalation paths should be known in advance. The registry should identify which consequences affect voting, new requests, transfers, public data, RPKI, reverse DNS, account recovery and support. A member that refuses to pay is different from a public body delayed by procurement, a bank transfer blocked by compliance checks, or an island operator recovering from a storm. A proportionate billing regime can be firm without being blind.
Staff, bank accounts and credentials are part of the same firewall. A registry cannot preserve continuity if emergency access depends on a single person, if bank authority becomes unclear when an executive is disputed, if payroll depends on one signatory, if vendor renewals require contested approval, or if credentials are held by individuals without conditional recovery. Continuity is not only about the member-facing database. It is about the legal and administrative machinery that keeps the database trustworthy.
Court-order handling as operational discipline
A court-order handling protocol is where legal accountability meets utility discipline. It should not be a defensive document written to avoid courts. It should be a practical guide that helps courts, members and staff translate legal rights into narrow registry action.
The first requirement is classification. What is the issuing authority? Is the order binding on LACNIC, on a member, or on another party? Is it final, interim, urgent or subject to appeal? What resources, accounts, services or documents are affected? Does it require disclosure, preservation, restraint, transfer, restoration, payment, recognition of authority or some other act? Does it contain confidentiality obligations? Does it conflict with another order, registry policy or member agreement? What is the deadline? Who inside the registry approves implementation? When must the action be reviewed?
The second requirement is operational translation. Courts may not speak in registry categories. An order may say that an asset must not be transferred, that a company must preserve property, that an administrator controls the estate, that a party must not dispose of rights, or that information must be disclosed. The registry must translate that language into precise action: transfer hold, authority note, account contact restriction, record preservation, limited disclosure, reverse-DNS continuity, RPKI maintenance, support-channel control, billing note or no action because the order binds someone else. Translation should be guided by written rules, not by ad hoc fear.
The third requirement is narrow implementation. If a court asks for a restraint on one block, unrelated resources should not be frozen unless the order or evidence requires it. If a member's authority is disputed, the last verified operational contacts should remain available for essential service unless that would defeat the order. If a court seeks preservation of evidence, the registry should preserve logs and documents without unnecessarily impairing member service. If compliance requires non-public action, the registry should still record internally what was done and why.
The fourth requirement is explanation. LACNIC should maintain standard material for courts and counsel explaining the operational consequences of common registry actions. What does a transfer hold do? What does it not do? What happens to RDAP publication? What is the risk of changing or revoking route-origin attestations? What does reverse DNS support? What is the difference between account control and resource ownership? What is the difference between preserving the last verified state and approving a new transfer? Such explanations help courts issue better orders. They also show that the registry is not resisting accountability; it is preventing collateral damage.
The fifth requirement is review. Legal orders should not become permanent shadows unless the law requires it. Each hold should have a review date, a responsible role, a record of communications and an evidence checklist. The registry should know how many holds are active, how old they are, what service effects they have, and what is needed to release or maintain them. Without review, temporary measures become a hidden layer of policy.
The sixth requirement is aggregate reporting. Members need not see confidential details. They should know categories: number of legal demands, transfer restraints, authority disputes, insolvency matters, payment-related holds, government requests, narrowed orders, challenged orders, service effects and average resolution times. Confidentiality can be preserved without making legal pressure invisible. Invisible pressure becomes rumour; rumour becomes premium.
Emergency authority should be narrow and real
Legal and governance stress are most dangerous when ordinary authority is contested. A board dispute, executive vacancy, removal, incapacity, resignation, conflict of interest or urgent litigation can leave staff unsure who may act. The registry may still need to pay invoices, renew insurance, maintain repositories, respond to security incidents, preserve records, instruct counsel, issue factual service notices and keep support channels open. If the authority to do those things depends on personalities rather than rules, continuity risk rises.
Every registry should distinguish governance direction from operational care. The board should supervise strategy, budgets, risk, senior leadership, conflicts, audit and institutional scope. Executives and staff should operate services, implement policy, support members, maintain systems, handle security and manage routine requests. In calm periods this division can be cooperative and informal. In crisis it must be explicit.
Caretaker authority should be narrow, written and reviewable. It should allow designated staff to maintain critical services, preserve records, pay ordinary obligations, handle security incidents, keep member support functioning, renew critical contracts, manage credentials under dual control, instruct counsel for urgent operational matters and communicate factual service status. It should not allow emergency actors to make contested policy choices, punish opponents, alter disputed records beyond necessity, expand institutional mandate, settle major claims without appropriate review or convert temporary authority into permanent control.
The board needs corresponding limits. Directors under legal stress should not use operational systems as instruments of factional control. They should not order broad record changes in individual disputes unless a clear rule, legal duty or security necessity supports action. They should not treat criticism or litigation as a threat to the internet. Their emergency role is to preserve legitimacy and continuity, not to operate the ledger by proclamation.
An emergency authority protocol should identify critical services: registry database, RDAP and WHOIS publication, reverse DNS, RPKI, member authentication, billing, transfer queues, support channels, backups, security monitoring, vendor contracts, bank accounts and member communications. It should identify decision rights: which roles may act, what approvals are needed, how conflicts are logged, what legal advice is required, how board notice works, how member notice works, how actions are audited and when emergency powers expire. It should require after-action reporting.
Credentials require special discipline. Conditional access to critical systems should be escrowed, audited and tested. Escrow does not mean reckless sharing. It means that signing operations, repository maintenance, database recovery, zone management, backups, vendor portals, emergency communication channels and finance systems can be recovered under defined triggers without depending on a single disputed office or unavailable employee. RPKI trust and repository continuity cannot be improvised safely in a crisis. Neither can bank authority.
Such a protocol would not make governance disputes disappear. It would make them less expensive. Members and counterparties could know that ordinary services continue while authority is resolved. Staff could avoid paralysis. Courts could see that the institution can preserve function without seeking immunity. The market could price LACNIC as a utility with emergency discipline rather than an association whose ledger depends on calm politics.
Insolvency, succession and the preservation of value
Insolvency is where legal doctrine and registry economics meet sharply. A distressed operator may still run a network. Its IPv4 resources may support customers, debt recovery, sale of the business or reorganisation. Creditors may see address holdings as part of enterprise value. Customers may care only that service continues. A court-appointed administrator, receiver or liquidator may need to maintain registry records while deciding whether assets are sold, operations continue or the company is wound down.
The wrong registry response is automatic destruction. Formal distress is not abandonment. In many legal systems, insolvency procedures exist to preserve value, not merely liquidate. A network may continue under supervision. A sale may maximise creditor recovery and preserve customer service. A registry that deregisters, disables security attestations or blocks all updates solely because distress exists may destroy value before the legal process can allocate it.
The opposite error is equally dangerous. The registry cannot accept any claimant who invokes insolvency. It must verify authority, identify the affected resources, preserve evidence, prevent fraudulent transfers and comply with applicable orders. It should not decide creditor priority or ownership disputes. Its job is to make lawful continuity possible while those questions are decided elsewhere.
For LACNIC, this means a published insolvency and succession path. The path should identify the evidence normally required from administrators, liquidators, receivers, restructuring officers, courts, public agencies and corporate successors. It should distinguish continuity actions from control changes. Continuity actions may include maintaining contacts, preserving reverse DNS, paying fees, maintaining route-origin attestations, receiving abuse reports and keeping public data accurate. Control changes may include transfer, sale, merger recognition, account takeover or material alteration of certification authority. The first category should often continue under verified authority. The second should receive deeper review.
Corporate succession is similar even outside insolvency. The region contains family-owned providers, public utilities, privatised telecom assets, university networks, municipal projects, carrier groups, subsidiaries, holding companies and cross-border reorganisations. A resource may have been issued to a company name that no longer matches the operating business. A successor may be lawful but poorly documented. A merger may have moved assets without listing number resources explicitly. A public-sector function may have shifted agencies. The registry's job is to turn lawful continuity into accurate records without using historical complexity as a source of discretionary control.
Resource-holder estates also raise customer-protection questions. If a network is being sold, customers may need time to migrate. If an address block is sold through a court-supervised process, routing-security and reverse-DNS continuity may be essential. If creditors dispute the sale, a transfer lock may be appropriate while operational use continues. If a business is abandoned, recovery procedures may apply. Each state requires a different response. A binary open-or-closed approach wastes value.
The economic principle is preservation of productive capacity. IPv4 cannot be replaced cheaply through ordinary new supply. IPv6 deployment remains essential, but it does not remove every immediate dependency on IPv4 reachability, reputation, customer equipment or third-party systems. A registry action that unnecessarily interrupts recognition during insolvency can harm creditors, employees, customers and the market. A registry action that recognises an unauthorised claimant can harm them as well. The solution is verified continuity, not institutional improvisation.
Government pressure and narrow compliance
LACNIC operates across jurisdictions with different legal cultures, political pressures and state capacities. It may receive requests from courts, regulators, law-enforcement bodies, finance authorities or public offices. Some requests may be lawful, precise and binding. Others may be informal, overbroad, politically motivated or directed at matters outside a number registry's function. The registry needs a doctrine of narrow compliance that neither ignores law nor turns the registry into a general enforcement arm.
The first rule is specificity. What is the legal authority? Which resource, account or service is affected? Is the order binding on LACNIC, on a member or on another party? Is it final or provisional? Does it require action, preservation, disclosure or restraint? Does it conflict with another order or member agreement? What is the least disruptive action consistent with compliance? These questions should be routine, not invented in a crisis.
The second rule is separability. A government request affecting one operator should not contaminate unrelated resources. A court order affecting a transfer should not disrupt unrelated account functions. A legal prohibition affecting a named party should not become general suspicion of a jurisdiction. A criminal complaint involving abuse should not become a transfer freeze unless the registry record, authority or specific legal duty requires it. Compliance should have blast-radius control.
The third rule is record preservation. When legal orders arrive, the registry should preserve relevant records, access logs, correspondence, authority documents and service-state evidence. It should maintain an audit trail of what it did, under what authority, which services were affected, who approved the action and when review is due. The point is not theatrical transparency in the middle of a sensitive case. The point is that the institution should be able to account for itself later.
The fourth rule is communication. Members should receive clear notice where lawful and safe. If notice cannot be given immediately, the reason should be recorded. Public reporting can be aggregate: number of legal demands by category, broad disposition, service effects, challenged demands, narrowed demands and average response times. Confidentiality can be preserved without making legal pressure invisible.
The fifth rule is mission boundary. A registry's compliance should be tied to record truth, authority, uniqueness, operational responsibility, security-state continuity, specific law and member agreement. It should not become a tool for broad industrial policy, political preference, commercial morality or state pressure unrelated to the registry record. If a government wants broader control over networks, that belongs in public law. The registry should not smuggle it into private recognition decisions.
This boundary is especially important where state capacity is uneven. Some public authorities will understand number resources well. Others may not. A court may issue an order using language more suited to tangible property than registry recognition. A regulator may ask for action that would harm customers more than the intended target. A law-enforcement request may be urgent but imprecise. LACNIC should be able to explain operational consequences and propose narrower implementation while respecting lawful authority.
Narrow compliance lowers risk for everyone. It helps courts get precise remedies. It helps members predict exposure. It helps staff resist pressure. It helps counterparties distinguish legal prohibition from institutional discomfort. It preserves LACNIC's legitimacy as a registry utility rather than a private enforcement platform.
AFRINIC as a warning, not a script
AFRINIC is the unavoidable caution in any discussion of registry continuity. It should be used carefully. LACNIC is not AFRINIC. Uruguay is not Mauritius. Latin America and the Caribbean are not Africa. LACNIC's governance, transfer environment, finances, membership culture and legal setting have their own characteristics. A lazy analogy would be unfair and analytically weak.
The useful lesson is narrower. AFRINIC showed how registry authority, scarce IPv4 value, litigation, receivership, election paralysis, creditor or member disputes, court orders, global coordination pressure and service continuity can become entangled. Once that happens, the registry stops being background infrastructure and becomes an economic event. Every statement about elections, board authority, resource rights, bank accounts, policy, receivership or possible succession can affect the confidence of resource holders and counterparties.
The caution is not that a registry should be insulated from legal challenge. That would draw the wrong conclusion. The caution is that continuity arrangements should exist before litigation tests them. If the only choices are to preserve the incumbent institution without question or to risk operational uncertainty, the design has failed. A mature registry should let courts hear disputes while the ledger remains accurate, publication services continue, security attestations remain coherent and legitimate updates remain possible.
For LACNIC, AFRINIC is a stress test rather than a prophecy. Could a dispute over a large holder be isolated from unrelated services? Could a contested transfer be paused without harming reverse DNS? Could a board dispute leave staff with clear caretaker authority? Could a court order be implemented narrowly? Could members understand what happens to RPKI, RDAP and transfer queues in a legal hold? Could a bank or creditor claim be absorbed without service panic? Could an emergency communication distinguish facts from institutional self-defence? Could a successor or interim operator preserve records if extreme corporate failure occurred?
Those questions are not accusations. They are the questions every critical registry should answer while calm. The time to define credential escrow, service failover, emergency authority, legal-order handling and independent audit is before a claimant asks a court for broad relief. The time to publish metrics on disputes, holds and service effects is before rumours set the price. The time to build board-succession rules is before authority is contested.
AFRINIC also teaches a political-economy lesson. The more discretionary power the registry holds over scarce resources, the more valuable control of the registry becomes. If board seats can influence enforcement posture, transfer mobility, fee incidence, resource interpretation, litigation strategy and emergency response, board control acquires economic value. That can attract the conflict that community institutions claim to avoid. The best way to reduce the prize is to narrow discretion. A board still matters, but it should not be able to turn legal stress into resource uncertainty.
LACNIC should therefore draw the institutional lesson, not the drama. Protect the ledger, not the mystique of the institution. Preserve service, not discretionary comfort. Keep courts available, but make disputes narrow. That is the useful comparison.
Reserves, audit and the boring cost of resilience
Continuity is not free. It requires reserves, insurance, counsel, audit, staff time, tested recovery, multilingual communication and disciplined governance. Members may reasonably ask why a registry holds money rather than lowering fees. The answer should not be institutional self-protection in vague terms. It should be a clear account of how reserves lower the continuity premium members would otherwise pay privately.
Reserves should be tied to defined risks: service continuity, cyber incidents, litigation absorption, vendor failure, business interruption, emergency communications, payment shocks, bank disruption, audit, recovery and temporary staffing needs. Members should see reserve targets, not just balances. They should understand which risks are funded, how targets are set, when reserves may be used, how replenishment works and which activities sit outside the continuity reserve. Money without explanation looks like accumulation. Money tied to continuity looks like insurance.
Legal-cost reporting should also be treated as continuity information. Members need not see privileged detail, but they should understand aggregate categories: litigation, external counsel, dispute handling, compliance, insurance, audit, emergency planning, recovery testing and member claims. If legal costs rise, members should know whether the rise reflects ordinary accountability, preventable governance weakness, member disputes, enforcement strategy, vendor claims or broader regulatory pressure. Without such categories, fees become opaque and trust declines.
Insurance and vendor terms also price legal risk. Insurers ask whether the institution has governance controls, incident response, continuity planning, documented authority, audited finances and clear legal duties. Vendors ask about payment reliability and authority to sign. Counsel prices urgency and ambiguity. Banks watch litigation and governance stress. Each counterparty charges for uncertainty in a different way. The bill eventually reaches members through fees, delays or thinner services.
Staff distraction is another cost. Legal stress consumes management attention. Engineers may be pulled into evidence preservation, declarations, access reviews or emergency planning. Support teams may handle worried members. Executives may communicate with courts, counsel and board members rather than improve service. This is why ring-fencing is economic, not only constitutional. The more a dispute can be contained to a narrow operational effect, the less staff time it drains from the registry's ordinary utility function.
Independent audit is the quiet mechanism that turns claims into confidence. Service-continuity controls, access logs, emergency actions, legal-order implementation, dispute holds, credential escrow, backup recovery, bank authority and RPKI continuity should be auditable. Auditability is legal insurance. Courts and members trust a registry more when it can show who did what, when, under what rule and with what limit. Audit also protects staff, because documented rules reduce the burden of personal judgment in contested cases.
The discipline should include failure exercises. A table-top exercise about a contested transfer is useful. So is an exercise about loss of bank authority, executive incapacity, a court order written too broadly, a disputed insolvency administrator, a late payment caused by foreign-exchange controls, a compromised member account, a vendor refusing service after a contract dispute, or a public authority demanding action outside the registry's role. These exercises need not be theatrical. Their purpose is to reveal whether written continuity rules actually identify who acts, what continues, what pauses, who communicates and what evidence is preserved.
Resilience becomes credible when it is boring enough to survive scrutiny. A registry should not need heroic improvisation to pay staff, keep repositories online, preserve reverse DNS, maintain the last verified routing-security state, answer a court or tell members what is unaffected. The cost of that boring resilience is real. The cost of lacking it is higher, because it is paid in discounts, delays, litigation, emergency counsel, reputational damage and member anxiety.
What LACNIC should measure before trouble
The quietest continuity controls are statistical. Metrics turn fear into evidence. They also reveal whether formally equal rules have unequal effects across geography, language and scale.
LACNIC should publish aggregate processing times for ordinary transfers, inter-regional transfers, merger and acquisition updates, name changes, public-sector successions, legacy regularisation, account recovery and dispute-affected files. Median time is useful, but long-tail time matters more. The long tail is where capital freezes, escrows fail and small sellers accept discounts. The data should separate applicant delay, registry review, payment issue, documentation supplement, need-review failure, legal hold, inter-registry coordination and operational-service lag.
It should publish categories of legal and dispute holds. How many resources were paused because of court orders? How many because of competing authority claims? How many because of suspected fraud? How many because of account compromise? How many because of insolvency or succession? How many because of payment? The public does not need private details. Members need to know whether holds are rare, narrow and resolved or growing into a shadow system.
It should publish service effects. Did any hold affect RPKI? Did reverse DNS continue? Were contacts updateable? Was public registration data annotated? Were transfers paused only for the disputed block or for wider accounts? How often were unrelated resources protected from a dispute? These questions go directly to the service-continuity firewall.
It should publish payment-friction categories. How often do payments fail or arrive late because of banking delay, intermediary fees, exchange controls, public procurement, invoice disputes or non-payment? How often do payment issues affect service states? This would help small operators plan and would prevent account standing from becoming an unmeasured choke point.
It should publish appeal and review outcomes. How many adverse decisions were appealed? How many were reversed, narrowed, confirmed or resolved by additional evidence? How long did review take? Which categories produced most friction? A registry that never reports review outcomes asks members to trust discretion blindly.
It should measure geography and language without shaming members. Do small island operators experience more documentation supplements? Do English-speaking Caribbean members face longer transfer times? Do Portuguese or Spanish documents receive different supplement rates? Do public-sector cases take longer? Do small blocks take longer relative to value? Aggregate answers would let LACNIC improve fairness without lowering integrity.
It should publish incident and recovery reports for continuity services. RPKI, RDAP, WHOIS, reverse DNS, member portals, transfer queues, billing systems and support channels should have incident categories and recovery times. Legal or governance incidents should be distinguished from technical outages. A service can be up technically and impaired institutionally. The distinction matters.
Finally, it should report reserves and legal-cost categories in a way that connects money to continuity. Members should know whether reserves are sized for real risks, whether legal costs are rising, whether insurance costs have changed, whether vendor resilience is funded and whether broader activities are consuming capacity needed for core services. A registry funded by members should show how member money lowers the continuity premium.
Metrics do not solve every dispute. They change the conversation. Instead of arguing whether the registry is trusted, members can ask whether delay is falling, whether holds are narrow, whether small markets face higher costs, whether RPKI is protected, whether legal orders are contained and whether reserves are doing real work. That is healthier politics than faith.
A lower-cost continuity bargain
The best court-continuity regime is one that makes litigation less dramatic. Members should be able to sue when they must. Creditors should be able to assert claims. Courts should be able to issue precise orders. Governments should be able to pursue lawful requests. Employees and vendors should be able to enforce contracts. Board disputes should have legal routes. Resource holders should be able to defend their interests. None of that should imply that the regional ledger becomes unstable.
LACNIC's bargain with its members should be modest and strong. Modest, because the registry should not claim to represent every economic interest in Latin America and the Caribbean or to decide the virtue of IPv4 commerce. Strong, because the registry must protect uniqueness, record accuracy, authenticated changes, public responsibility, reverse resolution, resource certification, transfer recognition and continuity during stress. The institution is most legitimate when it knows exactly what it must protect and exactly what it should not control.
The practical design is clear enough. Build a service-continuity firewall that separates ledger, RPKI, reverse DNS, transfers, billing, support, credentials and communications. Publish a court-order handling protocol that classifies demands, implements them narrowly, preserves evidence and explains registry consequences to courts. Create emergency authority that keeps critical services running while governance disputes are resolved, but is too narrow to become a political prize. Tie reserves to continuity risks and report legal costs in aggregate. Audit access, holds, emergency actions, bank authority and recovery tests. Communicate with members in plain operational terms. Measure delays, holds, payment friction, service effects and review outcomes. Treat compliance as a narrow duty, not as mission creep.
Court risk will never disappear. Scarce resources create disputes. Transfers create failed expectations. Corporate reorganisations create documentary ambiguity. Governments issue requests. Banks hesitate. Directors disagree. Staff and vendors change. Members enter distress. Courts impose orders. The question is whether those events remain bounded or become a region-wide confidence problem.
The economic prize is lower friction. If LACNIC can make legal states narrow, RPKI and reverse DNS resilient, transfer holds legible, payment states proportionate, emergency authority auditable, reserves disciplined and member communication factual, it will lower the private cost of relying on the registry. Buyers will require fewer discounts. Sellers will face fewer unexplained delays. Brokers will sell less uncertainty. Banks will receive better evidence. Small operators will not need insider knowledge to know what a court or payment issue means. Courts will understand operational consequences. Staff will be less exposed to improvised pressure.
That is the correct continuity premium: not a surcharge created by fear, but an investment in making fear unnecessary. A registry utility cannot promise peace. It can promise that conflict will not be allowed to contaminate more of the ledger than law and record integrity require.
For LACNIC, this matters because the region's diversity makes every hidden friction unequal. Large countries, small islands, Spanish, Portuguese and English communities, public networks, private carriers, family-owned providers, universities, cloud platforms and cross-border groups do not pay the same price for ambiguity. A legal rule that looks neutral from a conference room can become expensive in a small treasury office, a storm-exposed island network, a public-sector procurement file or a bank compliance queue. The registry cannot fix all those conditions. It can avoid adding avoidable uncertainty at the point where they meet.
Court and continuity risk is therefore not about predicting crisis. It is about building a registry whose most important sentence during a crisis can be short: the dispute is contained, the last verified state is preserved, critical services continue, lawful orders are implemented narrowly, members will be told what matters, and the ledger remains reliable.
That sentence has economic value. It is the difference between a registry record that markets treat as durable and one they treat as conditional on institutional calm. In a scarce IPv4 economy, and in a region where legal and financial distance is real, durability is not administrative housekeeping. It is the product.