Summary
- AFRINIC-administered IPv4 can decide whether an acquisition delivers the address continuity, customer capacity and integration value a buyer thought it had priced.
- The acquisition file can look complete before the address risk has been solved.
The deal can close before the address position has moved
The acquisition file can look complete before the address risk has been solved. The buyer has agreed on enterprise value. Counsel has drafted the share-purchase agreement or asset-purchase agreement. Engineers have reviewed transit, customer migration, router configuration, service availability and integration cost. The seller has described its public IPv4 holdings as part of the business being sold. Everyone in the room understands that public IPv4 is scarce and commercially important. Yet the deal may still rest on a dangerous assumption: that control of the company automatically carries clean control of the registry-recognized address position on which the business depends.
That assumption is weak in merger and acquisition work. A buyer may think it is buying a network, a hosting provider, a data-center platform, an enterprise-connectivity business, an ISP, a managed-security company or a local infrastructure operator. Economically, however, part of what it is buying may be continuity in a recognized address position: the ability to keep using, defending, documenting, integrating and, where appropriate, transferring public IPv4 after corporate control changes. If that position cannot be verified or moved through the relevant registry process, the buyer can own the shares and still inherit a damaged operating base.
This is the M&A address-risk problem. It is not the lending question of creditor underwriting, collateral perfection, step-in rights or default remedies. It is not the accounting question of how IPv4 should be recognized, measured, impaired or disclosed. It is not the broader capitalization question of whether registry recognition has become a form of capital. The M&A question is narrower and more immediate: what did the buyer price, what did the seller promise, what must be true before closing, how should the price move if the address position is weaker than advertised, and who bears the cost if post-closing registry execution fails?
AFRINIC makes the issue visible because its records sit at the junction of scarcity, institutional stress and African network continuity. The African Network Information Centre is the Regional Internet Registry for Africa and parts of the Indian Ocean, registered in Mauritius and responsible for number-resource administration in its service region. Public materials and reporting have described IPv4 exhaustion, address-record controversy, the Cloud Innovation dispute, receivership, disputed election processes, attempts at governance recovery and continuing litigation pressure. Those references should be handled as reported context, not as a precise current legal-status claim or as a verdict on any particular target. They are enough, however, to show why buyers cannot treat registry recognition as a minor schedule.
The practical risk is that money moves faster than records. Sellers are paid. Management changes. Employees leave. Integration begins. Customers are migrated. Routing and reverse DNS are altered. Finance teams book synergies. Only then does the buyer discover that the recognized holder is not the seller entity, a range is used by a third party, a lease was never disclosed, a customer assignment limits migration, a dispute is unresolved, a registry account is not in good standing, or a required update is stuck in process. The buyer then bears the cost while the seller may already have received most of the purchase price.
Good transaction work therefore treats AFRINIC-administered IPv4 as transaction infrastructure. It is not a decorative technical appendix and not a simple property deed. It is a recognized operating position whose value depends on records, authority, procedure, timing, customer dependence and continuity. In a post-exhaustion market, that position can change deal economics even when no one intended to trade addresses separately.
Scarcity turns a registry file into transaction infrastructure
IPv4 scarcity changed what a buyer must see in a network acquisition. In an earlier period, public addressing might have been reviewed mainly as engineering inventory: enough capacity for customers, workable DNS, acceptable abuse handling and no obvious routing failure. Today the same inventory carries market value, strategic optionality and continuity risk. If the buyer cannot retain, update or integrate the target's address capacity after control changes, the revenue model can change after signing.
The point is not that IPv4 has become conventional real estate. Regional Internet Registries do not function like land registries, and their policy language often resists proprietary framing. The economic point is narrower. Scarce public IPv4 supports products, customer contracts, cloud access, mail deliverability, enterprise allowlists, payment systems, firewall rules, abuse response, routing credibility and expansion plans. A buyer that pays for those earnings is implicitly paying for the address position that helps produce them.
AFRINIC policy and fee materials are useful here only as factual exhibits. They should not be treated as the framing authority for the article or as a commercial conclusion. The relevant mechanics are still important. Transfer rules make recognized holder status, dispute status, recipient qualification, membership and justified need relevant to whether an address-related change can be processed. Fee and transfer materials make good standing relevant to the administrative file. M&A-related transfers are also treated differently from ordinary timing restrictions in the policy architecture. These are not philosophical claims about ownership. They are deal mechanics.
Mechanics are enough to create value risk. If recognized-holder status matters, holder identity becomes a diligence item. If dispute status matters, adverse claims become price issues. If recipient qualification matters, buyer structure matters. If good standing matters, unpaid fees and stale accounts become closing conditions. If M&A transfers follow a distinct path, the deal file must show why the corporate transaction fits that path rather than assuming that any signed agreement will be accepted as a completed move.
This is why two targets with the same address count can have different transaction value. One may have clean holder records, current contacts, no undisclosed leases, documented customer use, no known adverse claims, good payment status and a tested post-closing update plan. Another may route the same amount of space but hold it through a dormant affiliate, rely on undocumented suballocations, carry old reputation damage, use a former employee for registry access and have no clear evidence trail connecting revenue to recognition. The spreadsheet address count is identical. The deal risk is not.
Scarcity magnifies the difference. When replacement IPv4 is expensive or unavailable on acceptable terms, a defect is not clerical. It can delay customer onboarding, force renumbering, require leasing, impair service commitments, reduce margins, upset integration timing or trigger claims between buyer and seller. In a competitive auction, a bidder that underwrites this risk carefully may bid less than one that ignores it. If the careless bidder wins, the loss arrives during integration rather than in the auction room.
The economics resemble other regulated or quasi-regulated inputs without being identical to them. Spectrum, permits, concessions, payment licenses and interconnection rights can sit outside simple ownership while shaping enterprise value. IPv4 behaves in M&A like a value-bearing permission-and-record stack. The buyer is not merely buying contracts and equipment. It is buying continuity in a registry-recognized position.
AFRINIC makes uncertainty visible without deciding every deal
AFRINIC should not be used as a slogan. It is tempting to turn every article about AFRINIC into a general story about crisis, legitimacy or institutional conflict. That would miss the transaction question. The buyer of an address-dependent business does not need a sweeping judgment on the registry's public history. It needs to know whether the target's file can survive a change of control. AFRINIC matters because its reported history makes that file discipline harder to ignore.
Public reporting has described allegations around altered address records, disputes involving large holdings, receivership, election discontinuity, board-reconstitution efforts, ICANN and NRO attention, and later claims and counterclaims around continuing legal pressure. Those reports are context. They are not a finding that any target's address ranges are defective, and they do not establish the current procedural status of a particular transaction. A conservative buyer uses them to raise the evidentiary standard, not to assume guilt by region.
The institutional lesson is that a registry file can be stable enough for ordinary operations while still creating nonroutine uncertainty. Packets may move. Customers may remain live. Reverse DNS may answer. RPKI controls may be unchanged. Yet a corporate transaction may require proof that ordinary operations did not require: holder authority, board approval, prior transfer evidence, account standing, consent from an affiliate, absence of adverse claims, or eligibility of the buyer's structure. A registry that appears invisible during normal service can become highly visible at closing.
The market effect is a transaction-cost effect. Buyers demand more evidence, more warranty coverage, more escrow, more conservative valuation and more time. Sellers with clean files can meet the demand and may preserve value. Sellers with weak files may discover that address capacity they treated as a pricing advantage has become a discount. The registry itself is not setting the purchase price. The record environment changes how private parties allocate risk.
This is also where AFRINIC's mandate boundary matters. A registry should maintain accurate records, verify authority, protect uniqueness and process eligible changes under applicable rules. It should not become a hidden investment-approval board, a valuation office or a capital-control agency. But the parties cannot ask it to ignore weak evidence simply because a deal has closed. In a scarce market, the thinness and predictability of registry process help determine whether address-dependent businesses can change hands without value leakage.
For Africa and the Indian Ocean service region, this is not an abstract governance point. Network investment often depends on acquisitions: regional consolidation, data-center expansion, managed-service rollups, ISP rescue transactions, cross-border enterprise platforms and infrastructure partnerships. If buyers cannot trust that address continuity can be evidenced and executed, they will price risk into the region's network businesses. The loss appears as lower seller proceeds, slower integration and more customer disruption.
Diligence starts with holder identity, not traffic
The first mistake in address diligence is to begin with what routes. Routing evidence is important, but it is not deal authority. A target can announce prefixes, serve customers and maintain a credible network while the registry and corporate record sits somewhere else. The buyer should begin with the question a closing room can answer: who is recognized as holder, and how does that recognized position connect to the company being acquired?
Sometimes the answer is simple. The target operating company is the AFRINIC member, maintains the account, pays fees, controls contacts and runs the network. More often, corporate history makes the file untidy. The holder may be a legacy subsidiary, a founder-controlled company, a pre-reorganization name, a holding company, a related service provider, an acquired ISP, a dissolved brand that was later restored, or a company that once held the network before assets moved around the group. A buyer cannot assume that buying the revenue company transfers the address position.
The diligence file should map each material range to the recognized holder, current legal name, prior names, registration country, account contacts, fee status, service agreements, transfer history, related-party use and technical-control holders. It should show whether the seller owns shares in the holder, controls it contractually, merely uses addresses from it, leases from it, suballocates through it or relies on informal group practice. The more distance between revenue and recognition, the more pressure belongs on the purchase agreement.
Corporate authority is the next layer. If a transfer, member-name change or contact update is needed, who can approve it? Does the holder's board need to act? Are minority shareholders involved? Was the range inherited from an acquired company whose records were never updated? Did a prior sale of business include address-related rights, exclude them or stay silent? Has the holder been merged, struck off, restored or renamed? These questions sound like legal housekeeping until closing depends on them.
The buyer also needs records that support historical control. Allocation or assignment notices, registry correspondence, invoices, service agreements, transfer approvals, board resolutions, acquisition files, customer assignment schedules and network-use evidence all matter. They are not collected for ceremony. They are collected because stale records become bargaining failures when a registry, seller, buyer or court officer asks for proof under time pressure.
AFRINIC's public background adds caution. Public reporting in 2019 described allegations that African IPv4 records had been altered and that dormant or acquired African companies' address ranges had been misdirected into commercial use. That reporting does not taint every AFRINIC-administered range. It does show why present reachability and seller assertion are not enough. Chain-of-record evidence is market hygiene.
The buyer should be skeptical when the data room says only that "the company has enough IPv4." Enough for what? Held by whom? Used by which customers? Subject to which contracts? Transferable to which buyer? Defensible against which claims? Integrated through which sequence? The router can show what works today. The registry and corporate files show what may survive closing.
Customer use makes value less portable
Buyers often treat customer use as proof of value. A hosting provider's addresses support servers. An ISP's addresses support broadband subscribers. A data center's addresses help tenants launch services. A managed-services platform uses public IPv4 for VPNs, firewalls, mail systems and enterprise access. These uses can justify a higher valuation because they support revenue. They can also make the address position less portable and harder to integrate.
The diligence question is whether customer use is documented and controlled. Which customers have dedicated ranges, shared pools, static addresses or bring-your-own arrangements? Which promises appear in contracts, service descriptions, migration plans, acceptable-use policies or side letters? Are customers entitled to keep addresses after termination? Are resellers allowed to assign further downstream? Are any customers using the target's ranges through separate technical accounts or third-party maintainers? If the buyer cannot answer these questions, it has not bought a clean address position. It has bought a dependency map it has not read.
Leases and suballocations are especially sensitive. A seller may call something a customer assignment when the economic reality is a long-term lease or a private arrangement with renewal, termination, reputation and routing terms. A buyer needs to know who has paid for use, for how long, under what cancellation rights, with what abuse duties, with what reverse-DNS control and with what continuity promises. An undisclosed lease can reduce the buyer's ability to integrate, sell surplus capacity, terminate risky use or move customers onto a new architecture.
Reputation belongs in the same file. Address ranges carry operational memory. Spam listings, abuse complaints, malware history, bulletproof-hosting suspicion, stale geolocation, blocked mail reputation and suspicious routing patterns can lower value even if the registry record is current. A seller may say the history is old, unfair or already remediated. The buyer still needs evidence. Who handled the cleanup? Which ranges remain listed? Which customers generated incidents? What monitoring continues after closing?
The buyer should distinguish address use from address control. The target may use AFRINIC-administered ranges held by a third party. It may announce them under a letter of authority. It may provide services to customers who bring external addresses. It may host customers with their own RPKI or reverse-DNS dependencies. It may route ranges through an upstream or related company. These arrangements are not necessarily bad. They are dangerous when the buyer prices them as owned or cleanly controlled capacity.
Customer dependence also changes remedy. If a defect is found, the buyer may not be able simply to remove a range from use or delay integration. A bank, hospital, government agency, e-commerce platform or enterprise VPN customer may rely on static addressing and allowlists. Renumbering can break access, security rules, audits and support processes. Even a technically successful migration can consume staff time and goodwill. Address risk therefore becomes customer-retention risk.
The economic point is portability. IPv4 that is embedded in profitable customer relationships may be valuable because it produces revenue, but it may be less saleable, less movable and more expensive to rationalize. M&A valuation has to price both facts at once.
Seller promises should match the address file
Diligence discovers risk; representations and warranties allocate it. If a buyer pays for a business whose value depends on IPv4, the seller should not be able to describe addresses vaguely and escape responsibility when the file breaks after closing. The purchase agreement should turn address facts into specific promises without pretending that registry approval is automatic.
The basic promise is control. The seller should state which company is the recognized holder of each material range, whether that company is included in the transaction, and whether the seller has authority to cause any required registry update, transfer, name change or post-closing cooperation. The promise should cover legal authority and practical control: board approval, account access, current contacts, payment status, service agreements and technical credentials. A statement that "the target uses the addresses" is too weak.
The second promise is accuracy. Registry records, contacts, billing information, holder names, customer assignment records, routing-support records and reverse-DNS arrangements should be accurate in all material respects or disclosed as exceptions. Accuracy matters because stale records can delay closing and raise suspicion after closing. A former employee as account contact, a defunct trade name in the file or invoices sent to the wrong company may not interrupt packets today, but each can become costly when the buyer needs action.
The third promise concerns encumbrances. In address-dependent M&A, encumbrance means more than a bank lien. It includes leases, long-term customer-use rights, negative pledges, sale options, rights of first refusal, related-party use, broker commitments, settlement agreements, pending transfer requests, court restrictions, unpaid fees, security interests in proceeds and any contract that limits the buyer's ability to use, move, transfer or integrate the ranges. The label can be negotiated. The schedule must be concrete.
No-adverse-claim language is equally important. The seller should disclose any claim by a former owner, customer, lender, creditor, lessor, broker, registry, regulator, employee, shareholder, related party or technical provider that could affect recognized holder status, use, transferability or operational control. The buyer does not need a guarantee that no one in the world could complain. It needs a statement that the seller knows of no undisclosed material claim or proceeding touching the address position.
Continuity warranties connect signing to closing. The seller should not sell, lease, suballocate, renumber, withdraw, transfer, pledge, alter RPKI controls, change reverse DNS, change abuse contacts, migrate customers, submit material registry requests or amend address-related contracts outside ordinary course without buyer consent. That is not legal clutter. It prevents the purchased address position from changing after price has been set.
These promises do not make registry risk disappear. They make it priced, disclosed and enforceable between the parties. In a market where address records can move enterprise value, vague schedules invite post-closing litigation.
Closing conditions are a market signal, not paperwork
The central timing problem is that registry execution may sit after commercial closing. The buyer signs, funds and takes control, then begins updating records, transferring resources or aligning accounts. That sequence is convenient for deal momentum. It is dangerous when address value is material. A stronger transaction makes essential registry steps a condition to closing or at least a condition to release of the relevant price.
The first condition is authority. The holder entity should approve the transaction and any address-related steps needed at or after closing. Board resolutions, shareholder approvals, officer certificates and powers of attorney should be signed by the right party, not merely by the seller parent. If the holder is outside the acquired group, the buyer needs a binding undertaking from that holder. If the holder is inside the group, the buyer needs evidence that its pre-closing management can submit paperwork and that those acts survive control change.
The second condition is standing. The purchase agreement should require evidence that involved accounts are current, required fees have been paid, contacts are reachable, no closure or suspension path is live and any required membership or recipient-qualification process has been prepared. A buyer should not discover after closing that a missed invoice or stale account blocks a registry update.
The third condition is documentary readiness. Signed forms, transfer materials, name-change documents, historical support, recipient information, needs-justification evidence where relevant, contact updates, technical authorization letters and required confirmations should be delivered before funds move or before escrow releases. If the registry asks for additional evidence, the seller should have a defined duty to provide it quickly. A vague cooperation clause is weaker than a document schedule.
The fourth condition is absence of adverse change in the address file. Between signing and closing, no new dispute, freeze, material abuse event, undisclosed customer assignment, lease, routing disruption, registry refusal, unpaid fee, transfer restriction or adverse claim should arise without buyer rights. The clause should be narrower than a general material-adverse-effect provision, but it should exist. If address capacity is part of value, degradation of that capacity matters before payment is final.
The fifth condition is technical continuity. Closing should not rely only on signatures. The buyer needs a cutover plan for route announcements, upstream letters, RPKI access, IRR records, reverse-DNS control, abuse contacts, monitoring systems, customer notices, escalation paths and rollback authority. If technical controls move later, seller staff or contractors should remain available long enough to complete handover.
Some deals cannot wait for all registry steps. Share deals may need speed. Public-company transactions may close before local records are fully aligned. Rescue transactions may face deadlines. In those cases, the deal should separate legal closing from address-risk release. Holdbacks, escrow, covenants and post-closing conditions keep seller economics exposed until execution becomes real.
Closing discipline changes bargaining behavior. A seller with a clean file prepares early. A seller with a weak file resists specificity. The buyer should read that resistance as evidence. Registry execution is not administrative polish. It may be the difference between buying a functioning network and buying uncertainty with customers attached.
Price should adjust when continuity is uncertain
Price is where address risk becomes visible. If a target's value includes IPv4 capacity, the agreement should say how price changes if that capacity is unusable, untransferable, encumbered, reputation-damaged or delayed. Without a specific mechanism, the buyer is left arguing after closing that the business it bought is not the business it priced.
The simplest tool is a holdback. A portion of the purchase price tied to address value remains unpaid until specified registry and technical milestones are satisfied: holder update accepted, transfer approved where needed, standing confirmed, contacts changed, RPKI and reverse-DNS control delivered, no undisclosed dispute discovered and customer-use schedules verified. The holdback should not be symbolic. It should approximate the value at risk, replacement cost or likely integration cost if the file fails.
Escrow can serve the same function with more structure. Funds are paid at closing but released only when address conditions are met. The release triggers should be factual. Completion of scheduled registry steps is stronger than buyer satisfaction. Absence of unresolved adverse claims for a defined period after acceptance may be appropriate in higher-risk deals. The escrow should also define what happens if registry action is delayed for reasons neither party controls.
Indemnity is the backstop. If representations are false or undisclosed pre-closing conditions impair value, the buyer should have a claim. But indemnity alone may be too slow. The buyer needs working capital to lease replacement capacity, renumber customers, hire technical help, clean reputation, pay fees, litigate claims or delay integration. Escrow and holdback keep cash aligned with risk while facts are resolved.
Purchase-price adjustment can be formulaic without becoming mechanical. The agreement can give full value to ranges that are recognized, transferable, controlled and clean; reduced value to ranges with disclosed customer dependence, delayed update paths or reputation remediation; and replacement-cost treatment for ranges under active dispute, undisclosed lease, failed transfer or severe pre-closing abuse history. Formulae are imperfect, but they force parties to discuss address value before closing rather than in anger afterward.
Earn-out logic should be used carefully. A seller may propose that address-dependent value be paid over time if customers remain and registry execution completes. That can work where the seller continues to support integration. It can also create perverse incentives if the buyer controls migration choices or if the seller has little influence after closing. Earn-outs should be tied to facts the seller can affect: delivery of records, cooperation, registry approval, customer consents or remediation of known defects.
AFRINIC's institutional setting makes price discipline more important, not less. If public governance or litigation context can affect timing, confidence or process, the buyer should not absorb all timing risk by default. The seller should bear risk for facts it controlled or failed to disclose. The buyer should bear risk for its own structure and integration choices. Registry-wide uncertainty should be priced through escrow, conditions and conservative valuation rather than hidden inside a single enterprise-value number.
Integration begins while the lawyers are still drafting
Address integration is not a post-closing chore. It begins during diligence because the buyer needs to know whether the target's network can be absorbed without breaking customers or losing value. A clean legal transfer can still produce a poor acquisition if integration planning ignores how deeply addresses sit inside operations.
The first integration choice is whether to preserve, migrate or segment the target's address architecture. Preservation is easiest when the target remains a separate operating company with stable customers and clean records. Migration may be necessary when the buyer wants common routing, security, monitoring, product packaging or network design. Segmentation may be best when certain ranges carry reputation risk, customer dependence or policy sensitivity. Each choice changes cost, timing and registry work.
Renumbering is the visible cost, but not the only one. Customer firewalls, allowlists, VPNs, payment systems, mail records, content-delivery integrations, monitoring probes, geolocation databases, fraud controls, DNS records, support scripts and compliance evidence may all assume stable IPv4. A buyer that announces a rapid integration plan without reading those dependencies can turn address rationalization into churn. The cheapest network design can become the most expensive customer decision.
Customer contracts should be reviewed for address promises. Some agreements may promise dedicated public addresses, static addressing, notice periods before changes, specific hosting locations, security contacts or continuity for regulated services. Others may be silent but commercially sensitive. Enterprise customers may have embedded the target's addresses into their own controls. Even if the contract permits change, the account manager may know that forced change risks renewal. Integration risk therefore belongs in the revenue model.
Abuse and reputation monitoring should continue without a gap. If the buyer changes ticketing systems, abuse mailboxes, routing, reverse DNS or customer support processes at closing, incidents can fall between teams. A range with manageable history can deteriorate quickly if nobody owns response during transition. The buyer should assign range-level responsibility before closing and preserve seller knowledge long enough to understand recurring problems.
Reverse DNS is often underestimated. It supports mail, diagnostics, enterprise trust and operational identity. If reverse-DNS control is held by the seller's engineers, an upstream provider or a third-party DNS platform, the buyer needs access and documented zones. The registry's role in reverse delegation may intersect with membership status and registered assignments. A failed reverse-DNS handover can make a clean share acquisition feel broken to customers.
RPKI and related routing-security records require the same care. The buyer needs to know who can create, maintain or revoke route-origin authorizations; which ranges have current authorizations; which upstreams and IXPs rely on them; and how changes will be sequenced. The buyer should not discover after closing that a former employee controls the interface or that authorization changes lag the routing plan.
Integration also affects value. Some ranges are crucial to the going concern and should not be separated. Others may be surplus and can support future sale, lease or expansion. Some may be too reputation-damaged to use without remediation. A buyer that treats all ranges as fungible inventory will overpay for trapped capacity and underprepare for continuity work. M&A address risk is not solved by transfer approval alone. It is solved when the acquired address position has a credible operating home.
Operational records are evidence, not deal parties
M&A teams need disciplined vocabulary around technical records. Autonomous system numbers, prefixes, routing records, IRR records, ROAs, BGP announcements, reverse-DNS delegations and RPKI controls are not companies, counterparties or deal entities. They are operational records, controls and signals. Treating them as transaction parties confuses evidence with authority and can produce bad diligence.
Each record answers a different question. A prefix announcement shows that a network is originating reachability. It does not prove that the announcing company is the recognized holder. An IRR record may help upstreams build filters. It does not settle corporate authority. A ROA can show authorized origin information under RPKI. It does not show that the seller has no undisclosed lease or customer promise. Reverse DNS can show operational control over name mapping. It does not prove transfer eligibility.
The buyer should use these records as cross-checks. Does the recognized holder match the operator? If not, is there a letter of authority, customer relationship, lease or group structure explaining the difference? Do ROAs align with actual origins? Do reverse-DNS zones match the services being sold? Do routing records identify old maintainers or unrelated networks? Are stale records likely to cause upstream filters to reject a post-closing change? Each inconsistency may be benign. Each deserves explanation.
Operational records also shape closing mechanics. If the buyer plans to move origin to its own network, upstream acceptance may require updated letters, IRR records, ROAs and coordination with route-filtering parties. If the target's customers continue to use the same ranges, changes may be minimal. If ranges are split between acquired and retained businesses, sequencing becomes delicate. The buyer should avoid changing registry records, routing and customer assignments in the same uncontrolled window.
Monitoring continuity is a deal asset. The buyer should maintain visibility into route announcements, RPKI validity, DNS health, abuse mailbox function, blacklist status, geolocation anomalies, customer static assignments and critical service reachability before, during and after closing. A monitoring gap can allow a small configuration error to become a customer outage or reputation event. Integration plans should include dashboards and escalation contacts, not merely legal schedules.
Technical records can also reveal undisclosed economics. A range described as spare may be announced by a third-party network. A customer pool may show signs of long-term dedicated use. Reverse DNS may identify business lines not disclosed in revenue schedules. Routing history may contradict reputation statements. RPKI absence may indicate weak operational control. None of these facts alone proves misrepresentation, but together they help the buyer ask sharper questions.
The registry should not be asked to interpret every technical signal as a commercial claim. Its role is to maintain accurate number-resource records and process changes under applicable rules. The buyer's job is to connect those records to the transaction. Good M&A practice keeps the layers separate: corporate parties sign the deal, registry records support recognition, routing records support reachability and operational controls support continuity. Confusing the layers is how value leaks.
Post-closing failures move cost to the buyer
The most expensive address defects often appear after closing because the buyer is then the party that must keep customers running. Before closing, the seller can promise cooperation and present the file optimistically. After closing, the buyer owns outages, delays, employee departures, customer complaints and integration costs. That shift is why post-closing registry failure must be priced before funds move.
One failure mode is stale records. Contacts are obsolete, invoices went to an old address, account credentials are unclear, the holder name does not match current corporate records, or historic transfer evidence is missing. None of this may stop packets immediately. It can still delay updates, create suspicion, require affidavits, consume legal time and slow integration. The buyer pays in management attention as well as money.
Another failure mode is disputed control. A former shareholder, affiliate, customer, broker, creditor, employee, lessor or acquired-company successor asserts rights after closing. The claim may be weak, but it can make a registry cautious and make buyers of surplus capacity reluctant. If the seller has been paid, the buyer must decide whether to litigate, settle, isolate the range, preserve the status quo or claim against escrow. Each option reduces deal value.
Transfer or update delay is a third failure mode. The buyer may have assumed an M&A pathway but then find that recipient qualification, standing, paperwork, needs justification, regional-use facts or registry capacity takes longer than expected. In a stressed institutional setting, timing risk can matter as much as final approval. A three-month delay may be tolerable for a passive holding company and costly for a buyer integrating products and customer networks.
Technical-control failure is more immediate. The registry record may be clean, but the buyer lacks access to reverse-DNS zones, RPKI controls, router configurations, abuse mailboxes, monitoring systems, customer assignment databases or old support tickets. A seller engineer leaves. A third-party maintainer refuses to act without a new contract. A customer continues to submit requests to the seller. The buyer then has legal control of a company but not working control over the address-dependent service layer.
Reputation surprises can be just as damaging. A range used by the target may carry mail-blocking history, abuse complaints, geolocation errors or platform suspicion that was not disclosed in the deal model. The buyer may have to clean listings, compensate customers, move high-value accounts, lease replacement capacity or delay product launches. If warranty coverage is weak, the buyer absorbs the cost as integration noise.
The worst structure is full payment at closing with only a general indemnity. It leaves the buyer funding repairs while pursuing a claim whose value depends on proof, survival periods, caps, baskets and seller solvency. Address-specific holdbacks and covenants avoid that mismatch. They recognize a simple economic fact: the party with the most knowledge before closing should keep some exposure until the address position proves usable after closing.
Post-closing failure is not rare because sellers are malicious. It is common because corporate history is messy and address systems remember old facts. Acquired ISPs, hosting platforms and data-center businesses often carry years of informal customer accommodations. The buyer's risk is that informality becomes expensive only after control changes.
Voluntary control deals are not bankruptcy transfers
M&A address risk should not be collapsed into bankruptcy or insolvency resource transfer. The distinction matters because incentives, authority and pricing tools differ. A voluntary corporate transaction is a negotiated change of control or business sale between parties that can allocate risk by contract. Insolvency deals involve court officers, creditors, priority fights, estate value, distressed timing and formal remedy structures. The address questions overlap, but the center is not the same.
In a voluntary transaction, the seller can prepare. It can clean records, pay fees, update contacts, disclose leases, obtain consents, solve customer-use issues, gather historical evidence and negotiate warranties. The buyer can diligence before signing, condition closing, adjust price and walk away. Both sides can decide how much address risk to bear. If they fail, the loss is often a diligence and drafting failure, not an unavoidable estate problem.
In insolvency, cooperation may already have collapsed. Management may be displaced. Creditors may dispute value. A receiver, administrator, liquidator or court may need recognition. The sale may happen under compressed timelines. Registry process may intersect with legal priority and asset-realization duties. That is the subject of a different analysis. It asks whether address-related positions are assets, licenses, contractual claims or registry-dependent rights inside an estate, and how transfer works when ordinary corporate consent is impaired.
The voluntary M&A buyer should not borrow insolvency language too quickly. A negotiated acquisition should solve authority before closing, not rely on later court recognition. It should use seller representations, holder approvals, conditions, escrow and covenants, not default remedies. It should treat address integration as part of the operating plan, not as recovery from failure. If the buyer must think like a secured creditor or insolvency officer on day one, the file is already weak.
The distinction also protects AFRINIC's role. In a voluntary deal, the registry should not be asked to adjudicate creditor priority or estate distribution. It should be asked to process accurate records and eligible transfers or updates under applicable rules. If a dispute exists, it may need to pause or require evidence. But the ordinary M&A path should remain a corporate-change path, not a disguised enforcement proceeding.
Purchase-price tools differ as well. In voluntary M&A, a holdback compensates for uncertain address execution, an indemnity covers seller breach and a closing condition prevents premature payment. In insolvency, price may reflect distressed uncertainty and limited warranties. Buyers in voluntary deals should not accept insolvency-level uncertainty while paying full strategic-control prices. If the seller wants full value, it should deliver a full file.
AFRINIC's receivership history can be mentioned only as background for institutional continuity, not as a reason to turn every acquisition into bankruptcy analysis. The buyer's core problem is not remedy priority after default or estate control after insolvency. It is whether the company it voluntarily buys can continue to use and integrate the address position it priced.
The buyer is buying continuity
The economics of merger and acquisition address risk reduce to one proposition: the buyer is buying continuity, not merely addresses. It buys the ability to keep customers live, keep routes accepted, keep reverse DNS and RPKI aligned, keep abuse response functioning, keep registry records credible, keep product promises intact and keep future transfer or integration choices open. If any of those fail, the address count in the data room was only a partial truth.
AFRINIC is a test case because it combines three pressures that M&A markets dislike: scarce IPv4, institutionally consequential registry recognition and reported governance stress. None of those means AFRINIC-administered targets are unbuyable. Many may have clean, valuable and operationally critical address positions. The point is that buyers must underwrite the file, not the slogan. A working network can still carry an address defect that changes price after signing.
The correct response is discipline, not panic. Buyer diligence should prove holder identity, records, customer use, disputes, leases, encumbrances, standing, transferability and technical control. Seller representations should convert those facts into promises. Closing conditions should make essential registry steps visible before payment. Purchase-price mechanisms should hold back value until execution is real. Integration plans should treat routing, reverse DNS, RPKI, monitoring and customer sequencing as deal work, not aftercare.
This discipline also protects the registry from being asked to do the wrong job. AFRINIC should not have to guarantee buyer economics, bless enterprise value or resolve every private bargain. It should maintain accurate records and process eligible corporate changes predictably. Buyers and sellers should carry commercial risk through contract. That separation is what turns a registry from a capital gatekeeper back into trusted infrastructure.
The market consequence is straightforward. If registry-recognized address records are predictable, they support investment in African networks. If they are uncertain, M&A capital prices the uncertainty, sellers receive less, integrations slow, customers face more disruption and scarce IPv4 becomes harder to deploy efficiently. The loss is not only financial. It is operational capacity trapped by doubt.
Voluntary M&A is the right place to solve the problem because the parties can plan. They can prepare records before signing, negotiate price before closing and sequence integration before customers feel the change. Bankruptcy and default scenarios are harder because cooperation has already weakened. A normal acquisition should not wait until stress to discover who controls the address position.
The buyer's final test is practical. Assume the seller has been paid, the founder has left, the old network team is gone and AFRINIC asks for proof before processing a material update. Can the buyer produce the records, authority, customer map, technical controls and contractual rights needed to keep the acquired business operating? If yes, the address position was part of the deal. If no, the buyer bought a network whose scarcest input still belongs to uncertainty.