Summary

  • In APNIC-region mergers and acquisitions, IPv4 risk turns less on headline scarcity and more on whether the buyer can prove holder identity, seller authority, transfer basis, operational continuity, and clean post-close registry recognition.
  • The buyer's problem is not solved by a purchase agreement alone: it must reconcile corporate control, APNIC or National Internet Registry evidence, customer use, routing state, dirty-prefix history, carve-outs, transition services, and the timing of recognition.
  • APNIC's M&A transfer page is a procedural exhibit, not a business conclusion; the hard work lies in proving that the address resources follow the deal without bringing avoidable liabilities.
  • Deals that treat IPv4 as a small technology annex risk price leakage, delayed closing, stranded customers, or post-close disputes over who can use and transfer the addresses.

The Address Line Item That Can Reprice A Deal

IPv4 holdings enter mergers and acquisitions in a deceptively modest way. They may appear in a technology diligence schedule, a network asset list, a seller disclosure letter, a transition-services annex, or a table of material contracts. Then the buyer discovers that the address position is not merely a list. It is a chain of recognition: corporate authority, registry records, National Internet Registry relationships, transfer eligibility, route-origin practice, customer reliance, abuse history, and contractual promises to third parties. If any link is weak, the price paid for the network can become detached from the control received at closing.

The APNIC region is a fertile setting for this problem. IPv4 scarcity has made address holdings economically material. Transfers and leases are common enough to support market pricing. Many networks depend on inherited, acquired, leased, or customer-used address blocks. National Internet Registries add local administrative layers in some economies. Corporate groups often hold resources in entities that do not match the perimeter of the sale. A buyer may purchase a data-centre business, a cloud platform, an ISP, a hosting provider, a managed-services company, or a regional subsidiary, only to find that the addresses are registered to a parent, a historic operating company, a domestic affiliate, or a party that is not being acquired.

This article is about M&A address risk, not incumbent optionality. The question is not whether an established holder can wait, sell, lease, or redeploy scarce IPv4 space over time. It is whether a buyer in a live transaction can be confident that the address resources that support the acquired business will be recognized, routeable, transferable, and clean after completion. That question is narrower, more urgent, and more document-heavy than a broad discussion of scarcity strategy.

APNIC's page for transfers due to merger, acquisition, or reorganisation gives the buyer a factual starting point. It indicates that corporate events can provide a basis for transfer or registration change when evidence supports the request. APNIC's general transfer conditions supply further procedural context. But those pages do not tell the buyer whether the seller has authority, whether all needed parties have signed, whether customer dependencies have been preserved, whether a National Internet Registry will require additional evidence, whether a carve-out has stranded the block, or whether a dirty prefix will reduce value after closing. Those are deal risks.

Holder Identity And Seller Authority

The first M&A question is simple: who is the holder? In practice, it is rarely simple enough. The seller may operate the network and announce the prefixes, but the registered holder may be another entity. A parent company may have centralized number resources while selling a regional business. A subsidiary may hold APNIC membership while the commercial business sits elsewhere. Historical acquisitions may have left records in the name of a company that has since changed name, merged, or become dormant. In National Internet Registry settings, domestic registration evidence may be essential to understanding who can act.

This distinction between operating use and recognized holding is where buyers often lose time. A purchase agreement can say that all network assets transfer, but APNIC or a National Internet Registry will look for evidence that the party requesting the change is entitled to do so. If the registered holder is outside the sale perimeter, the buyer needs that holder's consent or a restructuring before closing. If the holder is inside the perimeter but has old corporate records, the buyer needs name-change evidence, merger documents, board approvals, and authority certificates. If the addresses are held by a joint venture or a former affiliate, the buyer may face consent rights that were invisible in the technology schedule.

Seller authority is not merely a representation. It is a closing condition. The buyer should ask whether the seller can sign transfer forms, whether directors or officers have authority under local law, whether shareholder consent is required, whether insolvency or creditor restrictions apply, whether the addresses are subject to a pledge, and whether any court, regulator, or registry dispute limits the seller's power. In a fast-moving acquisition, these questions may feel slow. They are slower after closing, when the buyer has paid and the record does not move.

The LARUS publication of an APNIC company extract and the related legal review highlight why corporate evidence belongs in this conversation. The point is not to turn every network acquisition into a constitutional lawsuit. It is to recognize that address transfers sit at the intersection of corporate authority and registry recognition. A buyer cannot rely only on the seller's commercial story. It needs proof that the legal person on the relevant records can take the acts the transaction requires.

The Transfer Evidence Problem

The buyer's second question is evidence. APNIC's M&A transfer route is built around the idea that a merger, acquisition, or reorganisation can justify moving resources when documents support the change. That makes evidence the heart of the deal. The buyer should identify, early, what APNIC or the relevant National Internet Registry will need: sale agreement excerpts, merger certificates, corporate registry records, board resolutions, proof of name change, declarations of relationship among group entities, and confirmation that the transferred business includes the network using the resources.

The difficult cases are partial acquisitions. If a buyer acquires a business line rather than the whole company, the resource question becomes whether the addresses are sufficiently tied to the acquired business. A seller may want to keep part of the block for retained customers. A buyer may want all of it because the acquired network cannot operate without it. A registry may need evidence that the transfer reflects a real corporate event rather than a disguised market sale. The purchase agreement must therefore describe the address resources with precision, explain the business dependence, and allocate any retained or transferred portions clearly.

Evidence also matters for timing. A deal may sign before all registry documents are ready. The buyer then has to decide whether transfer recognition is a condition to closing, a covenant after closing, or a deferred deliverable backed by escrow, holdback, or indemnity. If the address block is mission-critical, post-close delivery may be too risky. If the block is useful but not essential, a holdback may be enough. The right answer depends on operational dependence and the probability that recognition will be delayed or refused.

Market materials from Brander Group, IPv4.Global, and IPXO show why buyers cannot treat transfer policy as a footnote. RIR transfer rules differ, market practice expects diligence on clean history and eligibility, and scarcity has created real financial stakes. These sources are not substitutes for APNIC's own procedure. They are evidence that sophisticated buyers already view address transfers as a market with legal and operational friction.

National Internet Registry Seams

National Internet Registry seams are a recurring APNIC-region issue. A buyer may plan for an APNIC transfer and later discover that the resource is administered through a domestic registry layer, or that local evidence must be reconciled with APNIC-facing records. The seam can affect language, document form, recognition of corporate change, local contacts, timing, and dispute handling. It can also affect who is treated as the party able to request a change.

In a domestic acquisition, the seam may be manageable because buyer, seller, registry relationship, and network operations all sit in one jurisdiction. In a cross-border acquisition, it becomes more complex. The seller may be incorporated in one economy, the address relationship may sit in another, the buyer may be elsewhere, and the network may serve customers across several markets. The buyer's lawyers may be expert in corporate M&A but unfamiliar with the registry path. The network team may know routing but not corporate evidence. The result is a gap where closing assumptions go untested.

The seam should be handled as a diligence workstream of its own. The buyer should identify which registry records matter, who maintains them, what domestic requirements apply, and what documents must be submitted before or after closing. It should confirm whether APNIC recognition and National Internet Registry recognition are both needed, whether one depends on the other, and whether any local policy limits transfer to an out-of-country buyer. It should also understand whether the acquired business needs a local member relationship after closing.

This is not a criticism of the National Internet Registry model. Local registry layers can support better domestic administration. The risk for M&A is not the existence of the layer, but the buyer's failure to plan for it. A seam that is known early becomes a closing item. A seam discovered late becomes leverage for delay, price renegotiation, or post-close dispute.

Customer And Routing Continuity

The buyer's fourth question is continuity. In a network acquisition, addresses are not only registry records. They are in routers, route objects, RPKI materials, reverse-DNS delegations, abuse contacts, customer contracts, firewall rules, cloud configurations, access lists, and monitoring tools. A buyer who receives registry recognition but loses routing continuity can still damage the acquired business. A buyer who preserves routing but lacks recognized control has a different problem: operational dependence without full administrative authority.

Customer continuity is especially sensitive where addresses are assigned, suballocated, or leased to customers. The seller may have promised fixed address ranges to enterprise clients, hosting customers, cloud tenants, or downstream networks. Some customers may announce the addresses themselves. Some may rely on reverse DNS. Some may have security rules tied to exact prefixes. If a transaction changes origin ASNs, route objects, or abuse contacts too quickly, customers may experience service disruption. If it changes them too slowly, the buyer may inherit unmanaged risk.

The purchase agreement should therefore treat address transition as a service-delivery issue, not just as a transfer issue. The buyer needs schedules of customer assignments, route-origin arrangements, RPKI Route Origin Authorizations, reverse-DNS responsibilities, abuse contacts, delegated administrators, and planned cutover dates. It needs the seller's cooperation during a transition period. It may need transition services for network operations, customer notices, and technical sign-offs. If addresses are split between retained and transferred businesses, the agreement must say who supports which customers during the split.

This is where the phrase "transfer" can mislead. A registry transfer may occur on one date, while the routing transition occurs across weeks or months. Conversely, operational control may move before formal recognition if the parties are careless. The best deals align the legal and technical calendars. They do not require perfect simultaneity, but they do require a controlled sequence that keeps customers online and evidence intact.

Dirty Prefixes, Abuse History, And Indemnity

Dirty-prefix risk is the M&A liability that often hides behind scarcity value. A block may have a market price, but its practical value depends on whether networks and security systems treat it as trustworthy. Prior spam, malware, fraud, botnet, proxy, sanctions-sensitive, or command-and-control use can leave reputation damage. Abuse databases, mail filters, hosting platforms, and counterparties may continue to penalize the prefix after the buyer takes control. The buyer may then own a scarce resource that is expensive to clean and hard to monetize.

Buyers should demand reputation diligence before signing or, at the latest, before closing. That diligence should review public blocklists, routing anomalies, origin history, abuse contacts, prior leasing arrangements, customer concentration, and unexplained changes in route origin. It should also distinguish between remediable and structural problems. A stale abuse contact can be fixed. A prefix with years of high-risk leasing activity may require a price adjustment, indemnity, remediation covenant, or exclusion from the purchased assets.

The seller's representations should be precise. A broad statement that all addresses are "in good standing" may be inadequate. The buyer needs statements about disputes, abuse notices, known blocklists, unauthorized announcements, customer claims, prior leases, suballocations, and security incidents that materially affect address use. If the seller refuses, that refusal is itself information. The buyer may still proceed, but it should price the risk rather than discovering it after close.

Dirty-prefix risk also affects post-close integration. The buyer may need to update abuse desks, publish new contacts, clean reverse DNS, replace route objects, revise RPKI attestations, notify major counterparties, or move high-risk customers off the block. These actions take time. They also require cooperation from the seller if historical data and customer records remain with the retained business. An indemnity without the data needed to remediate is only partial protection.

Carve-Outs And Stranded Address Space

Carve-outs create some of the hardest address questions in corporate transactions. A seller may sell a cloud division but retain a managed-services division that uses the same address pool. It may sell a regional ISP but keep enterprise customers served from shared infrastructure. It may sell data centres while retaining a backbone network. In each case, the address block may be economically tied to both the transferred and retained businesses.

The buyer should resist a vague promise that the parties will "allocate IP addresses as needed" after closing. The allocation must be described. Which prefixes transfer? Which remain? Which are temporarily shared? Who has the right to announce them? Who maintains route objects and RPKI materials? Who answers abuse complaints? Who bears the cost of renumbering retained customers? Who indemnifies whom if a retained customer causes reputation damage to a transferred block?

Carve-outs can also reveal that the seller is trying to sell business value while retaining the scarcest address value. That may be legitimate if priced openly. It is dangerous if hidden. IPv4 scarcity means the address pool may account for a material portion of the acquired network's economics. If the buyer pays for customer revenue but not for the addresses needed to serve those customers, it may be buying a transition problem rather than a durable business.

Conversely, the buyer should not assume it can take addresses that support retained customers without cost. Renumbering can be expensive, disruptive, and commercially sensitive. A fair deal may include temporary sharing, phased renumbering, or a service arrangement. The key is to make the address economics visible in the purchase price and transition package.

Transition Services And Post-Close Recognition

Transition services are often treated as an operational annex, but for IPv4 they can determine whether the buyer receives what it bought. If seller personnel control registry contacts, route objects, RPKI materials, reverse DNS, or customer records, the buyer may need their help after closing. The transition-services agreement should therefore include address-specific obligations: maintaining current announcements, supporting transfer submissions, updating contacts, helping with customer notices, preserving logs and abuse records, and assisting with reputation remediation.

The agreement should also allocate authority during the transition. A seller should not be able to change route origins, create new leases, split prefixes, or alter registry contacts in a way that undermines the buyer. A buyer should not be able to force abrupt changes that break retained customers unless the parties agreed to that outcome. Both sides need a controlled authority map.

Post-close recognition is the final test. The buyer may have signed documents, closed the acquisition, and taken operational control, yet still be waiting for registry updates. During that period, it faces liminal risk. It may be responsible for service but not fully reflected in records. It may owe customers uptime while relying on seller cooperation. It may have covenants to lenders or investors that assume control. If recognition is delayed, the buyer needs remedies: holdbacks, cooperation duties, indemnities, termination of transition fees, or step-in rights where lawful.

There is also a public-interest dimension. Disorderly transitions can create routing confusion, stale contact records, and delayed abuse response. A buyer that pushes for clean recognition is not merely protecting its purchase price. It is helping preserve a more accurate registry environment.

Financing The Acquisition

Many acquisitions that include material IPv4 holdings are financed. That adds another layer of address risk. Acquisition lenders may count the IPv4 position as part of collateral value or as a factor in enterprise value. They will care whether the buyer can obtain recognized control after closing, whether any addresses are pledged elsewhere, whether transfer is conditioned on documents not yet obtained, and whether dirty-prefix liabilities reduce value.

The acquisition lender's interests may not perfectly match the buyer's. A buyer may tolerate a post-close transfer delay if the business keeps operating. A lender may see that delay as a collateral defect. A buyer may accept leased address revenue. A lender may discount it if leases are opaque or hard to terminate. A buyer may view a National Internet Registry seam as routine. A lender may treat it as jurisdictional uncertainty. These differences should be resolved before signing the debt package.

The RIPE NCC seizure precedent is relevant in this financing context too. It shows that creditor claims against registration-related rights can become real. For an acquisition lender, that is both comfort and warning. Comfort, because address-related rights may be reachable in distress. Warning, because competing creditors, insolvency officers, and registries may all have views on the same resource. The buyer should avoid inheriting address blocks that are already entangled in security interests or disputes.

Closing Conditions, Holdbacks, And Price Protection

The transaction documents should decide how much address uncertainty the buyer is willing to carry after closing. If the address block is essential to revenue, recognized transfer or registry acceptance should be a closing condition. If the addresses are valuable but not essential to immediate operations, a holdback, escrow, or special indemnity may be enough. If only part of the block is uncertain, the parties can allocate a separate value to that part and release payment as evidence is delivered.

This is not mere legal tidiness. Price protection changes incentives. A seller who receives the full price before registry evidence is complete has less reason to spend management time solving awkward address questions. A seller facing a holdback has a reason to produce clean corporate documents, obtain consents, support National Internet Registry submissions, and help remediate dirty-prefix issues. The buyer does not need to punish the seller. It needs to make delivery of address control economically relevant.

The documents should also define what counts as successful delivery. A vague promise to "cooperate with transfer" may not be enough. The buyer may need recognition of the buyer or its designated affiliate as holder, acceptance of updated contacts, confirmation that no freeze or dispute blocks the resource, delivery of routing materials, transition of reverse DNS, handover of abuse records, and confirmation that no undisclosed lease or pledge impairs use. The definition should reflect the business dependence. A hosting provider needs more operational detail than a buyer acquiring a dormant address inventory.

Some sellers will argue that APNIC or a National Internet Registry controls timing, so they cannot guarantee recognition. That is partly true. It is also why the contract should allocate risk rather than ignore it. The seller can promise truthful evidence, full cooperation, no undisclosed restrictions, and timely response to registry questions. The buyer can accept that final recognition depends on registry review while still holding back value if the transfer fails for reasons within the seller's history or authority.

Closing conditions should be drafted with care where a transaction is public, competitive, or time-sensitive. A condition that gives the buyer too much discretion can destabilize the deal. A condition that is too weak can leave the buyer exposed. The middle ground is objective: specified resources, specified evidence, specified registry milestones, specified exceptions, and specified remedies. This gives deal teams a practical way to discuss address risk without turning every minor record issue into a right to walk away.

Representations, Disclosure, And What Silence Means

Representations are the buyer's written map of seller risk. In APNIC-region address deals, they should cover holder identity, authority to transfer, standing with APNIC or any National Internet Registry, absence of disputes or freezes, absence of undisclosed security interests, accuracy of customer and lease schedules, routing authority, known abuse history, and compliance with applicable transfer requirements. These statements should be tied to disclosure schedules that name the prefixes and explain exceptions.

Silence should be treated carefully. A seller may not volunteer that addresses are held by a different group entity, that a customer has a long-term right to a specific range, that a prefix has been leased through a broker, or that a National Internet Registry contact is no longer with the company. These facts may not look material to a corporate team focused on revenue and employees. They can be material to a buyer that needs registry recognition and clean use. The buyer should therefore ask targeted questions and require specific disclosures rather than relying on broad technology warranties.

The disclosure schedule should not be a dumping ground. It should identify the holder of each material prefix, the business using it, the route origin, any customer or third-party use, any lease or suballocation, any dispute, any known abuse issue, any pending transfer request, and any pledge or consent right. Where the seller cannot provide the answer, the gap should be named. Named uncertainty can be priced. Hidden uncertainty becomes a post-close argument.

Representations also shape remedies. If the seller states that no address resources are subject to undisclosed third-party use and that statement proves false, the buyer has a clearer claim. If the seller only promises general compliance with law, the claim may be harder and slower. In scarce IPv4 markets, the difference can be meaningful. The buyer may need money, cooperation, or both, and it may need them quickly enough to preserve customers.

There is also a reputational dimension. A buyer who discovers after closing that acquired prefixes have been associated with serious abuse may face questions from customers, peers, and security partners. A representation cannot erase that history, but it can allocate the cost of remediation and create a reason for sellers to disclose problems before the buyer inherits them.

Integration After Recognition

Even successful registry recognition does not end the work. The buyer must integrate the address position into its own network, compliance, customer-support, and finance systems. It must update records, align abuse handling, reconcile contracts, monitor route origins, review RPKI materials, and decide whether inherited leases or suballocations fit its risk tolerance. The first months after closing are where many hidden address issues become visible.

Integration should start before closing. The buyer should know which teams will own registry relationships, who will maintain route objects, who will answer abuse mail, who will communicate with customers, and who will monitor prefix reputation. If the acquired business used different tooling or outside advisers, the buyer needs a transition plan. If seller staff are leaving, knowledge transfer must occur before access disappears. Address knowledge often lives with a small number of network engineers; losing them can turn a clean legal transfer into an operational puzzle.

Customer communication requires judgment. Some customers need early notice because their security rules, reverse DNS, or routing arrangements will change. Others may not need any message if service remains stable. Over-notification can create anxiety; under-notification can create outages. The buyer should segment customers by dependence and risk. High-dependence customers deserve direct handling. Low-dependence customers may only need normal support readiness.

Integration is also the moment to decide whether to keep, sell, lease, or consolidate excess address space. That decision belongs after control is secure and liabilities are known. Selling too quickly may leave the business short of addresses. Leasing too quickly may import the very opacity the buyer tried to avoid. Consolidating too aggressively may disrupt customers. The better sequence is control, cleanup, measurement, then economic optimization.

The buyer should preserve evidence of the transition. Copies of registry communications, seller cooperation records, customer notices, route changes, and remediation steps can matter later if a dispute arises. They also help future acquisitions. An enterprise that learns how address control moved in one deal can price the next deal more accurately.

When Commercial Economics And Registry Evidence Diverge

Sometimes the economics of a deal point one way while registry evidence points another. The buyer may pay for a business whose cash flow depends on a block, yet the block is registered to a parent that refuses to transfer. The seller may claim the addresses are included, while the APNIC or National Internet Registry path requires evidence that has not been produced. The buyer may value a large pool of addresses, only to find that many are tied to retained customers or long leases. These divergences are not rare edge cases. They are a normal consequence of scarcity meeting corporate history.

The buyer should not assume that commercial common sense will cure the evidence gap. A court or registry-facing process may ask what the documents show, not what the valuation model assumed. If the address position is economically central, the documents must make it central. If a block supports the acquired business, say so. If a block is excluded, say so. If a block is shared temporarily, define the period and the conduct allowed. If the seller's affiliate must act, make it a party or obtain a binding undertaking.

This is particularly important in competitive auctions. Sellers often prefer short diligence periods and limited document access. Buyers may fear that pressing too hard on address detail will make their bid look difficult. But a bid that ignores IPv4 control may be overpaying. A disciplined buyer can distinguish itself by asking focused questions early and converting the answers into price, conditions, or transition terms. That is not deal obstruction. It is risk pricing.

Registry evidence can also improve the seller's position. A seller with clean holder records, clear authority, documented customer use, and ready APNIC or National Internet Registry materials can defend a higher valuation. In a market where IPv4 scarcity attracts buyer attention, clean transfer evidence is not administrative housekeeping. It is part of the asset story.

Governance Questions For The Buyer

Buyers often assign address diligence to network engineers, then ask lawyers to paper the result. That division is too narrow. IPv4 risk should also reach the investment committee, the board, and the post-close integration leaders when address holdings are material to the deal. The reason is straightforward: the risk can affect price, closing certainty, customer revenue, financing, and liability allocation. It is not only a technical matter.

The investment committee should know how much of the target's value depends on scarce address space, whether the buyer will control that space after closing, and what discount has been applied for transfer uncertainty. If the valuation assumes continuing customer revenue from address-dependent services, the committee should know whether those customers can be served under the buyer's control. If the valuation assumes sale or lease of excess addresses, it should know whether those addresses are clean, transferable, and free of retained-business claims.

The board or senior approval body should focus on authority and downside. Does the seller actually hold the resources it says it is selling? Are any addresses pledged to lenders or tied to insolvency risk? Is a National Internet Registry approval path needed? Could a dirty-prefix history produce customer or security problems after close? Are there sanctions, abuse, or law-enforcement sensitivities around prior use? Could a carve-out leave the buyer operating with too little address capacity? These questions are not designed to stop a deal. They are designed to prevent the buyer from purchasing a network whose control assumptions are wrong.

Post-close leaders need a different view. They must know which tasks start on day one: registry contact updates, route-origin confirmation, RPKI review, reverse-DNS handling, abuse contact takeover, customer notices, lease review, and monitoring of reputation signals. They also need authority to escalate quickly if the seller fails to cooperate. A buyer that leaves these tasks to informal coordination can lose weeks while customers and counterparties still expect stable service.

The governance point is especially important in roll-up strategies. A buyer acquiring multiple regional networks may see the same address issues repeat across targets. Over time, small mistakes compound: inconsistent holder records, mixed lease terms, unclean route history, and unclear National Internet Registry relationships. A disciplined buyer builds a house view on APNIC-region address risk and applies it across transactions. That creates better pricing, cleaner integration, and stronger negotiating power with sellers.

Insurance, Indemnity, And The Limits Of Risk Transfer

Buyers may try to move IPv4 risk into indemnities, warranty insurance, or seller escrows. Those tools help, but they do not replace control. Money received after a claim does not keep a customer online, clean a prefix overnight, or persuade a registry to accept weak evidence. The buyer should use financial protection for residual risk, not as an excuse to tolerate an address position that cannot support the acquired business.

Warranty insurance can be awkward for address risk because insurers may not understand registry recognition, routing reputation, or National Internet Registry seams in detail. They may exclude known issues, require narrow wording, or price the risk conservatively. Even where coverage is available, claims can take time. A buyer that needs immediate operational continuity should not rely on insurance as the first remedy.

Indemnities should be specific. A seller can indemnify the buyer for losses arising from undisclosed leases, misidentified holders, dirty-prefix history, failure to provide transfer evidence, retained-business use, or third-party claims to the addresses. But the indemnity should be paired with cooperation duties. If the seller has the documents, customer contacts, or historical logs needed to fix the problem, paying damages later is not enough. The buyer needs access to the material that allows remediation.

Escrows and holdbacks are often more useful because they create near-term leverage. If registry recognition is delayed, if a retained customer has not renumbered, or if a dirty-prefix issue requires cleanup, money can remain withheld until the problem is addressed. The amount should reflect the business importance of the address block, not just a generic percentage of purchase price. A small escrow may be meaningless if the prefix supports a large share of revenue.

Risk transfer also has a fairness boundary. Sellers should not be asked to guarantee every future route reputation issue or every customer action after closing. The buyer must own its own operation. The practical division is temporal and evidential: sellers answer for history, authority, disclosure, and promised cooperation; buyers answer for post-close management once control and evidence have been delivered.

What Good M&A Diligence Looks Like

A mature buyer treats APNIC-region address diligence as a set of linked tests. It verifies holder identity. It confirms seller authority. It maps APNIC and National Internet Registry records. It identifies transfer evidence. It reviews policies for merger, acquisition, and reorganisation. It tests customer and routing continuity. It investigates abuse and reputation. It discloses leases and suballocations. It handles carve-outs. It writes transition services around the actual address dependencies. It ties post-close recognition to remedies. It makes the purchase price reflect any gaps.

The work is not glamorous, but it is value-preserving. IPv4 scarcity has made address blocks economically meaningful. That means mistakes are no longer clerical. A missing consent can delay closing. A dirty prefix can reduce sale value. A National Internet Registry seam can create post-close uncertainty. A retained customer can prevent clean transfer. A route-origin change can disrupt service. A stale abuse record can damage the buyer's reputation. A pledge can give a lender unexpected leverage.

APNIC's official materials help the buyer understand the procedural route. They should not be asked to carry the whole conclusion. The conclusion belongs to the buyer: the deal is ready only when the corporate evidence, registry path, customer plan, routing transition, and liability allocation all point in the same direction.

The broader lesson is that IPv4 has become a control asset inside corporate transactions. It is not just a technical resource and not just a commodity. It is a scarce registry-recognized input into network service. In APNIC-region M&A, the buyer who understands that character can close with fewer surprises. The buyer who treats addresses as an annex may still close, but it may discover later that the most valuable part of the network was never fully delivered.

Sources and Further Reading